Batch-shrink JPEG, PNG and WebP photos directly in your browser. Convert to WebP or AVIF, resize for web, email or social — and your files never leave this device.
📸
Need images to start with?
Browse millions of high-resolution stock photos and illustrations with commercial licenses — then squeeze them here before publishing.
Explore stock libraries →
🎨
Design before you compress
Create social graphics, thumbnails and banners in a drag-and-drop editor, export, then run them through SqueezeIMG for the smallest files.
Try a design tool free →
📄
Working with PDFs too?
PDFLocal merges, splits, compresses and watermarks PDF files with the same promise: everything stays on your device.
Open PDFLocal →
⚡
SqueezeIMG Pro license key
Everything here stays free. Pro adds quality-of-life for heavy users: saved preset profiles (web / email / social one-click), AVIF batch presets, folder drag-in with structure preserved in the ZIP, and priority support. One-time license key — no subscription, still 100% in-browser.
Get the free Image Optimization Checklist
A 12-point pre-publish checklist (formats, sizes, lazy-loading, CDN tips) used by indie site builders to pass Core Web Vitals. Join the list and we'll send it over.
Send me the checklist
How image compression works (and why it stays on your device)
SqueezeIMG uses your browser's built-in image codecs — the same encoders Chrome, Edge, Firefox and Safari use to render the web — to decode each picture onto an off-screen canvas and re-encode it at the quality you choose. Because the work happens in JavaScript inside your own tab, nothing is uploaded to any server. There is no queue, no per-file size limit, and no "free tier" counting your conversions. You can verify this yourself: load the page, switch off Wi-Fi, and compression keeps working.
Most images shrink dramatically because cameras and screenshots are saved far more conservatively than the web needs. A 12-megapixel phone photo is typically 3–5 MB, yet the largest version any website displays is usually under 400 KB. Two levers do the heavy lifting: re-encoding (modern formats like WebP and AVIF store the same visual detail in fewer bytes) and resizing (a 4000-pixel-wide photo shown in a 800-pixel column wastes ~96% of its pixels).
Which format should I pick?
| Format | Best for | Typical savings vs. original* | Browser support (2026) |
|---|
| WebP | Photos, screenshots, UI images — the safe default | 25–45% smaller than JPEG, 60–80% smaller than PNG photos | ~98% of browsers in use |
| AVIF | Hero images and photo-heavy pages where every KB counts | 40–60% smaller than JPEG at similar quality | ~94% of browsers; canvas encoding only in Chromium-based browsers |
| JPEG | Maximum compatibility (old email clients, legacy CMSs) | 30–70% smaller than camera originals at quality 80 | Universal |
| PNG | Logos, line art, images that must stay pixel-perfect | Varies — lossless; resize is where PNG savings come from | Universal |
*Savings are estimates based on typical photographic content at quality 80 in 2026-era browser encoders; your results depend on image content, dimensions and the quality slider.
Recommended settings by use case
- Website images: WebP, quality 80, max width 1920 px (or 1600 px for blog content). Aim for under 200 KB per image.
- Email attachments: JPEG, quality 75, max width 1280 px — keeps a 20-photo batch under most 25 MB inbox limits.
- Social media: JPEG or WebP, quality 85, max width 1080 px — platforms re-compress anyway, so don't ship more pixels than they keep.
- Archiving with privacy: any format with Strip metadata on — removes GPS coordinates, camera serial numbers and timestamps embedded by phones.
Frequently asked questions
Are my images really not uploaded anywhere?
Correct. SqueezeIMG is a static page — there is no backend to receive your files. Images are read with the browser's File API, processed on a local canvas, and offered back as downloads, all in your tab's memory. You can run it offline once the page has loaded.
Why is my "compressed" file sometimes bigger?
If an image was already aggressively optimized (or is a tiny icon), re-encoding can add bytes. With Strip metadata turned off, SqueezeIMG automatically keeps the original file whenever the re-encode would be larger, so you never lose ground. With it on, the re-encode is always used because removing EXIF data requires rewriting the file.
What does the quality slider actually do?
It controls how much detail the lossy encoder preserves. At 100 the encoder keeps nearly everything (large files); at 80 it discards detail that's mostly invisible to the eye; below 60 you'll start to see softness and blocking in flat areas. Use the Compare button on any result to inspect a side-by-side view with a zoom loupe before committing.
Why is AVIF greyed out in my browser?
Every modern browser can display AVIF, but only Chromium-based browsers (Chrome, Edge, Brave, Opera) currently expose AVIF encoding to web pages. SqueezeIMG detects this on load and enables the option when your browser supports it. WebP encoding works everywhere.
Does stripping EXIF reduce file size?
A little — metadata is usually 10–60 KB per photo — but the real benefit is privacy: phone photos embed GPS location, device model and capture time. Any image re-encoded through a canvas loses all of that automatically, which is why the toggle is on by default.
Is there a limit on batch size?
No artificial one. Practical limits come from your device's memory — hundreds of phone photos in one batch is fine on a typical laptop. Files are processed one at a time to keep memory use flat, and the ZIP is assembled locally with JSZip.