How to Prepare Images for Email Attachments

Email limits are stricter than you think

Gmail allows roughly twenty-five megabytes per message including encoding overhead, which means your attachments should stay comfortably below twenty megabytes to avoid silent failures or bounced sends. Outlook and Microsoft 365 impose similar limits, often twenty to thirty-five megabytes depending on tenant policy. Mobile carriers and corporate gateways may cut far lower—ten megabytes or less—when scanning attachments for security.

Recipients on phones pay data charges for large downloads and may not open multi-megabyte images at all. Even when a message delivers successfully, huge inline images slow conversation threads and fill mailbox quotas. Preparing images before attaching them is courtesy and reliability engineering in one step.

FileShrinkr helps you hit safe targets quickly: compress to JPG or WEBP, merge multiple scans into one PDF, and download a ZIP of batch-processed files. You see results before opening your mail client, which beats discovering a send failure after composing a long message.

Set size and dimension targets

For a handful of casual photos, aim for one hundred to three hundred kilobytes per image at roughly sixteen hundred pixels on the long edge. That keeps a ten-photo gallery under three megabytes with room for message text. For document scans, five hundred kilobytes per page is usually plenty when text is the priority.

When total attachment budget is fixed—say eight megabytes for a conservative corporate gateway—divide by the number of files and compress to meet that per-file ceiling. PDF merge helps: ten scans as individual JPGs might inflate metadata and headers; one merged PDF often packages the same content with less overhead and simpler recipient experience.

Use FileShrinkr's editor to downscale images that exceed your pixel targets before compression. A four-thousand-pixel phone photo compressed to eighty percent quality may still exceed a three-hundred-kilobyte goal; resizing to sixteen hundred pixels first makes the quality slider effective again.

Choose JPG, WEBP, or PDF for email

JPG is the safest format for photo attachments because every mail client displays it inline without plugins. WEBP is smaller but some desktop clients still treat it as a generic attachment rather than a previewable image. When you know recipients use modern Gmail or Apple Mail, WEBP can shave another twenty percent off size; otherwise default to JPG for broad compatibility.

PDF works best for multi-page scans, forms, and mixed aspect ratios that should print on standard paper. One PDF attachment beats five separate images in a professional context. Enable compression on FileShrinkr unless the recipient explicitly requires lossless archival quality.

Avoid PNG for email photographs; file sizes balloon without visual benefit. PNG remains appropriate for small logos embedded in signatures, not for camera roll exports. SVG is rarely useful as an attachment—rasterize to JPG if you need universal preview.

Quality settings that preserve readability

Email photos rarely need print-grade fidelity. Quality seventy to seventy-five keeps skin tones smooth and landscapes attractive at phone screen sizes. Drop to sixty-five for secondary images or when you must squeeze an extra file into the same total budget. Raise to eighty only for hero images where detail is part of the message—product shots for a client approval, for example.

Scanned text demands sharper settings than scenery. Start at eighty quality and verify that small fonts remain crisp. If artifacts appear in letterforms, increase quality or resolution slightly rather than accepting blurry paragraphs. Rotated or skewed scans should be corrected in the editor before compression so OCR tools downstream read them cleanly.

FileShrinkr applies your quality choice consistently across batch uploads, which helps when you attach twelve similar receipt photos. Uniform processing prevents one random oversized file from breaking an otherwise compliant message.

Privacy and metadata considerations

Photos embed EXIF metadata: GPS location, device identifiers, and capture timestamps. Sharing images by email can unintentionally reveal where and when you took them. Stripping metadata before send reduces privacy risk and removes bytes. Even when location is not sensitive, cleaner files look more professional.

Corporate policies may prohibit certain attachment types or require encryption for confidential scans. Compression does not replace encryption, but smaller files encrypt and upload faster to secure portals. Know your organization's rules before batching HR or medical images.

When metadata removal becomes a dedicated step in your workflow, combine compression with explicit EXIF stripping in your editor or a future FileShrinkr option. Until then, be mindful that compressed JPGs may still carry metadata unless removed upstream.

Workflow checklist before you send

Rename files descriptively—invoice-march-electric.pdf beats IMG_4092.jpg in a client's inbox. Confirm total attachment size in your file explorer before composing. Open the compressed PDF or JPG locally to verify orientation, crop, and legibility. If using merge, scroll through every page once; one upside-down scan is a common preventable embarrassment.

For recurring sends—weekly field reports, property listings, classroom updates—save a FileShrinkr preset mentally: sixteen hundred pixel max width, JPG at seventy-five, merge scans to PDF. Repeatable habits beat relearning limits every time.

When a message still exceeds limits after compression, split into two emails with clear subject lines or upload a cloud link for the overflow. FileShrinkr gets you most of the way; knowing when to split rather than over-compress preserves quality for recipients who genuinely need it.