Workflows
How to Reduce Image Size for Email Attachments
Email attachments need a different kind of optimization than live website images because the goal is often smooth sending and easy opening, not maximum visual fidelity.
What you are really solving
How to Reduce Image Size for Email Attachments sounds simple, but the real task is creating files that send quickly and open easily without looking broken or unreadable — so the first move is to identify the destination (blog post, online form, CMS, email, ad platform, or messaging app) before touching any settings.
Step by step
Keep the guesses low: inspect the file, decide what the destination actually needs, then resize or compress in small, deliberate steps instead of re-exporting at random until it finally fits.
- Start by checking whether the image dimensions are much larger than email recipients actually need.
- Use a compatible, practical format for the content type.
- Compress moderately so the image remains readable and trustworthy.
- Send the optimized copy and keep the original separately if needed.
Settings that usually work
For many email attachments, realistic dimensions plus moderate JPG compression is enough. Use PNG only when text clarity or graphic edges justify it.
Example scenarios
A product photo shared with a vendor. A screenshot sent inside a support conversation. A scanned document image attached to a client email.
How it affects SEO and page speed
The same workflow usually improves any later web reuse because right-sized, lighter images are easier to publish efficiently.
Developer and workflow notes
Teams with email-heavy workflows should define simple attachment presets so file-size problems do not repeatedly slow down communication.
Common mistakes to avoid
- Emailing giant originals that recipients do not need.
- Using PNG for ordinary photo attachments without a reason.
- Over-compressing screenshots until labels become hard to read.
- Replacing the archive original with the reduced email copy.
Provider limits and the 33% encoding tax
Email never sends your file as raw bytes. The image is Base64-encoded into the MIME body, and Base64 turns every 3 bytes into 4, inflating the payload by roughly 33%. A 19 MB photo leaves your outbox as about 25.3 MB on the wire, which is why files that look under the cap still bounce. Size your attachments against the encoded weight, not the on-disk number.
Gmail caps a single message at 25 MB of attachments and silently swaps anything larger for a Google Drive link; its receiving ceiling is about 50 MB, so a Gmail-to-Gmail send tolerates more than a Gmail-to-corporate send. Microsoft 365 and Outlook.com default to a 20 MB per-message limit, and many on-premise Exchange servers are still tuned to 10 MB. To clear the broadest set of recipients in one shot, keep the total of all attachments under 10 MB on disk, which lands near 13.3 MB encoded and stays safely below every common gateway.
Per-use-case dimensions and KB budgets
Email is viewed on screen at 96 DPI, so the embedded DPI tag in the file metadata changes nothing about how large the image appears or weighs; only pixel dimensions and compression move the file size. A 4000x3000 px phone photo carries roughly 12 megapixels the recipient will never see in a reading pane that is about 600 px wide. Resize first with Resize Image, then apply JPG quality, and the savings compound. These targets keep attachments fast to send and sharp to open:
- Reference photo for a vendor or client: 1600x1200 px, JPG quality 80, target 200 to 400 KB.
- Screenshot inside a support thread: keep native pixel width up to 1920 px, export as PNG only if it holds small text, target under 300 KB; flatten to JPG quality 85 if it is a photo-style capture.
- Scanned document page: 1654x2339 px (A4 at 200 DPI), grayscale JPG quality 75, target 150 to 300 KB per page.
- Inline signature or logo embedded in the body: 150 to 200 px wide, PNG-8 or JPG, under 40 KB.
- Photo set of 5 to 10 images in one message: 1280 px on the long edge each, JPG quality 78, about 150 KB each to keep the whole message under 2 MB.
Inline images and the 102 KB Gmail clip
Images pasted into the message body behave differently from attachments. Gmail clips any message whose raw HTML and inline content exceeds 102 KB, hiding everything past the cutoff behind a View entire message link, which routinely buries email signatures and the bottom of newsletters. Keep every inline image small enough that the assembled message stays under that threshold, and never embed a full-resolution photo in the body when an attachment will do.
For signatures specifically, hold each embedded graphic to a 150 to 200 px display width and well under 40 KB, and set the HTML width and height attributes so the image does not reflow the layout while it loads. When a photo genuinely belongs in the body, run it through Compress Image to bring a 600 px-wide hero down to roughly 60 to 80 KB at JPG quality 75, which preserves clarity in the preview pane without tripping the clip. Always send the optimized copy and archive the untouched original separately, since the reduced version is sized for a screen, not for reprinting.
Worked example: eight photos under a 25 MB limit
A common email problem: eight holiday photos averaging 4.5 MB each total about 36 MB, over Gmail’s 25 MB attachment ceiling, so the send fails. Resizing each to 1600 px wide and compressing at quality 75 brings every file to roughly 380–420 KB, for a combined ~3.2 MB attachment that sends instantly and still looks clean on any screen the recipient opens it on.
The key move is resizing before compressing. At their original 4000+ px width the photos carry far more detail than any inbox preview or laptop screen can show, so dropping the dimensions removes most of the weight with zero visible cost — and only then does light compression finish the job.
Related tools
Use the tools below to apply this workflow directly in your browser and finish the job without leaving the page.
