Batch compress photos and videos to a target file size, with live progress and ZIP download — all processed inside your browser, so your files never leave your device.
Images are re-encoded as JPG (transparency is filled white). Videos are re-encoded as WebM and processed in real time — audio is not kept. See the guide below for details.
Most online compressors upload your photos and videos to someone else's server. Ours doesn't — every file is read, re-encoded and saved inside your browser.
Don't take our word for it. Open DevTools, switch to the Network tab, and compress a file. You'll see zero upload requests. Or disconnect your Wi-Fi and try again — it still works.
This image compressor re-encodes your files using your browser's own canvas and media APIs. Nothing is sent anywhere, so there's no upload wait and no file size cap.
Every compressor site claims to be private. The claim is worth nothing unless you can verify it, and you can, in about twenty seconds:
F12 to open DevTools and click the Network tab.The stronger test: disconnect your internet after the page has loaded, then compress. A server-based tool dies instantly. This one keeps working, because the compression code is already running on your machine.
Why this matters: uploaded photos carry EXIF metadata — GPS coordinates, camera serial, timestamp. When a tool processes files on its own servers you're trusting a stranger's retention policy with all of it. Here, the canvas re-encode strips that metadata as a side effect, and the original never leaves your device anyway.
Job portals, government forms and university applications love hard limits — "photo must be under 200KB". Switch Mode to Target Exact Size, type your limit, choose KB or MB, and drop the file in.
The tool runs a binary search across JPEG quality levels, encoding repeatedly until it finds the highest quality that still fits under your target. That's usually eight passes, and it happens fast enough that you won't notice.
Two things to know. If your target is very small for a very large photo — say 20KB for a 12-megapixel image — the tool returns the smallest it can produce, which may still exceed the target, because it reduces quality but not dimensions. And the result is always JPG, so if you need PNG or transparency this mode isn't for you.
| Quality slider | Target exact size | |
|---|---|---|
| You control | Visual quality | File size |
| Result size | Varies per image | Predictable |
| Batch behaviour | Same quality, different sizes | Every file under the same cap |
| Speed | One pass | Up to eight passes |
| Best for | Web images, bulk optimisation | Forms and portals with a hard limit |
For general web use, 75–85% on the slider is the sweet spot. Below about 60% you start seeing blocky artefacts around sharp edges and text. Above 90% the file grows fast for a difference nobody can see.
| Format | Best for | Transparency | Typical size |
|---|---|---|---|
| JPG | Photographs, anything with gradients | No | Baseline |
| PNG | Logos, screenshots, flat graphics, transparency | Yes | Much larger for photos |
| WebP | Almost everything on the modern web | Yes | ~25–35% smaller than JPG |
A common mistake is saving photographs as PNG. PNG is lossless, so a photo stays enormous — often five to ten times a JPG of the same visual quality. Save photos as JPG or WebP; keep PNG for graphics with hard edges or transparency.
This tool outputs JPG, which means a transparent PNG will come out with a white background. If you need to keep transparency, don't compress it here.
Being straight about this, because most tools aren't. Browser-based video compression uses the MediaRecorder API, which has real limits:
So this is right for quickly shrinking a screen recording or a silent clip for a web page. It's the wrong tool for a video with dialogue or music.
Images are typically 50–70% of a page's total weight, which makes them the biggest single lever on load speed. Google measures that through Core Web Vitals, and those feed into ranking.
width and height attributes too.A practical target: keep hero images under 200KB and in-content images under 100KB. Serve WebP where you can, and lazy-load anything below the fold.
The other tabs handle everyday file conversions, all in the same browser-only way:
.xlsx workbook with a preview of the first rows before you download..xlsx or .xls file as clean CSV, useful for imports that reject Excel files..docx, with blank lines becoming new paragraphs and an optional title heading.All four read only the first sheet and treat the first row as headers. For multi-sheet workbooks, save each sheet separately first.
No. Everything runs in your browser using the canvas and MediaRecorder APIs. You can verify it by opening DevTools' Network tab while compressing, or by disconnecting your internet and trying again — the tool still works.
No. Because there's no server, there's no upload cap and no daily quota. The only real constraint is your device's memory, so very large batches on an older phone may be slow.
Switch Mode to Target Exact Size, enter 200 and leave the unit on KB, then drop your image in. The tool tries multiple quality levels and keeps the best one that fits under your limit.
Browser-based compression captures the video canvas only, so audio isn't included. This is a limitation of the underlying API, not a setting. For videos that need sound, use a desktop encoder such as HandBrake.
The MediaRecorder API records in real time, so a five-minute video takes about five minutes. The progress bar shows exactly where it is. Leave the tab open and in the foreground while it works.
Output is JPG, which has no alpha channel, so transparent areas are filled with white. That's intentional — JPG is far smaller for photos. If you need transparency, keep the original PNG.
Yes. Re-encoding through canvas produces a fresh image without the original metadata, so location, camera model and timestamps are stripped. Useful before sharing photos publicly.
JPEG compression is lossy, so some data is discarded. At 80% quality the difference is invisible to the eye on most photographs. Below roughly 60% you'll start noticing artefacts around sharp edges and text.
Check the copy length on your page with the word counter and keyword density checker, style headings using the bold text generator, or see how the finished page renders on phones with the responsive design checker.