NiftyWebTools Start free

Nifty Tools

PNG to JPG

Convert png to jpg in your browser. Batch up to 50 at a time. Transparency flattens to white. No upload, no signup, no watermark.

Processing mode: Local Browser-local

  • No file leaves your browser
  • Mode: Browser-local
  • 250+ files processed in the last 24h
Waiting for PNG images.

Keep working

Related tools

JPG to PNG Converter — Free, In Your Browser Convert jpg to png in your browser. Batch up to 50. Lossless PNG for editing pipelines or PNG-only uploads. No upload, no signup, no watermark. AVIF to JPG Converter — Free, In Your Browser Convert avif to jpg in your browser. Batch up to 50 images at a time. No upload, no signup, no watermark. Quality slider, alpha flattens to white. Convert Image Files Convert images to WebP, JPEG, or PNG for websites, uploads, and sharing. Compress Image Make images smaller for websites, email, marketplaces, and forms. Resize Images Batch resize images by width, percentage, or common web-friendly dimensions. WebP to JPG Converter — Free, In Your Browser Convert webp to jpg in your browser. Batch up to 50 images at a time. No upload, no signup, no watermark. Quality slider, alpha flattens to white. JPG to WebP Converter — Free, In Your Browser Convert jpg to webp in your browser. Batch up to 50 at a time. No upload, no signup, no watermark. Quality slider for tight web delivery. Images to PDF Turn ordered JPG, PNG, WebP, and AVIF images into one clean PDF. PNG to PDF Converter Free Online PNG to PDF converter that runs in your browser. Embed PNGs losslessly with alpha preserved — no upload, no signup, no watermark.

How to use it

PNG to JPG Converter — Free, In Your Browser

  1. Drop your PNG files onto the workspace, paste from the clipboard, or pick them with the file picker. Up to 50 images per batch, 100 MB per file.
  2. Adjust the quality slider if you want — the default 92 is near-lossless for ordinary photographic content and is the conventional starting point for "compatibility conversion" use cases where the JPG should look indistinguishable from the PNG source.
  3. Click Convert. Each PNG decodes through the browser's built-in image path, draws onto a canvas with a solid white background fill (which flattens any transparency, because JPG has no alpha channel), and re-encodes as JPG through `canvas.toBlob('image/jpeg', q)`. Canvas JPG encoding is supported across every current browser — Chrome, Edge, Firefox, and Safari — so the conversion succeeds on every modern device. Download individually or grab the whole batch as a single ZIP.

Good for

Common use cases

PNG and JPG were designed for different jobs. PNG is a lossless container built for line art, screenshots, UI captures, logos, and any artwork where pixel-perfect preservation matters and transparency may be needed. JPG is a lossy container built for photographs, where a 10-to-1 file-size win at imperceptible visual cost is the expected trade-off. Converting from PNG to JPG is therefore almost never about compression for its own sake — it is about compatibility. Some marketplace-listing portals, certain form-upload pipelines, locked-down corporate email gateways, print-on-demand vendors, and legacy document workflows still specify JPG and reject or re-route other formats at the upload step. The conversion is the unblock step, not a quality optimisation. The honest counter-framing: if the source PNG is a screenshot, a UI capture, or any artwork dominated by flat colour and sharp edges, converting to JPG often makes the file *bigger*, not smaller, and adds visible compression artefacts around text and lines. PNG-to-JPG saves bytes when the source PNG was actually a photograph that someone exported in the wrong container; for true screenshot or UI work, PNG was the right format to begin with. The conversion happens in the browser, in a single batch of up to 50 images, which keeps signed product mockups, screenshots that capture internal data, and licensed artwork off third-party servers — the PNG source never leaves the tab, the JPG materialises locally, and the only network traffic is the page load itself.

Processing mode

Browser-local

Files are processed by your browser. They never reach our servers.

Questions

PNG to JPG Converter — Free, In Your Browser FAQ

Why convert PNG to JPG at all?

Compatibility, not compression. PNG and JPG are designed for different content — PNG is lossless and preserves sharp edges and transparency; JPG is lossy and produces tighter files for photographic content. The reason to convert is almost always that the destination surface (a marketplace listing, a government or university form, a print-on-demand uploader, a legacy office workflow, a locked-down email gateway) accepts JPG and rejects or mishandles PNG. If your destination accepts both formats, the choice is content-dependent: keep PNG for screenshots, UI captures, line art, and anything where transparency matters; switch to JPG for photographs that need to be lighter on disk or wire. Converting a screenshot or a UI capture to JPG just to "make it smaller" usually backfires, both because the file often grows and because the compression artefacts around sharp text and lines are visible.

What happens to transparent areas in my PNG?

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.

Will my files get smaller?

Depends on the content. Photographic PNGs — phone photos, camera output, scanned documents, screenshots that captured a browser displaying a photo — typically shrink dramatically when converted to JPG, often by 60 to 90 percent at quality 92, because PNG's lossless compression is highly inefficient on the smooth gradients and noise that dominate a photograph. Screenshot PNGs, UI captures, line art, vector exports, and anything dominated by flat colour and sharp edges either shrink only marginally or grow, because JPG's lossy compression cannot match PNG's efficiency on flat-colour blocks and the result is a larger file with visible edge artefacts. The honest answer is that PNG-to-JPG is a compatibility step that sometimes also delivers compression — the savings only materialise when the source PNG was photographic content that ended up in the wrong container.

What quality setting should I use?

The default is 92, which we picked as a high-quality compatibility default for the dominant use case here — converting a PNG so it can be uploaded to a JPG-only destination, where the goal is for the JPG to look indistinguishable from the source. Push to 95 if the output is destined for an archive or a print pipeline that will be re-compressed downstream and you want the extra headroom. Drop to 70 to 80 for thumbnail grids, social-feed images, and email attachments where absolute file size matters more than pixel-level fidelity. The slider gives you the full 50-to-95 range so you can match your specific delivery surface — there is no single correct number, only a defensible default that you tune from there.

Which browsers can run this PNG to JPG converter?

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.

Is there a file size or batch limit?

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.

Will this tool stay free?

The basic workflow is designed to stay free. Paid upgrades later will focus on bigger limits, batch work, OCR, saved presets, and ad-free use.