Skip to content
ToolShelf

Image compressor

Shrink a photo's file size in your own browser by re-encoding it at a quality you choose, with the before and after sizes side by side and the original never leaving your device.

Your image

Your image stays in this tab. The work is done by JavaScript in your browser. None of it is uploaded, logged or saved, and the tool keeps working with the network off.

How hard to squeeze

75%

Lower throws away more detail and saves more space. Around 75 is where most photographs stop looking different and the file is still much smaller.

Save as

Compressed

—

Choose an image and the compressed version appears here.

Your image does not go anywhere

There is no upload step here, and that is a fact about how the page is built rather than a promise about how it is operated. The file is read by JavaScript running in your own tab, drawn onto a canvas, encoded again, and handed back as a download. No part of it is sent to a server, because there is no code on this page that sends anything anywhere.

You can check it: load the page, turn off your network connection, and compress an image. It works exactly the same. Close the tab and the compressed version is gone too. It was only ever in memory.

What compression actually changes

The picture is re-encoded at a lower quality. A lossy encoder discards detail the eye is poor at noticing, small variations inside flat areas, fine gradations of colour, and the lower the setting, the more of it goes. The dimensions do not change. A 4,000 × 3,000 photograph is still 4,000 × 3,000 afterwards; only the file size falls.

If you want the picture physically smaller, fewer pixels, for a web page or an email, that is resizing, and it usually saves far more than quality alone. The two work well together: resize first, then compress.

Where to put the slider

Around 75 is the honest default. JPEG’s quality curve is steep at the bottom and flat at the top: below about 60 the artefacts become visible in skies and skin, and above about 85 the file grows quickly to preserve detail almost nobody can see.

It depends on the picture, though. Photographs with lots of texture hide compression well and can go lower. Flat colour, sharp edges, text and screenshots show it immediately and need a higher setting, or a different format entirely.

Why a PNG becomes a JPEG

PNG is lossless. There is no quality dial to turn down, which is exactly why it is the right format for screenshots and logos and the wrong one to ask this tool to compress.

A browser canvas can write a PNG, but its encoder is a plain one, no palette reduction, no filter search, so a PNG that has been through a real optimiser comes back larger than it went in. Rather than do that and call it compression, this converts to JPEG or WebP, which genuinely can be made smaller, and says so on the result.

If your PNG needs to stay a PNG, this is not the tool. A dedicated PNG optimiser reduces the colour count instead, which is a different technique this deliberately does not ship.

JPEG or WebP

WebP is typically 25–35% smaller than JPEG at a visually equivalent quality, and it can hold transparency. Every current browser displays it, and it is the better choice for anything going on a web page.

JPEG opens in everything, including software from decades ago, print shops, older photo frames and the occasional stubborn email client. If the file is going to someone else and you do not know what they will open it with, JPEG is the safe answer.

When the result comes out bigger

It happens, and the tool tells you when it does rather than hiding it. Two common causes: the quality is set higher than the original was saved at, so you are paying bytes to re-encode detail that has already been discarded; or the image is the sort a lossy format handles badly, where JPEG spends bytes trying to reproduce sharp edges it is not built for.

In either case the answer is the same: lower the quality, or keep the file you already had. Compressing an already-compressed image is not free, and each round trip loses a little more.

Questions

Are my images uploaded anywhere?
No. The file is read, re-encoded and handed back entirely by JavaScript running in your own browser tab. There is no upload step and no server involved, which you can verify by loading the page, disconnecting from the network, and compressing an image anyway. Nothing is stored either: close the tab and the compressed version is gone.
Does compressing change the size of the image on screen?
No. The pixel dimensions are untouched, a 4,000 × 3,000 photo is still 4,000 × 3,000 afterwards. Only the number of bytes changes. If you want the picture physically smaller, that is resizing, and doing both together usually saves far more than either alone.
What quality setting should I use?
Around 75 for most photographs. JPEG's quality curve is steep at the bottom and flat at the top: below about 60 artefacts become visible in skies and skin tones, and above about 85 the file grows quickly to preserve detail almost nobody can see. Images with flat colour, sharp edges or text show compression much sooner and need a higher setting.
Why did my PNG turn into a JPEG?
Because PNG is lossless and has no quality setting to lower. A browser canvas can write one, but its encoder is plain enough that a PNG which has been through a real optimiser usually comes back larger than it went in. Rather than do that and call it compression, the tool writes a format that genuinely can be made smaller and tells you it has.
Why is my compressed file larger than the original?
Usually because the quality is set higher than the original was saved at, so you are spending bytes re-encoding detail that has already been thrown away. The other common cause is the kind of picture: screenshots, diagrams and anything with sharp edges are expensive for a lossy format. The tool reports the growth rather than hiding it, lower the quality, or keep the file you had.
Should I choose JPEG or WebP?
WebP is typically 25 to 35% smaller at a visually equivalent quality and can hold transparency, and every current browser displays it. It is the better choice for the web. JPEG opens in absolutely everything, including much older software, so it is the safer choice for a file you are sending to someone whose setup you do not know.
Does compressing the same image twice make it smaller again?
A little, and it costs quality each time. Lossy compression is not reversible: every round trip discards more detail, and re-encoding an already-compressed image degrades it without the corresponding saving. Compress from the original where you can, and only once.
Is there a limit on file size?
25 MB per image, which is well above any normal photograph. The limit exists because the work happens in your browser's memory: a very large JPEG can decode to several hundred megabytes of raw pixels, which is enough to exhaust a tab on a phone. Files over the limit are refused with a message rather than attempted and crashed.

More tools