Free · Fast · Privacy-first

Compress Image for Email

Email attachment size limits are real and they bite at the worst possible moments.

⚡

Fits within email attachment limits

🔒

Faster to send and receive

✨

Works in any email client

⚡

No app download needed

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Image Compressor to your website

Drop the Image Compressor into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/image-tools/image-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/image-tools/image-compressor?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Compressor by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

How email clients handle large images and why inline images behave differently from attachments

Email images fall into two categories with completely different behavior, and confusing them is the source of most email image headaches. Attached images are files the recipient downloads separately by clicking the attachment, while inline images are embedded directly in the email body using Base64 encoding or CID references that the email client renders as part of the message. Attached images work like any other email attachment. They count against the provider's total attachment size limit, which is 25MB for Gmail, 20MB for Outlook, and 25MB for Yahoo Mail. Inline images, which appear directly in the email body between paragraphs of text, behave very differently. Outlook 2016 and earlier versions have well documented rendering bugs with inline images above roughly 1MB, causing the images to appear as blank boxes or red X placeholders depending on the security settings. Gmail renders inline images reliably up to about 5MB, but any inline image above 200KB contributes to triggering the View entire message truncation prompt because Gmail clips email threads exceeding 102KB total in the visible body. For email marketing, inline images above 200KB also trigger spam filters on Barracuda and SpamAssassin installations.

FixTools compresses images using the browser Canvas API, re-encoding JPEG files at the quality percentage you specify. For email attachments the practical targets are well understood. Individual photo attachments should stay under 2MB to download quickly on any connection. Batches of photos should keep each image under 500KB so the total email stays under 25MB even with fifty attachments. Inline email images should stay under 200KB to avoid Gmail truncation and Outlook rendering issues. JPEG quality of 80 percent typically achieves these targets for typical smartphone photos that start out between 3MB and 8MB. For PNG screenshots and document images commonly shared in business emails, converting to JPEG first using the Format Converter reduces file size by 40 to 70 percent before applying any quality compression, making the second step far more effective.

One practical tradeoff worth flagging clearly is what happens when the recipient plans to print the attached images. For event photos sent to a print shop, wedding photos forwarded to family members for printing, or product photos sent to a magazine for editorial use, compressing below 85 percent quality may visibly affect print clarity at A4 size or larger. In that case the right tool is a file sharing link to Google Drive, Dropbox, or WeTransfer rather than an email attachment, because file sharing services do not enforce the same size limits and can deliver the full original quality. For business documents, casual photo sharing, and general communication where screen viewing is the primary use, 80 percent JPEG quality is the right default. It reduces a 5MB photo to under 500KB while remaining indistinguishable from the original on any phone or laptop screen.

There is also a subtle compatibility issue with how different email clients render attached versus inline images that affects design decisions for newsletter and marketing emails. iOS Mail and Apple Mail on macOS treat inline image attachments slightly differently from how Gmail and Outlook treat them, and the rendering can vary further based on whether the recipient has remote image loading enabled in their email security settings. For marketing emails the safest pattern is hosted images referenced by URL from a CDN rather than inline Base64 images, which avoids all of the file size and rendering compatibility issues and lets you update images after sending without changing the email message itself.

Gmail message size limits (Google Support)Email image best practices (Litmus)

How to use this tool

💡

Upload your photo and compress to under 1MB for a good balance of quality and deliverability. Multiple images can be compressed one by one.

How It Works

Step-by-step guide to compress image for email:

1
Upload your image
Open the Image Compressor and upload the photograph or image you want to email. The tool decodes the file locally in your browser, which matters for sensitive business documents and personal photos that you do not want passing through a third party server before reaching the recipient.
2
Compress to under 1MB
Set quality to 80 percent as a starting point. Most photographs compress to under 1MB at this setting without any visible quality loss on screen, which keeps the total email comfortably within attachment limits even when you are sending several images attached to the same message.
3
Repeat for multiple images
If you are sending several images in the same email, compress each one in turn, or use the batch compressor to process the entire set in one operation. Batch processing is significantly faster when you have ten or more photos to send and produces consistent quality across the whole set.
4
Attach and send
Download the compressed images and attach them to your email in the normal way through your email client's attachment interface. The recipient receives a noticeably faster downloading message that does not eat through their mobile data and opens quickly on phones with limited storage.

