What Is This Tool?
A JPG compressor re-encodes JPEG images at a stronger compression setting. Cameras and phones save JPGs at very conservative (high) quality — great as an original, wasteful for sharing: a 5 MB photo typically compresses to well under 1 MB with no difference visible on screen.
JPG compression works by discarding visual detail the eye barely registers, so it's a quality dial, not magic: this tool exposes that dial directly and shows the resulting size per image, plus an optional maximum width, since oversized dimensions are usually the other half of the problem.
Why Use It?
- Purpose-built for JPGs — the format your photos are already in.
- Quality slider with per-image before/after sizes: see exactly what each setting costs.
- Optional max-width resize handles the "4000px photo" problem in the same pass.
- Batch compression, individual downloads.
- Local and private — no upload, no size limit, no watermark.
How to Use
- Drop JPG files onto the box (or click to choose).
- Set quality — 75% is the sweet spot for sharing; 60% for maximum savings.
- Optionally cap the width (1920px covers full-screen use).
- Download each compressed file; savings are shown per image.
Example
Input
IMG_2054.jpg — 5.1 MB, straight from a phoneOutput
IMG_2054-compressed.jpg — 0.62 MB (−88%)75% quality + 1920px max width: indistinguishable on screen, 8× lighter.
Common use cases
- Shrinking phone photos before attaching them to an email that has a size limit, without leaving your inbox app to find a separate tool.
- Preparing product photos for a website where page-load speed depends directly on image size.
- Fitting a batch of event photos under a messaging app's per-file size cap before sending.
- Reducing storage use for a large personal photo archive without a visible quality trade-off.
Understanding generation loss
Every time a JPG is re-encoded — not just resized, any re-save counts — it discards a little more visual information, because JPG compression is lossy by design and doesn't know it already threw something away the last time. This is why the standard advice is to compress once from a high-quality original rather than repeatedly editing and re-saving the same JPG: five rounds of "just a small edit, re-save as JPG" degrades a photo noticeably more than one careful compression pass at the quality level you actually need, even if each individual re-save looks fine on its own.
Why phone photos compress so dramatically
Phone cameras deliberately save at very high, conservative quality settings — often 90%+ — because manufacturers assume you might crop, edit or print the photo later and don't want to bake in visible compression loss before you've had a chance to use the full detail. For casual sharing, chat, or web use, that conservative quality is mostly wasted: the human eye can't distinguish 90% from 75% quality on a phone or laptop screen, but the file size difference between them is often 3–5×. This is exactly the gap this tool is built to close — you get the file-size benefit of aggressive compression while keeping visual quality that's indistinguishable from the untouched original at normal viewing sizes.
Frequently Asked Questions
What quality setting should I use?
75–85% for anything people will look at closely; 60–70% for chat and email where speed matters more. Below 50% blockiness becomes visible. There's no single right answer — the live sizes let you test in seconds.
Can I compress a JPG multiple times?
Each re-encode loses a little more information (generation loss). One careful compression is fine; repeatedly editing and re-saving the same JPG gradually degrades it. Keep an original and compress copies.
Why is my JPG barely getting smaller?
It was probably already compressed — for example an image downloaded from the web. There's little left to remove. The tool warns when output would be larger than input; keep the original then.
JPG compressor vs the general Image Compressor — which one?
They share the same engine. This page is tuned for the JPG-only workflow (accepts only JPGs, always outputs JPG). Use the general Image Compressor when you also have PNGs/WebPs or want WebP output.
Are my photos uploaded?
No. Compression runs in your browser via the canvas API. Photos never leave your device — this also means no file-size limits and no queues.