PNG to JPG

How to turn PNG into JPG

1. Select one or more PNG files above. A file is checked for the PNG signature before decoding.
2. Choose a background color and JPEG quality. The background is painted first, then the PNG is drawn on top at its original pixel width and height.
3. Choose Convert to JPG. Download a single result or, for a batch, use the ZIP button. Each JPG remains available individually.

The tool processes each image in sequence, so one bad file does not stop the rest. It reports the failed filename and keeps successful downloads.

What happens to transparent PNG pixels?

JPEG cannot carry an alpha channel. This tool fills the entire canvas with your selected color before drawing the PNG; transparent pixels reveal that fill, and partly transparent edge pixels blend with it. If a logo will appear on a dark page, select that page color before converting. Otherwise a white halo can become baked into the JPG.

Choose quality by inspecting the result

Start at the tool's default quality of 85, then compare the downloaded JPG with the original at actual pixel size. Lower quality can reduce the encoded bytes but may roughen narrow letters and hard color edges. Quality 100 does not restore detail missing from the PNG, and the browser's encoder decides the exact byte count.

Keep the dimensions unchanged first. If a phone or screenshot PNG is too large for the browser to decode or allocate a canvas, the tool says so; it does not silently shrink it. Open the source in an editor, resize it deliberately, then convert the smaller PNG here. A smaller pixel grid and a lower JPEG quality are different changes, so test them separately.

Why might the JPG color look duller?

A source PNG can carry color-profile information. In this tool the browser decodes that PNG, draws pixels into a canvas, and creates a new JPEG; the output is not a byte-for-byte copy of the source profile or other metadata. Compare the result in the same browser and against a known display-color export before blaming the quality slider. If exact managed color is mandatory, use a color-managed editor and inspect the output profile there.

Measured browser conversion

On October 27, 2026, we ran this page in headless Chrome 156.0.8078.48. The source images were generated locally: transparent-check.png was a 96 × 64 transparent canvas with a partly transparent blue rectangle, and photo-check.png was a 160 × 100 opaque blue canvas with an orange circle. They are controlled test artwork, not phone photos. We used the page's white background and quality 85, selected both PNGs together, clicked Convert to JPG, downloaded both JPGs and the ZIP, and decoded the downloaded files separately.

Both downloads began with JPEG signature FF D8 FF and decoded as JPEG. In this small, flat-color pair, each JPG was larger than its PNG source. That is a useful counterexample to the idea that changing the extension always saves bytes. The 96 × 64 source used only 282 bytes because its transparent background and simple geometry compressed efficiently as PNG. The tool preserves width and height; it does not hide a resize behind the conversion.

We repeated the 160 × 100 source at quality 50 and quality 100 without changing pixels or dimensions. The outputs were 1,468 bytes and 6,072 bytes, respectively; quality 85 had produced 2,070 bytes. In this browser, moving from 85 to 100 added 4,002 bytes while retaining the same pixel grid. This does not tell you that 50 is acceptable for fine text or faces: our source contained only a circle and two flat colors. Use 85 as a starting point, inspect your own result at actual size, and move the slider only when its visible tradeoff suits that image.

We also stress-tested a larger input made from locally generated random RGB pixels, not a camera photo. The 3,000 × 2,500 PNG occupied 22,542,418 bytes. At quality 85, this page produced a 5,358,789-byte JPEG at the same 3,000 × 2,500 dimensions; the click-to-ready interval was 1,868 milliseconds in this headless Chrome run. This establishes that the tested machine handled this one large file. It does not establish a universal file-size limit or promise the same speed on a phone. Random pixels are deliberately hard to compress, so do not use this result as an expected saving for your own photograph.

For the transparent source, the JPG corner at quality 85 read RGB 255, 255, 255 with white fill. We changed only the background picker to #18364a, converted again, and decoded the corner as RGB 23, 54, 74; the dark-fill JPG was 1,129 bytes. Its corner is close to the requested fill but does not reproduce each channel exactly because JPEG is lossy. Choose the background before conversion: repainting the web page later cannot recover the alpha channel from the downloaded JPG. This check covers one partly transparent test drawing and two fill colors, not every PNG edge or color profile.

The two-file ZIP was 3,524 bytes and contained exactly photo-check.jpg and transparent-check.jpg. We extracted each entry and compared its bytes with the corresponding individual download; both matched. The ZIP uses stored JPEG data, so this check proves packaging consistency for this pair, not additional photo compression. At a 390-pixel browser viewport, the measured document scroll width was also 390 pixels and the file picker was visible without scrolling. That checks layout at one simulated phone width; it does not claim a physical phone test.

Use the format your destination expects

JPG is useful for an opaque photo or a page that needs a smaller photographic image. It is a poor replacement for a logo that must stay transparent. If the destination actually needs an icon file, the PNG to ICO converter keeps icon layers in one ICO; the PNG favicon tool prepares a browser icon. Those are separate outputs from this page's JPGs.

PNG to JPG questions