Compress Images
Reduce JPEG, PNG, WebP and SVG file sizes directly in your browser. Nothing is uploaded — ever.
Drop your images here
JPG · PNG · WebP · SVG
Free · No account required · No upload · Processes entirely in your browser
Three steps. Under 30 seconds.
Drop your file
Loads into browser memory. Nothing transmitted.
WebAssembly runs on your CPU
Compression happens locally. No server involved.
Download and done
Saved to your device. Cleared from memory on close.
What is image compression and why does it matter?
Image compression reduces the file size of an image by discarding or encoding redundant pixel data more efficiently. A photo from a modern smartphone can be 6–15 MB — far too large for most web, email, or social media use. Compressing it brings the file size down to 200 KB–1 MB while keeping the image visually indistinguishable from the original at screen sizes.
For websites, image compression is one of the highest-impact performance optimisations available. Images are typically the largest assets on a web page, and their file size directly affects how fast the page loads — which affects Google search rankings through Core Web Vitals (LCP).
When to compress images — and why
- Websites and landing pages. Every extra kilobyte increases page load time. A 3 MB hero image compressed to 200 KB loads 15× faster, and Google notices. Compress every image before uploading to your CMS.
- Email attachments. Gmail limits attachments to 25 MB; Outlook.com to 20 MB; many corporate mail servers to 10 MB. A batch of uncompressed photos can easily exceed those limits. Compressing first makes attachments send reliably.
- Social media uploads. Instagram, Facebook, and X recompress images on upload, often degrading quality. Uploading a pre-compressed image gives you control over the final quality the platform outputs.
- E-commerce product photos. Shopify, WooCommerce, and Amazon require fast-loading product images. Compressing photos reduces page load time, lowers bounce rate, and improves conversion.
- App and game assets. Sprite sheets, backgrounds, and UI textures must be compact to minimise load time and memory usage on mobile devices.
JPEG, PNG, WebP, SVG — which format?
The right format depends on the image type and intended use.
| Format | Best for | Transparency | Typical reduction |
|---|---|---|---|
| JPEG | Photos, gradients, complex imagery | No | 60–80% |
| PNG | Logos, icons, screenshots, transparency | Yes | 40–70% |
| WebP | Web delivery — replaces JPEG and PNG | Yes | 25–35% vs JPEG |
| SVG | Icons, logos, diagrams (vector only) | Yes | 10–50% |
Your files never leave your browser.
Most online tools upload your file to a server, process it remotely, then send it back. This tool is architecturally different — compression runs via WebAssembly on your CPU. There is no server that receives your image. Not even temporarily.
- No file data transmitted over the network at any point
- No account, sign-in, or email required to use any feature
- Closing the tab clears all data from browser memory completely
- Open-source processing: Canvas API and pngquant WASM
Choosing the right quality setting
The quality slider controls how aggressively the encoder discards image data. Higher quality preserves more detail; lower quality produces smaller files.
| Quality range | Best for | Typical reduction |
|---|---|---|
| 85–100 | Print, archival, source files for future editing | 10–30% |
| 75–85 | Web images, blog posts, social media | 50–75% |
| 60–75 | Email attachments, preview thumbnails | 65–80% |
| Below 60 | Small thumbnails where size is the only priority | 75–90% |
How the compressor works
- JPEG and WebP Compressed using the browser's native Canvas API encoder. The quality slider maps directly to the encoder's quality parameter, controlling how aggressively DCT coefficients are quantised.
- PNG Uses pngquant compiled to WebAssembly — the same algorithm behind TinyPNG. It reduces the colour palette from 16.7 million (24-bit) to up to 256 colours, achieving 40–70% reduction with near-invisible quality loss.
- SVG Compression strips XML comments, metadata, and unnecessary whitespace from the source file. Paths, dimensions, and rendering instructions are preserved exactly.
- Nothing leaves your device. All compression runs locally in your browser. Files are never transmitted to any server at any stage of the process.