compress image

How to compress photos for email without wrecking clarity

Gmail caps attachments at 25 MB, Outlook at 20 MB. Learn how to compress photos for email by resizing first, then using JPEG quality 80-85, without losing visible detail.

Published
April 28, 2026
Reading time
7 min read
Author
TinyPixel

TL;DR

  • Resize before you compress: a 12 MP phone photo resized to 2 MP drops more file size than compression alone.
  • JPEG at quality 80-85 looks identical to the original for photos while cutting size dramatically.
  • Save PNG for screenshots and logos; it's the wrong tool for camera photos going into email.
  • Gmail's 25 MB limit includes the whole message, not just your attachments.
  • The two-step workflow: resize to the display size you need, then compress with quality 80-85 JPEG.

You've probably hit the wall. You select a few photos from your phone, attach them to a Gmail message, and that red error pops up: "Attachment too large." Same story in Outlook, or worse, some school or work portal that chokes on anything over 5 MB. You don't want to send blurry mush, but you need to compress the photo for email in a way that actually gets through.

The good news: you don't have to choose between "too big to send" and "too ugly to look at." With the right two-step process, you can shrink files by 80-90% and still have a photo that looks clean on any screen.

Why email limits force the issue

Gmail caps total message size at 25 MB. Outlook stops at 20 MB. Many institutional systems cut you off at 10 MB, 5 MB, or even lower. And here's the catch: that limit includes everything in the message. The text, the signatures, and every attachment together. So three or four phone photos can blow right past it.

A modern iPhone shoots 12 MP photos that typically land between 4 and 6 MB each straight off the camera. Four of those and you're already at 16-24 MB. Add a screenshot or two and you've got a rejected email. The bandwidth and storage costs aren't the issue for you personally; the issue is that the server simply refuses to accept the message.

This is why so many people search for help right after Gmail or Outlook rejects them. You're not alone, and the fix is straightforward once you know the order of operations.

The biggest mistake: compressing before resizing

Most people's first instinct is to crank the JPEG quality slider down to 30 or 40 and hope for the best. That works, sort of. But it leaves you with artifacts, blocky patches in blue skies, and muddy detail in hair and grass.

The bigger win comes from resizing first. A 12 MP phone photo is 4032 by 3024 pixels. No one is viewing that at full resolution in their email client. Most laptop screens are 1920 by 1080. Many email panes show images far smaller. If you resize that 12 MP photo down to 2 MP, something like 1920 by 1440, you cut the pixel count by over 80%. The file size drops proportionally, and you haven't touched compression quality yet.

Resize first, then compress. That's the rule.

JPEG vs. PNG: pick the right format

For photos from a camera or phone, JPEG is the right tool. It's designed for continuous-tone images with gradients, skin tones, sky, foliage. At quality settings of 80 to 85, it's visually indistinguishable from the original to the human eye, while typically cutting file size to 20-30% of the uncompressed equivalent.

PNG is lossless, which sounds good, but it's the wrong choice for photos. A PNG of the same 12 MP image might be 10-15 MB with zero compression artifacts, but it's also three times the size of a well-crafted JPEG. PNG excels at screenshots, text, logos, and anything with sharp edges and solid color blocks. For your vacation photos, portrait shots, and pet pictures, use JPEG.

WebP can work too, but email clients are inconsistent about displaying it inline. Some show it. Some force a download. Until that's more reliable, JPEG remains the safe universal choice for email attachments.

The practical workflow step by step

Here's how to handle it without installing anything complicated.

Step 1: Resize to the dimensions you actually need

Open your image in any tool that lets you set pixel dimensions. If the photo is going into a document, a blog post, or just viewing on screen, 1920 pixels on the long edge is plenty. For a smaller inline image, 1200 or even 800 pixels might be enough.

When you resize, maintain the aspect ratio so the photo doesn't stretch. Most tools lock this by default. Don't upscale; only downsize.

You can resize images quickly with an online tool like TinyPixel's resizer if you don't want to open Photoshop or similar software.

Step 2: Export as JPEG at quality 80-85

This is the sweet spot. Quality 90 or 95 gives you diminishing returns: the file gets noticeably bigger but you can't see the difference. Quality 70 or below starts introducing visible artifacts, especially in smooth gradients and shadow areas.

At 80 to 85, you get that aggressive size reduction with clarity that holds up to normal viewing. A resized 1920px photo at quality 82 might land between 300 KB and 800 KB depending on content complexity. That's a file you can attach ten of and stay well under any email limit.

If you need to compress images after resizing, look for a tool that lets you set a target quality level rather than just a generic "high/medium/low" preset.

Step 3: Check the total bundle size before sending

Add up your attachments. Remember the limit is the total message, not per file. If you're at 22 MB in Gmail, that simple text you typed pushes you over. Consider splitting into two messages, or use a shared link for a large batch and attach just a preview image or two directly.

What about HEIC files from iPhones?

iPhones default to HEIC format, which is efficient but poorly supported outside the Apple ecosystem. Many Windows machines and Android phones can't open them without extra software. If your recipient might be on a different platform, convert to JPEG before attaching.

You can convert HEIC to JPEG directly in your browser if your phone or computer didn't handle it automatically.

Real numbers from a real photo

Take a typical iPhone photo: 4032 by 3024 pixels, 4.5 MB as HEIC, roughly 5.2 MB if exported to PNG.

Resize to 1920 by 1440 and export JPEG at quality 82: about 340 KB.

That's a 93% reduction from the PNG version, with no visible quality loss at normal viewing sizes. You could attach 73 of those in a single Gmail message. Or you could skip the resize, keep the full dimensions, compress to JPEG 82, and get maybe 1.8 MB. Still too big for a batch, and you gained nothing in visible quality because no screen shows those pixels anyway.

When to break the rules

If you're sending photos to a print shop, don't resize. They need the full resolution. Use a file transfer service instead of email for those originals. The workflow above is for viewing on screens: sharing memories, inserting into documents, attaching to forum posts, sending proofs for approval.

If your image has critical text overlays or UI elements, test at your chosen quality. Small text can degrade faster than photographic content. For mixed images, you might nudge to quality 88 or 90, or consider PNG for the text portion and JPEG for the photo portion separately.

Tools that keep it simple

You don't need to buy or install anything for basic email prep. Browser-based tools handle resizing, format conversion, and compression without uploading to social platforms or creating accounts you don't want. Look for tools that process locally in the browser if you're handling sensitive images.

For a broader set of edits (rotate, crop, flip), an editing toolset in the browser can handle the whole prep flow without multiple apps.

The TL;DR for busy people

Resize first. 1920px on the long edge is plenty for screen viewing. Export JPEG at quality 80-85. Skip PNG for photos. Check your total attachment size before hitting send. That's it. Your photos get through, and nobody emails back asking why everything looks like a 2005 webcam capture.

If Gmail or Outlook just bounced your attachment, now you know exactly why and exactly how to fix it in about sixty seconds.