Compress and convert images without uploading them
Drop your files, choose a format and a target width, download smaller ones. Everything runs in this browser tab — no upload, no account, no per-file limit.
| File | Original | Output | Before | After | Saved |
|---|
Need this in your build pipeline?
Batch hundreds of files, run it from CI, or call it over HTTP. Pro starts at $9/month — flat, no per-image surprise billing.
Why this stays fast and free
Most converters upload your file, process it on a server, then hand it back. That server is why they meter you. This one has no server.
Nothing leaves your device
Decoding, resizing and re-encoding all happen with the browser's own image pipeline. There is no upload endpoint to leak.
No size limit, no queue
Your CPU is the server. A 40 MB photo takes as long as your machine needs, not as long as a free tier allows.
Works offline
Once the page is loaded, cut the network. It still converts — that is the honest test of a client-side tool.
Questions people actually ask
Is my image really not uploaded?
Correct. There is no backend. Open your browser's DevTools → Network tab and convert something: you will see no request carrying your image. If you want to be thorough, load the page, then disconnect from the internet and convert again.
Which format should I pick?
WebP for almost everything on the web: roughly 25–35% smaller than JPEG at the same visual quality, and it supports transparency. JPEG when the file has to open in ancient software or a print pipeline. PNG when you need lossless pixels or transparency for a design asset. AVIF is the smallest of the four, but browser encoding support is inconsistent — if it is unavailable, the tool falls back and labels the row so you know.
What quality setting should I use?
82% is the sweet spot for photos: most people cannot see the difference and you save a lot of bytes. Below 60% you start seeing blocking in gradients and skies. Screenshots and text-heavy images usually look better as PNG at full quality than as low-quality JPEG.
Why did my HEIC file fail?
HEIC is Apple's format and only Safari can decode it in the browser. Chrome and Firefox have no built-in decoder, so a purely client-side tool cannot read it. Our API handles HEIC server-side — that is one of the reasons it exists. On macOS you can also convert first with Preview, or use a Safari-based tool.
Does resizing change my aspect ratio?
No. When you set a max width, the height is scaled proportionally. Images narrower than your target are left untouched rather than upscaled.
Is there a file count or file size limit?
Only your device's memory. As a practical rule, keep a single batch under about 200 MB and close other heavy tabs. Very large batches on a low-memory phone may be slow.
Guides
HEIC to JPG, without the quality loss
Why your iPhone photos won't open on Windows, and the four ways to fix it.
WebP vs AVIF vs JPEG
Real numbers on where each format wins, and when converting is a waste of time.
Why your images are slowing your site
The three mistakes behind most bad LCP scores, and how to check yours in five minutes.