Inbox attachment limits near one megabyte
Corporate inboxes and municipal webmail still reject inline photos above one megabyte even when the message body is tiny. The failure often appears after you pick a sharp phone photo measured in tens of megabytes, not because the subject was wrong. Plain backgrounds and tight framing usually beat aggressive quality drops alone. Evenly lit, face-forward crops usually survive tighter budgets better than wide scenes. Width and height on the result card update whenever the engine changes dimensions.
Portrait sharpness in the megabyte comfort zone
At one megabyte many headshots stay crisp enough for email threads and HR forwards when lighting is even. Panoramic vacation shots may still need mild width reduction to avoid banding before they fit a megabyte-class cap. Banding in skies appears before faces look merely soft; resize width when gradients strip. If rejection continues, re-read the help text for a second hidden rule. Landing under the published maximum usually beats chasing an exact byte count.
Quality search versus width reduction at 1MB
JPEG quality tuning handles most portrait exports. Extremely wide originals may need modest downscaling alongside quality steps, the result card lists dimensions whenever pixels change during targeting. High-contrast badge lettering survives better than thin scripts at tight caps. Open the download once before you close the tab. Temporary processing is not archival storage, save the download you intend to submit.
Outlook and Gmail recompression after 1MB export
Some clients recompress attachments on send even when the file already cleared one megabyte. Attach the browser download directly from disk when the client allows and keep a higher-resolution master offline. Copy the exact help-text number when switching pages. Neighboring tools look similar but can still fail validators. Nearby tools cover adjacent size and format rules when this page is not the match. When format or pixel rules sit outside this page, finish those steps on the related tools linked nearby.
Byte readout semantics for one-megabyte targets
Target met means the generated JPG is at or under one megabyte on disk. Oversize outputs are not labeled compliant; best-effort messaging appears when the cap cannot be reached reasonably. Families, product variants, and localized banners compress differently with identical settings. Open the download once before you close the tab. Temporary processing is not archival storage, save the download you intend to submit.
When kilobyte siblings replace 1MB targeting
If the recipient later publishes a fifty- or hundred-kilobyte portal cap, switch to the matching KB tool. One-megabyte optimization is for attachment comfort, not micro signature fields. Keep an uncompressed master until the destination accepts the file. If rejection continues, re-read the help text for a second hidden rule. Width and height on the result card update whenever the engine changes dimensions.
Send-day checklist for one-megabyte JPGs
Open the download once, confirm bytes clear one megabyte, verify JPEG is expected, and avoid renaming PNG with a .jpg extension on strict validators. Using the wrong numeric page wastes attempts even when the preview looks visually fine. If rejection continues, re-read the help text for a second hidden rule. Width and height on the result card update whenever the engine changes dimensions.
How this target works
The encoder tries quality steps, and may reduce pixels if quality alone cannot get under 1MB. The result card shows the generated file bytes, not a guessed number. A pass means the file is at or under 1MB (1048576 bytes).
How we check target tools
Representative target-size tools are run on the same photo set used in our research notes. We record generated bytes and whether the ceiling was met. This page uses that engine. Last methodology review: 5 October 2026. See how we test.
Limits you should expect
A tiny, already-light file may not shrink further. A huge, detailed photo may need fewer pixels to stay under the ceiling, which softens fine texture. The page never claims an exact byte count unless the generated file matches that count.
Technical reference
Everyday “JPEG” files follow the JFIF interchange pattern on top of JPEG compression. MDN summarizes the type, MIME value image/jpeg, and common extensions: MDN image file type guide.
Related research
Target ceilings behave differently from quality-first compression. The 100KB experiment is the measured example: 100KB JPG compression test.
Frequently asked questions
Is 1MB the same as 1024KB for email?
Labels differ by client wording. Trust the measured byte readout on the result card for the attachment you will send. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.
Will email portraits stay sharp at 1MB?
Usually yes for typical headshots. Preview at full zoom before forwarding sensitive identity photos. Batch mode still shows per-file previews. Review each result before submitting a set.
Resize before 1MB JPG targeting?
When width is extreme, mild downscaling can preserve detail better than quality alone, watch listed dimensions. JPEG target-size encoding is lossy; the preview exists so you can judge tradeoffs honestly.
1MB batch family photos?
Each attachment is processed independently with its own preview and download link. Batch mode still shows per-file previews. Review each result before submitting a set.
Is compressing toward 1MB still a lossy process?
Yes. 1MB leaves more room than kilobyte micro-limits, but JPEG re-encoding is still lossy. Keep a master offline and verify the downloaded bytes on disk before email or portal upload.
General compress vs 1MB page?
Use this page when instructions quote one megabyte explicitly; general compress has no published ceiling. Neighboring tools exist for nearby sizes; switching is better than forcing the wrong ceiling.