PNG to JPG
Convert PNG to JPG with quality control, in your browser, with no upload.
How to convert PNG to JPG
- Drop your PNG files into the upload box, or click to select.
- Pick a quality level. Default of 85 is a safe balance for most photos; drop to 75 for aggressive savings, raise to 92 for visually critical content.
- Download the resulting JPGs individually or as a batch.
The conversion happens entirely inside your browser. Files never get uploaded anywhere.
Why convert PNG to JPG?
PNG is a lossless format designed for graphics with sharp edges and transparency. JPG is a lossy format designed for natural photography. When a PNG is actually storing photographic content (taken from a phone, a camera, or a screenshot of a photo-heavy scene), it’s roughly 5–10× larger than the equivalent JPG with no visible quality difference.
The most common reasons we see people convert PNG to JPG:
- Reducing page weight on a website or blog where the images are natural photographs.
- Working around platform limits that cap upload sizes or reject PNG for specific image types.
- Compatibility with older software that renders JPG more reliably than PNG (rare in 2026 but still happens with legacy systems).
- Preparing photos for email where file-size caps matter.
If your PNG is a screenshot, logo, or line-art graphic with sharp edges, stick with PNG. Converting these to JPG will introduce visible halos around hard edges and fuzzy text.
What happens to transparency
JPG has no alpha channel, so any transparent pixels in the source PNG get flattened. Our tool fills transparent areas with white (#FFFFFF) before encoding. If the source PNG was fully transparent in some regions, those regions become white in the JPG.
If you need a different background color, open the PNG in an image editor first, flatten against your preferred color, and then convert. Or leave the PNG as PNG — there’s usually no good reason to convert a transparent graphic to JPG anyway.
Choosing the right quality level
JPG’s quality parameter controls how aggressively information gets discarded during encoding. The defaults we suggest:
- 92 and above: Visually lossless for most photos. Large files. Rarely worth it for the web.
- 85: The web sweet spot for photos. Visible artifacts are hard to spot at normal viewing sizes.
- 75: Aggressive but acceptable for blog photos and thumbnails.
- 60 and below: Visible artifacts. Only use when file size is non-negotiable.
Our default is 85 because PNG-to-JPG conversion is typically a “reduce file size” workflow, and 85 gets 90%+ of the savings of lower settings without the visible quality cost. Drop the slider if you want to squeeze harder; raise it for hero images.
File size expectations
A rough rule of thumb for a 3000×2000 image:
- As PNG (photo content): 4–8 MB.
- Converted to JPG at quality 85: 500–900 KB.
- Converted to JPG at quality 75: 300–500 KB.
For graphics (logos, icons, illustrations), savings are much smaller or negative because PNG was already efficient for that content. For photos, the conversion typically cuts size 5–10×.
When PNG is still the right choice
Don’t convert to JPG when:
- The image has transparency you need to preserve.
- The image has sharp edges, text, or line art. JPG introduces halos.
- You’re working in an editing pipeline where every save must be lossless.
- The image will be compressed again later (re-saving JPG accumulates losses).
If you want the file-size savings of JPG-level compression plus the flexibility of transparency, consider converting to WebP instead. WebP is lossy by default but supports alpha.
How the conversion works
When you drop a PNG in, the browser:
- Decodes the PNG into a bitmap.
- Paints the bitmap onto a canvas with a white background fill.
- Re-encodes the canvas as JPG at your chosen quality.
- Offers the result as a download via an in-memory blob URL.
No server round-trip. No upload. No external service. All processing uses the browser’s built-in Canvas and JPEG encoder APIs.
Metadata stripping
Re-encoding through canvas drops all metadata: EXIF fields (GPS coordinates, camera model, timestamps), color profiles beyond sRGB, and any other non-pixel chunks.
For most web publishing this is the right default. If you want to preserve metadata in the converted file, you’d need to read it with a library like piexifjs and re-embed it after conversion — not something our browser tool does.
For explicit metadata stripping that keeps the source format intact, see our EXIF stripper.
Common mistakes
- Converting a logo or screenshot with sharp edges to JPG and being surprised by visible fringing.
- Using quality 100 “to be safe.” Quality 100 typically produces files 2–3× the size of quality 90 with no perceptible improvement.
- Expecting transparency to survive. It can’t — JPG has no alpha. Plan for flattening.
- Repeatedly converting back and forth between PNG and JPG. JPG is lossy; each round trip degrades the image.