Compress Images Online
Compress images up to 90% smaller with a browser-based compressor. Batch process, preview before/after, download a ZIP. No uploads.
- 100% browser-based — no uploads, ever
- Unlimited batch — process hundreds at once
- Free forever — no signup, no watermarks
- Works on iPhone, Android, Mac, Windows, Linux
Convert in four steps
Drop images, paste from clipboard, or use your camera on mobile.
Adjust quality or dimensions — or accept the smart defaults.
The tool runs on your device with no server round-trip.
One-click download, or a single ZIP for batches.
Common questions
Are my images uploaded to a server?
No. Every conversion in this tool runs entirely in your browser using the Canvas and File APIs. Your images never leave your device, which makes the tool faster, private by default, and safe for confidential or personal photos.
Is there a file size or count limit?
There is no hard limit imposed by us — the tool is bound only by your device's memory. Most modern phones and laptops comfortably process dozens of high-resolution photos at once.
Will I lose quality?
JPG is a lossy format, but at the default 92% quality setting most people cannot tell the difference from the original. Increase the quality slider to 100% for near-lossless output, or lower it for smaller files.
Does it work on iPhone and Android?
Yes. The interface is mobile-first, supports the camera and clipboard, and produces standard files that save directly to your device's downloads or photo library.
Everything worth knowing about the Image Compressor
Compressing an image well is not the same as making it smaller. Any tool can push quality to 30% and hand back a tiny file; the trick is to shrink the file to a fraction of its original size while keeping the result visibly indistinguishable from the source. That takes an encoder tuned to human perception rather than mathematical fidelity.
This compressor runs entirely in your browser and gives you two workflows: quality-first (pick a quality level, get whatever size it produces) and target-first (pick a target file size in KB, let the tool binary-search for the quality that hits it). Both work on JPG, PNG, and WebP inputs, and both are safe to use on private images because nothing is uploaded.
How much you can save without seeing it
Most photos taken by modern phones and cameras are already saved as JPG at quality 95 or higher. Re-encoding at quality 82 typically produces a file that is 40–60% smaller with no visible difference on a normal screen. On a landing page with a dozen photos, that's often enough to knock a full second off LCP and drop a page from 'needs improvement' to 'good' in PageSpeed Insights.
PNG screenshots and illustrations compress differently. The gains come from restructuring the color palette and stripping metadata rather than lossy re-encoding, so expect 10–30% reductions rather than the dramatic wins you see with JPG.
Quality vs target-size workflows
Use the quality slider when you care more about preserving fidelity than hitting an exact number: 'as small as it can be without looking bad' is a quality-first decision. Set it to 0.80 and check the before/after preview.
Use the target-size mode when a portal or client is imposing a hard limit — 200 KB for a visa photo, 50 KB for a job-board profile picture, 20 KB for a tiny avatar. The tool will keep re-encoding at progressively lower quality (and, if needed, progressively smaller dimensions) until the file fits.
Why the file is bigger than you expected
Very small photographs sometimes end up larger after re-compression than they were before. That's a sign the source was already aggressively compressed — every subsequent pass adds artefacts without shaving much size. If you see this, keep the original.
Screenshots of code editors or terminals are dense in fine text and don't compress well as JPG at any quality; use PNG or WebP for those. The compressor will happily produce a JPG, but the file may look mushier than the source.
Batch compression for websites
Drop the whole /images folder from your project. The tool applies the same quality setting to every file, keeps original filenames, and outputs a ZIP you can drop straight back into your build. For most sites this alone is a 30–60% asset-weight reduction — bigger than most 'performance optimization' plugins deliver.
Combine with the WebP converter for another 25–35% win on top. Together they routinely take a 20 MB image folder down to under 5 MB with no visible degradation.
What the tool won't do
It won't upscale — you can only make an image smaller in file size or pixel count, not larger. It won't losslessly reduce the size of a file that's already near the encoding floor. It won't preserve metadata by default (a privacy-first choice — most users compressing an image are about to share it).
- — Aim for 200 KB or under on hero images and 50 KB or under on thumbnails — that hits most performance budgets.
- — If the compressor makes a file bigger, keep the original — it's already well-compressed.
- — Combining compression with resizing (to actual displayed dimensions) gives you a much bigger win than either alone.