Make any photo fit a 3 MB email attachment without it looking bad

Phone photos in 2026 are big. A photo from a recent iPhone or a flagship Android lands somewhere between 3 and 8 MB straight out of the camera roll. That is fine for sharing through iMessage or WhatsApp, which compress aggressively on their end. It is a problem when you need to attach a photo to an email, embed it in a contract, or upload it to a portal that capped attachments at 3 MB in 2014 and has never raised the limit.

This is the recipe.

图像压缩器

批量压缩为 WebP、AVIF、JXL，支持高级参数调节

→

What "looks bad" actually means

Most amateur photo compression goes wrong in one of two ways. Either the file is shrunk so aggressively that color banding shows up in the sky and the skin tones turn waxy. Or the file is resized to a tiny dimension so it looks like a thumbnail when the recipient zooms in. Both happen when you let an automated tool decide the settings for you.

The fix is to do two things deliberately: hit a target dimension first, then hit a target file size second. In that order. Resize is the lever that does the heavy lifting; quality is the lever that fine-tunes.

The recipe for a 3 MB target

For a typical phone photo (4032 × 3024 from an iPhone, similar from a modern Android):

1. Resize to 1920 pixels on the long edge. This is enough resolution to look sharp on a desktop screen, fill a presentation slide, or print at small sizes. Use Lanczos3 as the resize algorithm; it is the default in most tools and gives the sharpest result for downscaling.
2. Encode as JPEG at quality 85. The mozjpeg encoder produces files about 5 to 15 percent smaller than the standard JPEG library at the same visual quality. Quality 85 is the practical knee of the curve where the quality-to-size ratio is best. Going higher than 85 increases file size without visible improvement; going below 75 introduces visible artifacts.
3. Check the resulting file size. A 1920-wide JPEG at quality 85 is typically 400 KB to 1.2 MB. That fits any email cap with room to spare.

If the result is larger than 3 MB after step 3 (which can happen for very busy or high-noise photos), drop the long edge to 1600 pixels and re-encode. That is almost always enough.

A 1 MB target (for stricter portals)

Same recipe, two tweaks:

1. Resize to 1440 pixels on the long edge.
2. Encode as JPEG at quality 80.

Result: typically 300 to 800 KB, fits comfortably under 1 MB. The image still looks good at full screen on a laptop.

A 500 KB target (for legacy systems)

1. Resize to 1080 pixels on the long edge.
2. Encode as JPEG at quality 75.

Result: typically 150 to 450 KB. The image will look fine on a phone screen and slightly soft on a laptop, but it will fit through any portal short of 1990s dial-up era.

The mistake to avoid

Do not run the same image through two compression tools in sequence. Every JPEG-to-JPEG pass eats a small amount of detail. After two passes the file looks meaningfully worse than after one pass at the same final size. A common failure pattern: you save the photo at quality 95 in your photo app, then run it through a "compressor" that re-encodes it at quality 85, then attach the result. You just paid the JPEG quantization tax twice for the same final quality.

The right way: open the original (or the highest-quality version you have) and compress in one pass to the target size and quality. The compressor on this site can take a 10 MB original and produce a 1 MB JPEG in one step, which is structurally less destructive than two passes through different tools.

Format choice in 2026

JPEG is the right answer for email attachments specifically, because it is the format every mail client decodes correctly. WebP and AVIF are smaller but several email clients (corporate Outlook installs, older mobile clients, some webmail providers) still render them poorly or as a download attachment instead of inline. Save the modern formats for the web.

For graphic content (screenshots, charts, diagrams) headed to email, PNG is the right answer for the same reason. Universal decoder support, no chroma artifacts, smaller than you would expect once OxiPNG runs over it.

A 30-second mental checklist

Before attaching any photo to anything, ask:

• What is the byte cap on the destination? (Email: usually 25 MB. Specific portals: read their docs.)
• What is the recipient going to do with it? (Look on a phone? Print? Project on a screen?)
• Do I have time to compress carefully, or do I need a one-pass answer right now?

The 1920-wide / quality 85 recipe above is the one-pass answer for almost every photograph. Memorize it and you can stop fighting attachment limits forever.

Z.Tools·z.tools

Image Compressor · Z.Tools

Batch compress to WebP, AVIF, JXL with advanced controls