Make every image as small as it can afford to be
Modern cameras produce 5–15 MB photos; modern life constantly demands “under 2 MB”, “under 500 KB”, “maximum 200 KB”. Profile pictures, visa applications, marketplace listings, CMS uploads, email attachments — the wall is everywhere, and resizing in a photo editor is a chore nobody enjoys. This compressor attacks both sources of bloat at once: a quality slider tames the encoding, and an optional dimension cap removes the pixels no screen will ever show. Batches welcome; before/after sizes reported per file and in total; nothing leaves your device.
How to compress images
- Drop one or more images (JPG, PNG, WEBP) into the tool.
- Set the quality slider — 70% is a strong default for sharing.
- Optionally cap the longest side: 1920 px covers full-screen viewing; 1280 px suits forms and forums.
- Click Compress and check the savings report; download files singly or all at once.
The two levers, and which one is doing the work
Quality controls how aggressively the encoder approximates detail; from 95% down to 70% the file often halves with no visible change at normal viewing distance. Dimensions are the silent giant: a 4000×3000 photo viewed on a 1920-pixel screen wastes three-quarters of its pixels, and capping it to 1920 instantly cuts the file ~75% before quality even enters the picture. The biggest wins come from pulling both levers — which is exactly what the “2 MB → 180 KB” transformations are made of.
PNG screenshots: a special note
By default the tool converts compressed output to JPG, which is what makes screenshots shrink 80–90%. If you need PNG to stay PNG — transparency, or razor-sharp UI text for documentation — tick Keep PNG as PNG; savings will be smaller (PNG is lossless) but dimension-capping still helps massively.
Quality settings by destination
- Web pages & listings: 70–80%, capped at 1920 px — fast and indistinguishable.
- Email & chat: 65–75%, capped at 1280–1920 px.
- Strict portals (≤200 KB): 60%, capped at 1280 or 800 px; re-run with lower values if needed.
- Anything you might print later: compress a copy — keep the original master untouched.
One drop, two sliders, and the upload wall stops being your problem — with a receipt showing exactly how many megabytes you saved.
Quick reference
| Property | Detail |
|---|---|
| Input | JPG, PNG, WEBP — batches supported |
| Levers | Quality slider + optional max dimension |
| Typical savings | 60–90% with both levers |
| PNG mode | Convert to JPG (max savings) or keep PNG |
| Reporting | Per-file and total before → after sizes |
| Originals | Never modified — output is a new download |
| Processing | 100% in-browser, no upload |
Frequently asked questions
How do I hit a specific target like “under 200 KB”?
Start at 60% quality with a 1280 px cap and check the reported size; adjust and re-run as needed. Each attempt takes seconds because nothing is uploaded — iteration is the intended workflow.
Will people notice the compression?
At 70%+ quality and sensible dimensions, no — not on screens. Visible artefacts only creep in below ~60%, and even then mostly around sharp, high-contrast edges.
Why did my PNG screenshot become a JPG?
Converting to JPG is where the dramatic savings come from, so it's the default. Tick “Keep PNG as PNG” to preserve format and transparency — dimension capping alone still shrinks most screenshots substantially.
Is the original photo on my device changed?
Never. Compression produces new files with “-compressed” in the name; your originals stay exactly as they were. Treat compressed copies as disposable exports.