Real-world examples

Common situations where this approach makes a real difference:

Real estate agent sending property photos to clients

A real estate agent emails 15 interior and exterior photographs to prospective buyers after a showing. The original photos from a professional shoot are 8MB to 12MB each, which would total over 130MB and far exceed Gmail's attachment limit. After compressing at 80 percent JPEG quality at 1600 by 1067 pixels, each photo lands between 350KB and 650KB. The 15 photo email totals approximately 7MB, well within Gmail's 25MB limit, downloads in seconds for the client on a phone, and shows every detail the buyer needs to evaluate the property.

HR manager sending offer letter with profile photo inline

An HR manager sends a personalized offer letter email to a new hire with the employee's profile photo embedded inline at the top of the message. The original photo pulled from LinkedIn is 2.4MB, which would cause rendering issues in older Outlook clients and trigger Gmail truncation. After compressing at 80 percent quality and resizing to 300 by 300 pixels for the inline display size, the embedded image is 42KB. The email displays correctly in Outlook 2019, Outlook 365, Gmail, and Apple Mail without truncation or rendering failures across all the recipient's devices.

Wedding photographer delivering preview images

A wedding photographer sends preview images to newlyweds via Gmail one week after the wedding as a quick first look before the full gallery delivery. The original RAW exports are 25MB each and even the JPEG previews are 8MB to 12MB. After compressing 10 preview photos at 82 percent quality at 1920 by 1280 pixels, each file is 700KB to 1.1MB. The 10 photo email totals 9MB, well under Gmail's 25MB limit, and the previews look excellent on phone screens for the couple to share immediately with family.

Email marketing campaign with product images

A small business marketing team prepares an HTML email newsletter announcing a new product line, with six inline product images embedded in the message body. Original product photos are 1.2MB to 2.5MB each. After compressing at 78 percent JPEG quality at 600 by 400 pixels for the email display size, each image is 55KB to 110KB. The email passes SpamAssassin's image to text ratio check, renders cleanly across Gmail, Outlook 365, and Apple Mail, and avoids the Gmail truncation prompt because the total inline image weight stays under the clipping threshold.

Pro tips

Get better results with these expert suggestions:

Keep inline email images under 200KB to avoid Gmail clipping

Gmail clips email threads when the total message size exceeds 102KB, showing a View entire message link that requires an extra click and breaks the reading flow. If your email has multiple inline images, keep each well under 80KB to 100KB to stay safely under this threshold. For promotional emails with three or four images, target 60KB per image at 600 pixels wide and you will land comfortably inside the limit.

Convert PNG screenshots to JPEG before emailing

Screenshots saved as PNG are commonly 1MB to 5MB for a full screen capture because PNG preserves every pixel losslessly. Converting to JPEG at 80 percent quality before compressing reduces them to 100KB to 300KB in almost every case. Use the Format Converter first, then compress. Document screenshots compress extremely efficiently with JPEG because they contain mostly flat colors and text blocks, exactly the content JPEG handles well.

Use Google Drive links for batches of high resolution photos

If you need to send more than 10 photos, or if recipients will print at large format, attach a Google Drive folder link instead of individual attached files. This bypasses attachment size limits entirely and recipients get the full original resolution to work with. You can also compress the Drive copies if you want faster preview loading inside Drive itself, which is helpful when the recipient is browsing the folder on a phone.

For Outlook recipients test inline images under 500KB

Outlook 2016 and 2019 have known and persistent issues rendering inline Base64 encoded images above roughly 800KB to 1MB depending on security settings. If your audience uses corporate Outlook on Windows, compress inline images to well under 300KB per image to ensure reliable rendering across the whole recipient base. For maximum compatibility, reference images via hosted URL rather than embedding inline, which sidesteps the entire rendering issue.

