Compression without an upload
Most online compressors send your file to a server. This one does not. The image is decoded into a canvas in this tab, re-encoded at the quality you choose, and handed back as a download. Nothing is transmitted, logged or stored — which makes it usable for client work and unpublished material.
Choosing quality and format
| Quality | Best for |
|---|---|
| 30–50% | Thumbnails and previews where softening will not be noticed |
| 50–70% | Listing pages and small in-page images |
| 70–88% | The usual choice for photographs on the web |
| 88–95% | Hero images and anything that will be viewed large |
WebP typically produces files 25–35% smaller than JPEG at matching quality and is supported by every current browser. Use JPEG only where something in your pipeline cannot read WebP.
Why image size decides your page speed
On most Indian small-business sites, images are the largest thing on the page by a wide margin. A homepage carrying six unoptimised 2 MB photographs will not load quickly on a mobile connection whatever else you fix.
Sensible targets for the web:
- Hero images: under 200 KB
- In-page photographs: under 100 KB
- Thumbnails and logos: under 30 KB
Resize before you compress. A 4000px photograph displayed in a 800px slot wastes most of its bytes regardless of quality setting — use the Image Resizer first, then compress.
What it will not do
Already-optimised files sometimes grow when re-encoded, because you are compressing something that has already been compressed. The tool reports this honestly rather than pretending to have saved you space — if the result is larger, keep the original.
Frequently asked questions
Does this upload my image?
No. The file is processed on a canvas inside your browser tab and never leaves your device.
What quality setting should I use?
Around 75% suits most photographs. Below 50% you will see softening on detailed images.
Should I use WebP or JPEG?
WebP for anything on the web — it is typically 25–35% smaller at the same visual quality. JPEG only where compatibility demands it.
Why did my file get bigger?
It was already well compressed. Re-encoding an optimised file usually adds bytes. Keep the original.