Free Tool Desk

JPG Compressor

Re-save a JPG at fixed quality 75 for a smaller file. Pixel dimensions stay the same, and some files do not get smaller.

Free to use No sign-up required Files deleted after processing

This tool re-saves your JPG at quality 75 and leaves the width and height alone. It suits a large photo saved at a high quality setting that has to fit an upload limit. It does little for a JPG that was already compressed hard: in our tests those files shrank only a little, and one got bigger. The worked examples below show which is which, so you can tell before you replace an original.

Accepts JPG · up to 20 MB each

Choose a file before converting.

Processing your file…

This usually only takes a moment.

Your file is ready

Download Result

Your file is processed on our server and deleted automatically afterward — see the privacy note below.

Overview

About JPG Compressor

What this compressor actually changes

Your JPG is decoded and saved again as a JPG at quality 75 out of 100. The quality is fixed: there is no slider and no target-size option. Width and height are not changed, so a 4000 × 3000 photo is still 4000 × 3000 pixels afterwards. Colour detail is stored at half resolution (4:2:0 subsampling), the usual JPG setting, which can slightly soften thin coloured lines such as red text on a white background.

Because the file is rebuilt, the embedded metadata is not carried over. Camera and date fields, GPS location and the embedded colour profile are all gone from the result. If the photo relied on an EXIF rotation flag to display upright, the rotation is applied to the pixels first, so it still looks upright without the flag. No colour conversion is applied before the colour profile is dropped, so an image in a wide-gamut space such as Adobe RGB or Display P3 can look different afterwards (see how colour profiles work).

Will my JPG get smaller? It depends on how it was saved

The quality the JPG was saved at is what predicts the result. A file saved at 90 or above has plenty to give up. A file saved near 75 or below does not. We generated one test scene, saved it at several qualities, and ran each file through this tool:

Test JPG (1200 × 800)BeforeAfter at quality 75Change
Saved at quality 95, progressive219.7 KB38.2 KB-83%
Saved at quality 92105.6 KB37.7 KB-64%
Saved at quality 8559.5 KB53.7 KB-10%
Saved at quality 6028.7 KB33.3 KB+16%
Screenshot with text, saved at quality 9085.5 KB62.7 KB-27%

Generated locally; not a benchmark; not a guaranteed result. The test images are synthetic (smooth gradients with fine noise), not camera photos, so treat the direction as the lesson and not the numbers. The quality 60 file got bigger because re-saving at 75 stores more detail than that file had. A byte-for-byte size check before you delete the original takes five seconds and avoids that trap.

Compressing the same file again

We ran this tool's own output through it again five times. For our 1200 × 800 test image the size stayed at 113,699 bytes on every pass and the pixels did not change after the first pass. On smaller test images the size moved by less than 1% between passes. The file is already at quality 75 after the first pass, so a repeat gains nothing. A JPG from a camera, a phone or another program is a different case: the first pass re-quantises it, and every re-save in any program that re-encodes JPG loses a little more. Keep the original, compress once, and avoid chains of re-saves.

When the pixel count is the real problem

Compression lowers the bytes per pixel. It cannot help if the image simply has far more pixels than it will ever be shown at. We took a 3000 × 2000 JPG (581.0 KB) and compared two routes:

RouteResult sizeDimensions
Compress only169.2 KB3000 × 2000
Resize to 1500 × 1000 only64.4 KB1500 × 1000
Resize, then compress56.4 KB1500 × 1000

Generated locally; not a benchmark; not a guaranteed result. If your photo is 6000 pixels wide and it will sit in a 1200-pixel column, start with the image resizer. If you must keep every pixel, compress alone is the right route.

Photos, screenshots and scans

JPG compression is built for photographs and smooth gradients. Screenshots, charts and scans of text are the opposite case: sharp edges produce faint speckling around letters, and the PNG version is often smaller as well. In our test the same generated screenshot was 15.5 KB as a PNG and 85.5 KB as a JPG at quality 90. If that describes your image, the JPG vs PNG vs WebP guide explains which format to keep, and the PNG to JPG converter covers the other direction.

Compatibility

Supported Formats

Accepts JPG/JPEG (.jpg, .jpeg), including progressive JPGs and grayscale JPGs. Output is a standard colour JPG at the same dimensions. PNG, WebP, GIF and other formats are not accepted here. Limits: 20 MB per file, 12,000 px per side and 40 megapixels. One file is compressed at a time.

Guide

How to Use JPG Compressor

  1. Choose a JPG (up to 20 MB). The file is identified by its contents, so a PNG renamed to .jpg is rejected.
  2. Click "Compress JPG".
  3. Download the result, named after your original with "-compressed" added. Compare its size with the original before you delete anything.

Highlights

Features

  • Fixed quality 75 Every JPG is re-saved at quality 75 out of 100. There is no slider, so the same input always gives the same output.
  • Dimensions unchanged Width and height are never altered. Pair it with the image resizer when you also need fewer pixels.
  • Repeat passes barely change it In our tests, running the tool's own output through it again changed the file size by less than 1%.

Applications

Use Cases

  • Getting a high-quality phone or camera photo under a form's upload limit
  • Trimming a batch of web images that were exported at a very high quality setting
  • Removing the camera, date and GPS fields from a photo as a side effect of re-saving it

Good to Know

Limitations

Quality is fixed at 75 and cannot be changed, and there is no way to ask for a target file size. A JPG that was already saved at a similar or lower quality may come back the same size or larger. EXIF data, GPS data and embedded colour profiles are removed. A JPG that is cut off, for example from an interrupted download, is not always rejected: in our test the readable top part came back and the rest of the picture was filled with flat grey. Check the result before you rely on it.

Files are processed on our servers and are not shared with third parties. Files are deleted as soon as processing or download finishes. Any leftover temporary file is removed automatically by our cleanup process within the configured retention period (60 minutes). See our Privacy Policy for full details.

Support

Frequently Asked Questions

Why did my JPG get bigger or stay the same size?

The file was probably already saved at a quality near or below 75. Re-saving at 75 cannot remove detail that is not there, and it can add some back. In our local test a quality 60 JPG grew by about 16%. If the result is not smaller, keep the original.

What quality does it use, and can I change it?

Quality 75 out of 100, fixed. There is no slider and no target-size option. If you need a smaller file than quality 75 gives you, reduce the pixel dimensions with the image resizer first.

Will compressing twice make the picture worse?

Running this tool's own output through it again changed the size by less than 1% in our tests, and left our largest test image byte-for-byte identical, because the file is already at quality 75. The first pass on a file from another program does change it, and so does every re-save elsewhere, so compress once from your original.

Does compressing remove EXIF and GPS data?

Yes. Camera, date, GPS and colour-profile data are not written to the result, and a stored rotation flag is applied to the pixels. If you only want the metadata gone and the picture left exactly as it is, the Image Metadata Remover does that without re-encoding.

Where is my file processed, and is it kept?

Your file is uploaded and processed on our server. It is deleted as soon as processing or the download finishes, and any leftover temporary file is removed by an automatic cleanup within 60 minutes. The Privacy Policy has the details.

Keep Going

Related Tools