Email attachments
Compress JPEG to 200 KB
Preset and ready: drop a file and the output lands under 200 KB as JPEG — processed entirely in your browser.
Drop your image here or browse
JPEG, PNG, WebP — everything stays on your device
Why this exact limit matters
JPEG attachments have a hygiene problem nobody announces: your phone writes a multi-megabyte file, your mail app "optimizes" it on the way out, and the recipient’s client renders whatever survived. Setting the format and the ceiling yourself — JPEG, 200 KB — removes every invisible re-encode from that chain and puts exactly one deliberate compression in its place.
Shrinking attachments to a stated size keeps mail deliverable without forcing you to learn a photo editor just to send a picture. 200 KB is a moderate limit, common for application portals, and this page is preset to exactly that ceiling.
How to compress to 200 KB
- Drop your image into the box above — it stays on your device.
- Confirm the target: under 200 KB as JPEG.
- The MozJPEG encoder searches its quality range so the JPEG output lands just under your limit. Dimensions are left at their original size unless the target demands otherwise.
- Preview the result, compare it with the original if you want, and download — the filename carries its actual size.
Tip: If you attach photos regularly, compress before attaching rather than relying on the mail client's "large attachments" link — those links expire, while a small attachment is a real attachment.
Measured: one clean encode at attachment scale
A 914 KB portrait photograph, a 1920-pixel display cap, and a 200 KB JPEG ceiling — the quality ladder’s own verdict:
Bytes delivered
190.6 KB
4.8× under the source
Ladder result
q65
found by search, not guessed
Display frame
1067×1280
larger than inbox view needs
Same KB, full frame
q34
what pixels cost in quality
Two facts do the work here. Quality 65 at display scale is visually the original — nobody opens an attachment at 400% zoom. And the fourth stat is the comparison that matters when you are tempted to keep every pixel: the identical ceiling over the full 1500×1800 frame buys only quality 34.
Frequently asked questions
Progressive or baseline JPEG for attachments?
Baseline renders top-to-bottom everywhere; progressive loads in passes and occasionally confuses older clients and scanners that inspect mail. This tool emits standard baseline — the choice that never draws attention to itself.
Why do two photos at the same 200 KB look different in quality?
Because content sets the price: detailed scenes grow fast along the quality ladder, flat ones slowly. Identical ceilings produce identical bytes, never identical quality — which is exactly why byte-first beating quality-first matters.
If the recipient re-saves my attachment, does it degrade further?
Every JPEG re-encode is generation loss, but one round at quality 65 is invisible in practice. The dangerous pattern is repeated casual re-saving — keep your original, and this file is the disposable copy.
Will the recipient see a quality difference?
For photos shared to be looked at on a screen, the output of this tool at typical email limits is visually indistinguishable from the original. The comparison view shows both images side by side so you can judge for yourself.
How does the tool hit the exact JPEG size?
It encodes your image with the MozJPEG encoder several times, binary-searching the quality setting until the output lands just under your limit — then keeps that best result.
What happens to my image when I close the tab?
It is discarded from memory. Nothing was transmitted and nothing was stored, so there is nothing to delete.