Optimize Image Tools
Compress JPG, PNG and WebP images to shrink file size without losing quality.
Images are usually the heaviest thing on a web page and the reason email attachments bounce. A photo straight off a modern phone is routinely 4-8 MB, while the same picture at a quality nobody can tell apart is often under 500 KB. Compression is what closes that gap: it re-encodes the image so it stores the same picture using fewer bytes, trading detail your eye does not notice for size your connection definitely does.
Where to start
- Compress Image
- A photo is too large to email, too slow on a web page, or over an upload limit — and it needs to stay the same dimensions.
- Resize Image
- The image is far larger than it will ever be displayed. Shrinking 4000px to 1600px saves more than any compression setting.
- JPG to WebP
- You control the website it will appear on. WebP typically lands 25-35% smaller than JPG at the same visual quality.
- PNG to JPG
- A photograph got saved as PNG. PNG is the wrong format for photos and often 5-10x larger than it needs to be.
Resize first, then compress
This is the single biggest win and the step people skip. File size scales with pixel count, so halving both dimensions removes about three quarters of the pixels before compression has done anything at all. If an image will be displayed 800 pixels wide, there is no reason to ship 4000 pixels of it — the browser just throws the extra away after downloading it. Resize to roughly twice the display size to stay sharp on high-density screens, then compress. Doing it in the other order wastes the compression work.
Choosing a quality setting
JPG quality is a scale, not a switch. Somewhere between 75 and 85 is the range where almost nobody can pick the compressed version out of a line-up, and where the savings are steepest — dropping from 100 to 85 often halves the file for no visible change. Below about 60, flat areas start to band and sharp edges pick up halos. Photographs tolerate aggressive compression well; screenshots, diagrams and anything with small text do not, because JPG's artefacts cluster exactly around hard edges. Compress those as PNG or WebP instead.
PNG for photographs is the most common mistake
PNG is lossless, which sounds strictly better and is why so many photos end up saved as PNG. But lossless means it must store every pixel exactly, and photographs have millions of subtly different pixels, so PNG has almost nothing to compress. The result is a file five to ten times larger than a JPG nobody could distinguish from it. Keep PNG for logos, icons, screenshots, line art and anything needing transparency — images with large areas of flat, identical colour, which is what PNG is genuinely good at.
Why smaller images matter beyond convenience
Page weight is a ranking and revenue issue, not just an aesthetic one. Google measures Largest Contentful Paint — how long the biggest visible element takes to appear — and on most pages that element is an image. A visitor on a phone with a weak signal will often abandon a page before an oversized hero image finishes loading. Compression is the cheapest performance work available: no code changes, no infrastructure, just smaller files.
Frequently asked questions
How much smaller can I expect the file to get?
For a typical phone photo, 60-80% smaller with no visible difference is normal, and more if you resize first. Images that are already compressed, or that are mostly noise or fine texture, compress far less.
Does compressing lose quality?
Lossy compression discards some detail by definition. At sensible settings the difference is invisible at normal viewing size, but it is permanent — so compress a copy and keep the original if the image might need editing later.
Can I compress the same image twice?
You can, but each pass re-encodes what the previous pass already degraded, and the artefacts compound. Go back to the original and compress once at the setting you want instead.
Is my image uploaded to be compressed?
No. Compression runs in your browser, so the file never leaves your device. That also means there is no size limit imposed by a server — only what your own machine can handle.