Does a JPEG lose quality every time you save it? The same file saved 20 times
The converter opens on PNG: turn a picture into a PNG before you edit it, and saving it again changes nothing. Below, what 20 JPEG saves in a row did to a photo and a screenshot. Nothing is uploaded.
Convert toKeeps transparency. Best for diagrams and logos
PNG keeps transparency and loses nothing, so there is no quality setting.
Drag and drop your images
or click to choose · Ctrl+V to paste (up to 30, 50MB each)
JPEGPNGWebPAVIFGIFBMPSVGHEIC/HEIFTIFF
Everything runs in your browser. Your images are never sent to a server.
You only cropped it, or only turned it the right way up, and the picture looks a little worse. The crop is not the cause. The save is. A JPEG is compressed again every time it is saved as a JPEG, and that compression touches the whole picture, not just the part you changed. This article gives what we found when we saved the same JPEG 20 times in a row, and how to edit without the loss.
Editing does not lose quality. Saving as JPEG does
Cropping keeps a part of the pixels. Turning a picture by 90 or 180 degrees, or flipping it, moves pixels without changing their colours. None of these lowers the quality by itself. Opening, viewing, copying or renaming a JPEG does not change a pixel either.
JPEG is a lossy format: to make the file small it throws a little away each time it is written. When a picture that is already a JPEG is written as a JPEG again, it goes through that compression a second time, and the new errors land on top of the old ones, all over the picture.
PNG is lossless. Saving a PNG changes no pixel: when we cropped a PNG to its full size and saved it, not one of its 480,000 pixels came out different. (That figure is from the measurement behind this article's Japanese version, made in a browser; the table below is a separate measurement.)
Measured: the same JPEG saved 20 times in a row
How we measured: two 800×600 pictures, a photograph scaled down and kept lossless, and a drawn screenshot (a white page with grey panels and dark text). Each was saved as a JPEG at quality 92, then that JPEG was opened and saved again at the same quality, with no edit in between, 20 times. We used the image library sharp (libjpeg-turbo, 4:2:0 colour). After every save we compared each pixel's red, green and blue values (0 to 255) with the original and with the save before (2 November 2026). Browsers and apps use other encoders and settings, so read the numbers as orders of magnitude, not as what your app will do.
The first save did most of the damage. For the photo, the average difference from the original was 1.86 after one save and 2.19 after twenty: the first save was 85% of the total. For the screenshot it was 0.51 and 0.75, 68% on the first save.
Each save after that changed fewer pixels. The first save changed 94.6% of the photo's pixels; the second changed 23.5%, the fifth 9.4%, the tenth 3.0% and the twentieth 0.8%. Saving again at the same quality settles towards what the encoder already wrote, so most pixels stop moving.
But it never quite stopped, and the worst pixels kept drifting. The largest single difference from the original grew from ±34 after one save to ±47 after ten and ±63 after twenty for the photo, and from ±52 to ±72 for the screenshot. Those are a few pixels at sharp edges; the average barely moved. So the answer to "every time?" is yes, by less each time.
The file did not get smaller in return. The photo was 152.5KB after the first save and 152.2KB after the twentieth (1KB = 1,024 bytes).
A photo saved again and again (JPEG quality 92, measured)
Save
Pixels changed by this save
Average difference from original
Largest difference
PSNR
1
94.6%
1.86
±34
39.7 dB
2
23.5%
1.92
±39
39.3 dB
3
16.6%
1.97
±39
39.0 dB
5
9.4%
2.05
±43
38.5 dB
10
3.0%
2.14
±47
37.8 dB
20
0.8%
2.19
±63
37.3 dB
A screenshot saved again and again (JPEG quality 92, measured)
Save
Pixels changed by this save
Average difference from original
Largest difference
PSNR
1
51.1%
0.51
±52
45.4 dB
2
10.3%
0.60
±60
44.0 dB
3
7.8%
0.65
±63
43.3 dB
5
3.9%
0.70
±67
42.5 dB
10
0.4%
0.74
±70
42.0 dB
20
0.1%
0.75
±72
41.8 dB
"Pixels changed by this save" compares each save with the one before. The other columns compare it with the original. Differences are per colour value on a 0 to 255 scale; a higher PSNR means closer to the original.
How to edit without the loss
Keep the original, and when you redo an edit, start again from it rather than from your last export. Do all the edits in one go if you can, so the picture is saved once.
Work in PNG until the last step. The converter at the top of this page opens on PNG: drop a JPEG in, edit the PNG, and save as JPEG only once at the end, if you need a small file. Turning a JPEG into a PNG does not bring back what the JPEG already lost; it only stops further loss. A PNG of a photo is also much larger.
What this site's tools do: the crop, rotate, pixelate, watermark and grayscale tools write a JPEG back as a JPEG and a WebP as a WebP, so a JPEG put in is saved as a JPEG once. A PNG put in comes out as a PNG, with no loss. Four cases always save a PNG instead, which adds no loss: the grayscale tool's two-tone (black and white only) style, a rotation with the blank corners kept transparent, a circular crop, and transparent borders added to reach a ratio. An iPhone HEIC photo is saved as a JPEG, because browsers cannot write HEIC, so editing one costs one JPEG save; convert it to PNG first to avoid that.
Frequently asked questions
Does a JPEG lose quality every time you save it?
Yes, every time it is saved as a JPEG again, but most of the loss happens on the first save. We saved a photo 20 times in a row at quality 92: the first save accounted for 85% of the average difference from the original that 20 saves produced. Each later save changed fewer pixels (94.6% on the first, 23.5% on the second, 3.0% on the tenth), but it never stopped, and the largest single difference kept growing, from ±34 to ±63 on a 0 to 255 scale.
Does opening or copying a JPEG lose quality?
No. Opening, viewing, copying or renaming a JPEG does not change a single pixel. The loss happens only when a program saves it again as a JPEG.
Does cropping reduce image quality?
Cropping itself does not: it only keeps a part of the pixels. What costs quality is saving the result as a JPEG, which compresses the whole picture again, including the parts you did not touch. Saved as a PNG, a crop of the whole picture came out with not one of its 480,000 pixels changed.
Does saving at the same quality stop the loss?
It slows it, but it does not stop it. At the same quality 92, the share of pixels that changed fell with every save (for our screenshot, 51.1% on the first save, 0.4% on the tenth), but after 20 saves some pixels were still moving.
Does the file get smaller each time I save it?
Hardly. Our photo was 152.5KB after the first save and 152.2KB after the twentieth. Saving again costs quality without saving space.
Does converting a JPEG to PNG bring the quality back?
No. A PNG keeps exactly what it is given, so a JPEG turned into a PNG keeps the JPEG's losses. Converting to PNG is worth it before editing, because from then on saving changes nothing.
Is my image uploaded when I use these tools?
No. The converter, and the crop, rotate, pixelate, watermark and grayscale tools, open and save the image inside your browser; nothing is sent to a server.
The tool at the top of this page is theimage converter; it runs in the browser, and nothing is uploaded. When to choose PNG and when JPEG is measured in PNG vs JPG.