No uploads. No servers. No tracking.
Compress your images
without leaving the browser.
Drop JPG, PNG, or WebP files below. Everything runs on your device — your images never touch a server.
Drop images hereTap to select images
JPG, PNG, WebP · Max 20MB each
Pick a max size
Use the slider or type a custom value. Default is 500 KB.
Drop your files
Drag images or tap to pick. Compression starts instantly. Up to 20 files.
Download
Grab files individually or as a ZIP. Nothing was ever uploaded.
More tools
Formats
JPG, PNG, and WebP. PNG is internally converted to WebP for effective compression.
Privacy
Zero network requests during compression. Open DevTools and verify — the Network tab stays empty.
Performance
Web Workers compress in the background. Three images process concurrently without blocking the UI.
Why compress images?
Images account for roughly half of the average web page's total weight. A single uncompressed photograph from a modern phone camera can easily exceed 5 MB — enough to add several seconds to page load times on mobile connections. Compressing images reduces file size while preserving visual quality, which directly improves page speed, user experience, and search engine rankings.
Google's Core Web Vitals, particularly Largest Contentful Paint (LCP), penalize pages that take too long to render their main visual content. Oversized hero images are one of the most common causes of poor LCP scores. Compressing a 4 MB hero image down to 200 KB can shave multiple seconds off load time and push a page from "needs improvement" into the "good" range.
Common scenarios where compression helps
- E-commerce product images — Online stores often have hundreds of product photos. Compressing each to under 200 KB keeps category pages fast and reduces bandwidth costs.
- Blog and editorial images — Articles with multiple photos benefit from compression to keep total page weight under 1 MB, improving readability on slow connections.
- Email attachments — Many email providers cap attachments at 25 MB. Compressing a batch of vacation photos to 500 KB each lets you send more in a single email.
- Social media uploads — Platforms like Instagram and Twitter re-compress images on upload, often aggressively. Pre-compressing to a reasonable size gives you more control over the final quality.
How browser-based compression works
This tool uses the HTML5 Canvas API and Web Workers to compress images entirely on your device. When you drop an image, a Web Worker decodes it, draws it onto an off-screen canvas, and re-encodes it as a JPG or WebP at progressively lower quality levels until the file fits under your target size. Three images process concurrently for speed, while the main thread stays responsive.
Because everything runs in your browser, there are no upload queues, no file size limits imposed by a server, and no risk of your images being stored on third-party infrastructure. This makes client-side compression ideal for sensitive documents, client deliverables, or any workflow where privacy matters. Open your browser's Network tab during compression and you'll see zero outbound requests — that's the guarantee.
FAQ
- Are my images safe?
- Yes. Compression uses the Canvas API and Web Workers inside your browser. Nothing leaves your device. Check the Network tab in DevTools to verify.
- What happens with PNG files?
- PNG is lossless, so quality-based compression doesn't work. PNGs are internally compressed as WebP to hit the target size, then saved with the original .png extension.
- What if my file ends up smaller than the max size I set?
- The max size is an upper limit, not an exact target. The compressor reduces quality until the file fits under that limit, so results are often well below it. If the file is already smaller, it's returned as-is.
- How many files at once?
- Up to 20 images, max 20MB each. Three compress concurrently to balance speed and memory.
- Mobile?
- Yes. Tap the upload area to pick images. Compression runs in the background.