Your files never leave your device
Compression happens in your browser using the Canvas API. Nothing is uploaded, stored or logged, which matters for client work, ID documents, screenshots of private dashboards and anything under an NDA.
Image Tool
Compress JPG, PNG and WebP images up to 90% smaller without visible quality loss. Everything runs inside your browser — your files are never uploaded, so there is no queue, no watermark and no size limit imposed by a server.
Compressed files keep their original name with a size suffix. Location data and other EXIF metadata are removed automatically.
Most online image compressors send your photos to a server, process them in a queue, then hand back a download link that expires. This one never transmits a single byte.
Compression happens in your browser using the Canvas API. Nothing is uploaded, stored or logged, which matters for client work, ID documents, screenshots of private dashboards and anything under an NDA.
Set a limit like 100 KB and the tool runs a binary search across quality levels to find the sharpest version that still fits. Most competitors only offer a blunt quality slider.
Queue up to twenty images and watch each one report its before size, after size and percentage saved, plus a running total for the whole batch.
Downscaling a 6000 px photo to 1920 px usually saves more than any quality setting can. Set a max width once and it applies to the whole batch.
Convert JPG and PNG to WebP in the same pass for a further 25–35% reduction, with automatic fallback to JPG on browsers that cannot encode it.
No account, no daily cap, no email wall and no watermark stamped on the output. Because there is no server doing the work, there is nothing to meter.
Four steps, no upload wait, and the result downloads straight to your device.
Format choice usually saves more than the quality slider does. Match the format to the content.
| Format | Best for | Transparency | Typical saving |
|---|---|---|---|
| JPG | Photographs, complex scenes, anything with gradients and no flat edges. | No | 60–85% from an unoptimised camera file |
| WebP | Almost everything on the modern web. Handles photos and graphics equally well. | Yes | A further 25–35% over an equivalent JPG |
| PNG | Logos, icons, screenshots with text, and any image needing a transparent background. | Yes | Mostly from resizing — PNG is lossless |
JPG and WebP are lossy: they discard visual information the eye is unlikely to notice, which is why they shrink so dramatically. PNG is lossless — every pixel survives, so the only real saving comes from reducing dimensions or colour depth.
This is why a screenshot saved as PNG can be 2 MB while the same screenshot as WebP is 120 KB with no visible difference.
Between 100% and about 85% quality the file shrinks a lot and the image looks identical. Between 85% and 70% the savings continue and most people still see no difference on screen. Below roughly 55% you start seeing blocking around sharp edges and banding in skies.
Compressing an already-compressed JPG again always costs quality, so work from the original file whenever you can.
Images are typically the heaviest thing on a web page and the most common reason a page fails a Core Web Vitals assessment.
Work out your export dimensions first with the aspect ratio calculator, then compress here. If you are matching brand colours across assets, the colour converter handles HEX, RGB and contrast checks.
Clearing space rather than publishing? Our guides on doing a digital declutter and backing up your computer pair well with a compression pass, and cloud storage explained covers where to put the results.
What people ask most before compressing photos online.
Lossy compression does discard data, but between 100% and roughly 80% quality the loss is invisible at normal viewing sizes while the file often shrinks by more than half. PNG compression is lossless, so quality is untouched and savings come from resizing instead. If you need pixel-perfect fidelity for print or archival, keep the original file and compress a copy.
No. Every step runs locally in your browser through the HTML Canvas API. Your images are read from disk into memory, re-encoded, and offered back as a download. Nothing is transmitted, stored or logged anywhere, and the tool continues to work if you disconnect from the internet after the page has loaded.
Switch the mode to Target file size and enter your limit in kilobytes. The tool encodes the image repeatedly at different quality levels, narrowing in on the highest quality that still fits under your cap. If the target cannot be met at the current dimensions, set a max width as well — reducing pixels is far more effective than pushing quality below 40%.
There is no server-side limit because there is no server. The practical limit is your device memory: twenty images per batch keeps things comfortable on a phone, while a desktop handles very large files easily. Extremely large images, above roughly 8000 pixels on a side, may be downscaled by the browser itself on mobile.
Yes, automatically. Re-encoding through a canvas produces a clean file containing only pixel data, so GPS coordinates, camera model, timestamps and any other metadata are stripped. That is useful before posting photos publicly, though it also means you should keep your originals if you rely on that information.
For anything published on the web, yes. WebP typically produces files 25–35% smaller than JPG at matched visual quality and supports transparency. Every current browser supports it. Stick with JPG only when a specific platform or application refuses WebP uploads, which is still occasionally the case with older CMS installations and some print services.
PNG is a lossless format, so the quality slider has no effect on it. Savings come only from reducing dimensions or from converting to a lossy format. If your PNG is a photograph, switching the output format to WebP or JPG will usually cut it by 80% or more. If it is a logo or screenshot with transparency, set a max width and keep WebP to preserve the alpha channel.
Yes. The tool is built mobile-first, and tapping the drop zone opens your photo library directly. Because processing happens on the device, a large batch will take longer on a phone than on a laptop, and very large batches may be limited by available memory. Compressing in groups of five to ten works reliably on most handsets.
Drop in a batch, pick a target, and download files that load faster everywhere — without handing your photos to anyone.
Compression is irreversible. Always keep a copy of your original files before replacing them with compressed versions, particularly for photographs you may want to print or edit later.