Loading page
About this tool
Work out amp-img dimensions, retina source sizes and estimated file weight against the 200 KB AMP for Email limit.
AMP Email Image Size Guide turns a placement in your email column into the three numbers you actually need: the CSS display size, the source pixel size to export for retina screens, and an estimated file weight per format. It also builds the matching amp-img tag — AMP for Email forbids plain img and requires width, height and a layout attribute — and tracks the 200 KB ceiling Gmail places on the AMP part of a message. Weight figures are planning estimates from typical bytes-per-pixel rates, not encoder output.
Open AMP Email Image Size Guide on AltFTool — it loads instantly in your browser.
Upload or drag in the file you want to work with.
Adjust the settings and preview the result.
Download the finished file to your device.
Emits width, height and layout in the form AMP validates, including responsive's aspect-ratio behaviour.
Tracks the 200 KB AMP part limit and the 75 KB amp-custom CSS cap as you change inputs.
Shows the same image at AVIF, WebP, JPEG, PNG and GIF, with base64 overhead alongside.
The AMP HTML part must be under 200 KB in Gmail; larger messages fall back to the plain HTML part. Inline styles in <style amp-custom> are separately capped at 75 KB. Images referenced by HTTPS URL do not count towards the 200 KB, but base64 data URIs do.
Design to a 600 px content column and export at twice the display width for retina screens — so a full-width hero is 1200 px wide. Going past 2x roughly doubles the pixel count again for a difference few readers can see on a phone.
No. AMP for Email replaces <img> with <amp-img>, which requires an explicit width, height and layout attribute. Use layout="responsive" for images that fill the column, "fixed" for exact pixel boxes and "intrinsic" for logos that must not be enlarged.
JPEG remains the safe default because decoder support across mail clients is uneven. WebP is roughly 30% smaller at similar quality and AVIF smaller still, so serve them through a content-negotiating CDN and keep a JPEG for the fallback HTML part.