Question 1

Why convert PNG to JPG at all?

Accepted Answer

Compatibility, not a guaranteed size reduction. PNG is lossless and keeps transparency. JPG is lossy and suits photographs. Convert when the destination accepts JPG but rejects or mishandles PNG. Keep PNG for screenshots, interface captures, line art and images with transparency. Converting those images to JPG can make the file larger. It can also add visible artefacts around text and lines.

Question 2

What happens to transparent areas in my PNG?

Accepted Answer

They flatten to white. JPG has no alpha channel, so any transparent or semi-transparent pixels in the source PNG must be composited against a solid background before encoding. The tool fills the canvas with white before drawing each PNG, which means transparent regions render as crisp white rather than the black-fill artefact some converters produce when they drop the alpha without filling. White is the broadest-compatibility background — marketplace listings, form-upload portals, document workflows, and most print-on-demand previews assume a white seamless background — so the default is the right answer for the dominant use case. If your PNG is a logo or an icon where the transparency itself is the design, JPG is the wrong target format altogether — pick PNG-or-similar via the sister tool Convert Image Files.

Question 3

Will my files get smaller?

Accepted Answer

It depends on the content. Photographic PNGs can become smaller because JPG suits gradients and image noise. Screenshots, line art and graphics with flat colours can shrink very little or grow. They can also show visible artefacts around sharp edges. Treat this as a compatibility conversion.

Question 4

What quality setting should I use?

Accepted Answer

The default is 92. Increase it when you want to keep more detail. Reduce it when file size matters more than detail. The slider covers 50 to 95.

Question 5

Which browsers can run this PNG to JPG converter?

Accepted Answer

Every current Chrome, Edge, Firefox, and Safari. PNG decoding via `<img>` has been universally supported across browsers since the late 1990s — PNG was published as a W3C recommendation in 1996 and the major engines added native rendering shortly after, so any browser still in service today renders PNG without question. Canvas JPG encoding through `canvas.toBlob('image/jpeg', quality)` is supported in every current browser as well — JPG is the original Canvas encode target and works on every device that can run modern web apps, including iPhone Safari and Android Chrome. There is no browser-version caveat for this conversion direction (unlike WebP or AVIF encoding, which Safari does not currently implement through the Canvas API). The tool still verifies the encoded blob's MIME type as a defensive check before writing the output file, so any future edge case surfaces a clear error rather than a misnamed file.

Question 6

Is there a file size or batch limit?

Accepted Answer

Each PNG must be under 100 MB and a single batch can hold up to 50 images. The 100 MB cap protects lower-RAM devices from running out of memory during decode, since the browser materialises the full pixel grid into a canvas before re-encoding — a 100 MB compressed PNG can expand to several gigabytes of decoded pixel data in memory. The 50-file cap keeps the ZIP build responsive — for large batches the bottleneck is browser memory, not the conversion itself, since each image processes sequentially. If you need to convert more than 50 images, run the tool twice and stack the resulting ZIPs — the conversion is deterministic, so the second batch produces output identical to what one continuous run would have written.

Question 7

Will this tool stay free?

Accepted Answer

Yes. Everything this tool does is free. On some tools, a Day or Project Pass raises the file-size and batch limits if you need more.

PNG to JPG

Converted images

What next?

How to use PNG to JPG Converter

Common use cases

Runs in your browser

PNG to JPG Converter: common questions