FAQ

Frequently asked questions

Gmail allows total attachments up to 25MB per email message. Outlook caps attachments at 20MB. Yahoo Mail allows 25MB. Apple Mail follows the iCloud limit of 20MB unless Mail Drop is enabled, which allows much larger attachments via iCloud. Individual images should ideally be under 2MB to 5MB each in practice, regardless of the absolute ceiling, to leave room for multiple attachments in the same message and to keep download times reasonable for recipients reading email on mobile data plans.

Uncompressed smartphone photographs are typically 3MB to 10MB each at default camera settings. On a typical mobile connection, a 5MB image takes two to four seconds to download depending on signal strength and tower congestion. Compressing to under 500KB brings download time to under half a second. Multiply that by ten images attached to a single email and the difference between receiving a compressed email and an uncompressed one is 20 to 40 seconds of waiting, which feels much longer when the recipient is trying to quickly check messages.

Always compress before attaching. Some email clients, particularly mobile Gmail and iOS Mail, auto compress attached images when sending, but this secondary compression degrades already compressed photographs further and is unpredictable in its quality output. Compressing manually with FixTools before attaching gives you full control over the output quality, lets you preview the result before sending, and avoids the unpredictable double compression that happens when the email client applies its own pass on top of your already optimized file.

For more than 10 high resolution photographs, use a file sharing link to Google Drive, Dropbox, or WeTransfer instead of email attachments. Share the folder link directly in the body of the email. This bypasses attachment size limits, lets recipients download selectively rather than all or nothing, and keeps the full original resolution available for printing or further editing. The Image to PDF tool also bundles multiple images into a single PDF attachment, which produces a smaller combined file size than sending each image individually.

Gmail does not automatically compress attached images when sent from the desktop web interface. On the Gmail mobile app there is an option to send large attachments via Google Drive link instead of as inline attachments, which Gmail may prompt you about for files above 25MB. Gmail does not silently compress your photographs in transit. Compress manually with a dedicated tool like FixTools to control the quality precisely and to ensure consistent output regardless of which device you are sending from.

Yes. All compression runs locally inside your browser using JavaScript and the Canvas API. Your images are never uploaded to any FixTools server and are fully private throughout the compression process. This matters significantly for business emails containing confidential documents, contracts, internal product photos, or sensitive company materials that should not pass through unknown third party compression services as part of a routine pre send optimization step.

Gmail clips email threads when the total message size exceeds 102KB, displaying a View entire message link that the recipient must click to see the full content. For emails with inline images encoded as Base64 directly in the HTML body, each image's Base64 encoding adds roughly 33 percent overhead to its file size. An 80KB inline image adds approximately 107KB to the email body when encoded. Keep each inline image well under 75KB to reliably avoid Gmail clipping for emails containing one to three inline images alongside text.

JPEG for photographs almost always. PNG only for graphics, logos, or screenshots where you need sharp text and edges to remain crisp. PNG photographs are 3 to 5 times larger than JPEG equivalents at the same visual quality on screen. A 4MB PNG photo becomes 600KB as JPEG at 82 percent quality with no visible difference. For business documents and screenshots with text overlays, PNG preserves sharp text noticeably better than JPEG, but for pure photographic content JPEG is the right default every time.

Use the FixTools batch compressor to process all photos at once at 80 percent quality, then attach the compressed batch to a single email. If the total batch is still close to the attachment limit after compression, split into two messages or switch to a shared cloud folder link. The Image to PDF tool also bundles multiple compressed photos into a single PDF, which is sometimes the cleanest way to send a small set of images that belong together as a single document.

Yes. The Canvas API re-encoding step does not preserve EXIF data, so camera model, exposure settings, capture timestamp, and embedded GPS coordinates are all stripped from the output. For most email use cases this is a positive privacy outcome because it prevents accidentally sharing home address coordinates with the recipient. If you specifically need to preserve metadata for an editorial or legal workflow, keep the original file alongside the compressed copy and use a dedicated metadata editor to handle the EXIF fields separately.