
Photo by Kawê Rodrigues on Pexels
Quick answer
Yes — converting to JPG applies lossy compression, which permanently discards some image data. At 80–90% quality the difference is invisible to most people. For images with transparency, text, or sharp edges, the quality loss is more noticeable. And no: converting JPG to PNG does not improve quality. That data is already gone.
Does converting to JPG reduce quality? Yes, technically — but the more useful answer is: it depends on what you are converting, and at what quality setting. Converting a photograph to JPG at 80% quality produces a file that is 60–70% smaller with no visible difference. Converting a logo with sharp text to JPG at any setting produces blocky artifacts around every edge.
There is also a question most people ask backwards: they convert JPG to PNG hoping to recover quality, and wonder why it did not work. It never works. This post covers both directions and everything in between.
What happens to quality when you convert to JPG

Photo by Michael Burrows on Pexels
JPG uses lossy compression. When you convert an image to JPG, the encoder analyzes the pixel data, identifies details that the human visual system is least sensitive to, and discards them. The higher the quality setting, the less it discards. The decision is permanent — the discarded data cannot be recovered.
This is why converting to JPG always technically reduces quality. But "technically" is doing a lot of work in that sentence. At 80% quality, the discarded information is the kind of subtle frequency data in smooth gradients that virtually no viewer can detect on a screen. At 40% quality, the discarded information includes color accuracy in high-contrast edges, and the characteristic blocky JPEG artifacts become visible.
The quality loss from converting a photograph to JPG at 80% is invisible to most people. The quality loss from converting a logo with white text on a dark background to JPG at 80% is immediately obvious. Same compression method, completely different results — because the image content determines how much the compression hurts.
| Image type | JPG quality loss at 80% | Recommended format |
|---|---|---|
| Photograph | Invisible | JPG or WebP |
| Illustration with gradients | Minimal | JPG or WebP |
| Logo or icon | Noticeable (edge artifacts) | PNG or SVG |
| Screenshot with text | Visible (blurry text) | PNG |
| Image with transparency | Transparency destroyed | PNG or WebP |
When the quality loss is invisible
For photographs — real-world scenes with complex color gradients, varied textures, and natural lighting — JPG compression at 80% produces results that are effectively indistinguishable from the original at normal viewing sizes.
The reason is how JPEG compression works: it targets the subtle high-frequency information in image blocks — tiny variations in similar-colored areas — that the human visual system processes less precisely than large color differences. Photographs are full of this kind of information. Removing it produces a smaller file that looks identical because the information was in the threshold of what your eyes can perceive.
80% quality is the standard setting for web images. It produces files 60–70% smaller than the original with no perceptible difference at typical screen sizes. For print or professional photography, 90–95% is safer. Below 70%, start checking the result at full zoom before publishing.
File size reduction is substantial. A typical unoptimized product photograph runs 3–6MB as a PNG or high-quality JPEG. After converting to JPG at 80%, it typically lands between 300KB and 1.5MB — with the same visual appearance in a product listing, on a website, or in a marketing email. That 70% size reduction directly affects page load time.
When converting to JPG will visibly reduce quality
JPG compression struggles with three categories of image content. Knowing them saves a lot of confusion about why a converted image looks wrong.
1. Transparency
JPG does not support transparency. Any transparent pixels in a PNG become solid — white by default in most tools, black in others — when converted to JPG. A product photo on a transparent background becomes a product photo on a white rectangle. If you need transparency, stay in PNG or switch to WebP, which supports it.
2. Text and sharp geometric edges
JPEG compression operates in 8×8 pixel blocks. High-contrast edges — dark text on a white background, a crisp logo on a solid color — get their block boundaries exposed as visible artifacts. The result looks blurry or "ringy" around the edges. Screenshots, UI mockups, and logos belong in PNG for this reason.
3. Already-compressed JPGs
Converting a JPG to another JPG (or opening and saving it) re-runs the compression algorithm on already-degraded data. Each encode discards more. The quality loss from three or four re-saves becomes clearly visible even at 80% quality. Open a JPG, edit it, and save it as a new JPG — that is two rounds of lossy compression on the same image.
If your source file is already a JPEG and you need to edit it, convert it to PNG first, make your edits, then export as JPG once at the end. Every intermediate JPG save compounds the quality loss.
The JPG-to-PNG myth: why it does not improve quality
A widely held belief: if you convert a JPG to PNG, you get a higher-quality image. This is not how it works.
When JPEG compression runs, it permanently discards data. That data does not exist anywhere anymore — not in the file, not in memory, not recoverable by any software. Converting the result to PNG wraps the already-compressed pixel values in a lossless container. The file gets larger (sometimes much larger), but the image is identical to the JPG source. There is nothing to recover because the original information was discarded by the encoder.
The practical result: a 1.2MB JPG converted to PNG becomes a 4MB PNG that looks exactly the same as the 1.2MB JPG. You paid four times the storage cost for zero quality improvement. (If you opened the PNG in an editor and saved it as JPG again, you would then have two rounds of lossy compression on the same original. That does make it worse.)
The only scenario where JPG-to-PNG conversion is useful: you need to edit the image further and want a lossless working copy so that your edits do not apply lossy compression on top of lossy compression. That is a workflow decision, not a quality recovery.
WebP: what JPG should have been

