Compress an image and see the quality before you download

Shrink a photo and watch the quality change on a drag-to-compare slider. Measures JPG against WebP on your own image, and admits when a file cannot get smaller.

๐Ÿ”’ Runs in your browser

The number is not the point. The picture is.

Every compression tool gives you a slider and a file size. Almost none of them let you see what the slider is actually doing to your photograph.

So people pick a number that sounds safe, download it, and only discover the damage later โ€” after it has been uploaded, printed, or sent.

Here the original and the compressed version sit in exactly the same place, and you drag a divider between them. Skies band. Skin goes blotchy. Text edges fur up. All of it is visible before you commit, at the setting you are actually considering.

That is the whole design. Two thumbnails side by side would not work, because at thumbnail size every setting looks fine.

When a file cannot get smaller, this says so

A photograph from a decent camera app has already been compressed once, and most of the redundancy is gone. Re-encode it at high quality and the result can be larger than the original โ€” you are spending new bytes to describe the previous compression's artefacts.

Most tools hide this. They hand back a file named "compressed" and report a saving of zero percent, or quietly return your own file with a new name.

This one tells you the image is already efficient, shows you what it would take to actually go lower, and says plainly that downloading the result would make your file worse. A tool that will not admit failure cannot be trusted when it claims success.

WebP, measured on your image rather than asserted

WebP typically lands 25 to 35 percent below JPEG at matched visual quality. That is a well-known average, and averages are not much use when you have one specific photo in front of you.

So both formats are encoded and weighed, and the real difference for your image is put on screen. Usually WebP wins. Occasionally, on a small or already-optimised JPEG, it does not.

โš ๏ธ WebP is offered, never chosen for you. Some government and exam portals still accept JPG only, and a rejected upload costs far more than the kilobytes saved.

It removes your location data

This is a side effect rather than a feature, but it is worth knowing.

Re-encoding through the browser discards all EXIF metadata. On most phones that includes the GPS coordinates of where the photo was taken, the device model, and the exact timestamp. If you are about to post a picture publicly, that matters.

It also means the orientation tag is discarded, which is why this tool reads the orientation before re-encoding โ€” otherwise portrait photos would silently come out sideways.

What this does not do

  • It does not resize. The pixel dimensions stay exactly as they were. If a form demands specific dimensions as well, use resize a photo to exact pixels and file size.
  • It cannot make an already-optimised file meaningfully smaller without visible loss, and it will tell you so rather than pretending.
  • It does not open HEIC. Convert an iPhone photo with HEIC to JPG first.

This tool runs entirely inside your browser. Your file is never uploaded โ€” it never leaves your device, so there is nothing for us or anyone else to read, store or leak.

Common questions

Why did my file get BIGGER instead of smaller?

Because it was already compressed. A JPEG straight from a decent camera app has usually had most of the redundancy squeezed out of it, and re-encoding at high quality adds new compression artefacts while spending bytes to describe the old ones. Compressing twice does not halve the size - it can grow it. This tool tells you when that happens rather than handing back a bigger file labelled as smaller.

Should I use JPG or WebP?

WebP is usually 25 to 35 percent smaller at the same visible quality, and every browser released since 2020 supports it. But some government and exam portals still accept JPG only, and a rejected upload costs more than a few kilobytes saved. This tool encodes both and shows you the real numbers for your specific image, so the decision is made on facts rather than a rule of thumb.

How much quality can I lose before it matters?

Far more than most people expect, and the honest answer is that it depends on the picture. Flat areas like skies and skin show compression first; busy detail like foliage hides it. That is exactly why the comparison slider is the main feature here - a quality number is meaningless on its own, and the only reliable test is looking at your own image at the setting you are considering.

Does this remove the location data from my photo?

Yes, as a side effect. Re-encoding through the browser canvas discards all EXIF metadata, and on most phones that includes the GPS coordinates of where the photo was taken, along with the device model and timestamp. If you are about to post a photo publicly, that is a real privacy benefit worth knowing about.

It still will not fit under my limit. What now?

Reduce the pixel dimensions instead of the quality. Beyond a point, lowering quality destroys the image while barely moving the file size, because you are fighting the compressor rather than working with it. Halving the width and height removes three quarters of the pixels and costs far less visible quality than the equivalent saving from quality alone.

Written and maintained by Mustak Momin ยท Last reviewed