You shoot or export a product photo for your email campaign. It's 4.2 MB and looks great. You drop it into your email template and hit send — only to find that half your subscribers never see it because their email client clipped the message, deferred the image load, or their inbox provider quietly blocked it. The other half waited ten seconds for it to appear on mobile.
Email is one of the most unforgiving environments for large images. Unlike a web page that can lazy-load assets, email clients fetch images at open time — and they do it over whatever connection the recipient has, on whatever device they're using. Getting your JPEG file size right is not optional. It's the difference between an email that lands and one that gets ignored.
To reduce JPEG size for email, resize the image to 600px wide (the standard email column width), export at quality 65–75, and strip EXIF metadata. This typically reduces a multi-megabyte photo to under 150 KB — well within the safe threshold for all major email clients — with no visible quality loss at normal viewing sizes.
What is JPEG compression for email?
JPEG (Joint Photographic Experts Group) is a lossy image format — unlike PNG, every time you save a JPEG at a quality setting below 100, it permanently discards some pixel data using a compression algorithm called DCT (Discrete Cosine Transform). The lower the quality setting, the smaller the file and the more visible the degradation.
For email specifically, reducing JPEG size involves three distinct levers, and using all three together produces far better results than any one alone:
- Resizing — scaling the image down to the actual display width in the email template. Sending a 4000px-wide photo to display in a 600px column is the single biggest source of wasted bytes in email images.
- Quality reduction — lowering the JPEG quality setting from the export default (usually 90–95) to the email-optimized range of 65–75. At normal email viewing sizes, the difference is invisible.
- Metadata stripping — removing embedded EXIF data (GPS coordinates, camera model, shooting settings) and ICC color profiles that add KB of data with zero visual benefit in an email client.
Together, these three steps routinely produce 80–90% file size reductions from a raw camera export — taking a 4 MB photo to under 200 KB without any visible loss at email display sizes.
Why image size matters in email
The consequences of oversized email images are more severe than most senders realize. It's not just about slow loading — it affects whether your email renders at all.
- Gmail clipping. Gmail clips emails over 102 KB of total HTML payload. If your email is clipped, recipients see a "View entire message" link instead of your content — and your open tracking pixel is never fired, corrupting your analytics.
- Mobile load time. The majority of email opens happen on mobile, often on cellular connections. A 3 MB image in an email can take 8–12 seconds to load on a slow 4G connection. Most recipients don't wait.
- Inbox provider throttling. Some corporate email servers and ISPs apply size-based filtering or deferral to messages with heavy attachments or large inline images. Staying under 200 KB per image keeps you out of these filters.
- Rendering failures. Outlook on Windows has known issues with very large inline images — it will sometimes refuse to display them at all or distort them unpredictably.
- Bandwidth costs at scale. If you're sending 100,000 emails and each recipient loads a 2 MB image, that's 200 GB of image data served per campaign. Compress to 150 KB and you're at 15 GB — a substantial CDN cost difference.
Step-by-step: how to reduce JPEG size for email
- Determine the actual display width in your email template. Standard email templates are 600px wide. If your image spans the full column, your target export width is 600px — or 1200px if you're targeting high-DPI (Retina) screens. There is no reason to embed a 3000px image in a 600px column, no matter how high-resolution the original is.
-
Resize the image first, before compressing. In Photoshop: Image → Image Size → set width to 600px (or 1200px for Retina), resample with Bicubic Sharper. In GIMP: Image → Scale Image. In command line:
magick input.jpg -resize 600x output.jpg. Resizing alone — before touching quality — often cuts file size by 70–80%. -
Export or re-save at quality 65–75. In Photoshop: File → Export → Export As → JPEG, set Quality to 70. In GIMP: File → Export As → set quality to 70 in the JPEG options dialog. In command line:
magick input.jpg -quality 70 output.jpg. Quality 70 is the sweet spot: files are small, and degradation is invisible at 600px display width. -
Strip EXIF and metadata. Photoshop and most export tools include metadata by default. In Photoshop's Export As dialog, uncheck "Metadata." For command line, ExifTool is the standard:
exiftool -all= output.jpg. The Rebrixe JPEG Compressor strips metadata automatically. This step adds another 5–20 KB savings on camera photos. -
Run a final compression pass. After resizing and quality reduction, run the result through a dedicated JPEG optimizer like MozJPEG or jpegoptim. These tools re-encode the JPEG using more efficient Huffman tables without changing quality settings:
jpegoptim --max=75 --strip-all output.jpg. This typically squeezes an additional 5–15% on top of what Photoshop achieves at the same quality number. - Check the output in an email preview tool. Use Litmus, Email on Acid, or simply send yourself a test to your phone. Zoom in to 100% on your phone screen and confirm no visible blocking artifacts, banding, or color shifts. If you see issues, re-export at quality 75–80.
- Confirm the final file size. Right-click the output file and check its size. For a single inline image: target under 200 KB. For a hero image in a promotional email: target 100–150 KB. If you're still over, go back to step 2 — the most common cause is an image that was resized to display width but not to a round pixel dimension, causing unnecessary data.
Common mistakes that tank deliverability
1. Compressing without resizing first
The most common mistake: people lower the JPEG quality slider on a 4000px-wide original and wonder why the file is still 800 KB. Quality reduction alone on a large image produces a large file at lower quality — the worst of both worlds. Always resize to your template's display width before touching the quality setting.
2. Re-compressing an already-compressed JPEG
Every time you open and re-save a JPEG at a quality setting below 100, you add a new layer of compression artifacts on top of the existing ones. A photo that was saved at quality 80, opened, and resaved at quality 80 is not the same as a photo saved once at quality 80 — it's visibly worse. Always compress from the original high-quality source file, never from an already-compressed version.
3. Using PNG for photographic email images
PNG files of product photos or lifestyle images are almost always 3–5× larger than equivalent JPEG files at the same visual quality. If your email image doesn't require a transparent background, there is no reason to use PNG. Convert to JPEG and compress — the size difference is enormous.
4. Sending images as email attachments instead of hosted URLs
Images embedded as inline attachments (base64 or CID-referenced) bypass CDN caching,
inflate your raw email size, and trigger spam filters. Always host your images on a
CDN or your email platform's asset server and reference them with standard
<img src="https://..."> tags. This is both faster for recipients
and better for deliverability.
hero-banner-600w.jpg). This makes it immediately clear
that the file has already been resized for email, preventing colleagues from accidentally
uploading the original 4 MB source file to the template builder.
Real-world compression examples
These results are from applying the full workflow — resize to 600px, export at quality 70, strip metadata, MozJPEG pass — to common email image types:
The pattern is consistent: the resize step does the heavy lifting, and the quality reduction step finishes it off. Working from an original high-resolution source almost always achieves 85%+ total reduction with no perceptible quality loss at email viewing sizes.
Tool comparison
The right tool depends on your workflow — browser-based for one-off images, command-line or build-tool integration for automating production email pipelines.
| Tool | Type | Resizing | Metadata strip | Privacy | Best for |
|---|---|---|---|---|---|
| Rebrixe JPEG Compressor | Browser | Yes | Auto | Client-side only | Quick one-off email image prep, no uploads |
| Squoosh | Browser | Yes | Manual | Client-side only | Visual before/after comparison with MozJPEG |
| TinyJPG | Browser / API | No | Yes | Server upload | Batch compression via API for marketing teams |
| jpegoptim (CLI) | CLI | No | --strip-all | Local | Build pipelines and batch automation |
| MozJPEG (CLI) | CLI | No | Yes | Local | Maximum compression quality — best-in-class encoder |
| ImageOptim (macOS) | Desktop app | No | Yes | Local | macOS drag-and-drop batch workflows |
Compress your email JPEG right now — free
The Rebrixe JPEG Compressor runs entirely in your browser. Your images are never uploaded to a server — compression, resizing, and metadata stripping all happen locally. No account, no file size limit, no watermarks. Set your target width (600px for standard email templates), choose your quality level, and download the result in seconds.