Photo by cottonbro studio on Pexels
If your destination is a website, there is a better conversion target than JPG: WebP. WebP uses a modern compression algorithm that achieves the same visual quality as JPEG at roughly 25–35% smaller file sizes. It also supports transparency — which JPG does not — making it a single format that can replace both JPG and PNG for web use.
WebP support was a browser compatibility problem for years. Internet Explorer refused it until IE was discontinued. That excuse is gone. Every major browser — Chrome, Firefox, Safari, Edge — has supported WebP since 2020 or earlier. If you are building a website today, serving WebP for on-page images and keeping JPG for email and social sharing is the right call.
The quality comparison: a photograph converted from PNG to JPG at 80% is noticeably smaller than the original PNG, which is good. The same photograph converted to WebP at equivalent quality is smaller still, which is better. For everything served inside a browser, converting to WebP rather than JPG is the correct move in 2026.
| Format | Compression | Transparency | Relative file size |
|---|---|---|---|
| PNG | Lossless | Yes | Largest |
| JPG | Lossy | No | 60–70% smaller than PNG |
| WebP | Lossy or lossless | Yes | 25–35% smaller than JPG |
How to convert images without unnecessary quality loss

Photo by cottonbro studio on Pexels
- 1
Identify the image type first
Photograph or complex image with gradients: JPG or WebP are fine. Logo, icon, text-heavy image, or anything with transparency: PNG or WebP. Using the right format is more important than any quality setting.
- 2
Choose the output format intentionally
For websites: WebP. For email and social sharing: JPG. For images that need transparency: PNG or WebP. The format choice determines what is possible — JPG at any quality setting will destroy transparency.
- 3
Set quality to 80% for JPG or WebP (photos)
This is the sweet spot: files are 60–70% smaller with no visible quality difference for photographs. For sharp-edged content that must be in JPG, 85–90% is safer.
- 4
Convert once from the best source available
Always convert from your highest-quality source — the original PNG, the RAW export, the PSD. Converting from an already-converted JPG applies two rounds of lossy compression. The second round degrades quality that the first round already compromised.
- 5
Upload to the Image Converter and download
ImageTools converts between JPG, PNG, WebP, HEIC, AVIF, and more. Select the output format, convert, download. No account required, files deleted within 1 hour.
Convert between JPG, PNG, WebP and more
No account. No watermark. Files deleted within 1 hour.
Open Image ConverterFrequently asked questions
Does converting PNG to JPG reduce quality?
Does converting JPG to PNG improve quality?
What quality setting should I use when converting to JPG?
Does converting to JPG remove transparency?
Is WebP better than JPG for image quality?
Converting to JPG does reduce quality — that is unavoidable with lossy compression. What is avoidable is reducing it more than necessary: convert from the best source you have, use 80% quality, and pick the right format for the content. The quality you keep is the quality that matters.