PNG to JPG

What is PNG to JPG?

PNG and JPG were built for opposite jobs. PNG never throws away a pixel — perfect for screenshots, logos, line art, anything with sharp edges. JPG throws away the visual details your eye is least likely to notice — perfect for photographs, where the loss is invisible but the file shrinks 50–80%. Converting a PNG screenshot to JPG produces a smaller file with visible artefacts around text. Converting a PNG photograph to JPG produces a much smaller file with no visible loss at all. Knowing which case you're in is the whole game. This converter runs on a Canvas inside your browser tab. Each PNG is decoded once, then re-encoded as a baseline JPEG at 92% quality (the sweet spot for photographs — high enough that compression artefacts are invisible to the naked eye, low enough to get meaningful file-size savings). Transparent regions fill to solid white on export, because JPG has no alpha channel and white is the safest default for documents, ID scans, and product photos. Files never upload — the whole pipeline is local.

Why use this tool?

Canvas-native resolution — your source image's width × height is preserved exactly. A 3000×2000 PNG comes out as a 3000×2000 JPG. Quality is hard-coded to 92% on the encoder, which is the standard professional default for photographic JPGs (most editors use 85-95%, 92 is in the sweet spot). EXIF metadata (camera model, capture timestamp, GPS coordinates if present in the source) is preserved during conversion. If you specifically WANT to strip metadata (privacy-sensitive sharing), run the output through /image/remove-metadata afterward. Batch mode handles up to 50 files in one drop. The converter processes them sequentially in the browser (parallel canvas operations can blow out memory on phones), so for very large batches expect ~150ms per file on desktop, 400-800ms per file on mobile. Output downloads as a ZIP when you process more than one file. No upload at any step. The Canvas pipeline runs in WebAssembly + the browser's native JPEG encoder, which works offline once the page is loaded.

Common use cases

The dominant case: shrinking a PNG screenshot of a photograph or design comp before emailing or uploading to a portal that caps attachment size. A 4 MB PNG of a phone screenshot routinely becomes 400-800 KB as JPG with no perceptible quality loss. Close seconds: preparing product photos for Amazon / Shopify / Etsy listings (most platforms accept both but JPG's smaller payload uploads faster and serves visitors quicker); converting design exports from Figma / Sketch / Adobe XD that exported as PNG when JPG would have been fine; bundling photos into an email where the cumulative attachment size matters; converting an old PNG photo archive to JPG to free disk space when long-term quality isn't needed. DO NOT use for: screenshots of text or UI (JPG artefacts make text fuzzy — keep as PNG or convert to WebP), logos with sharp edges (same), images you still plan to edit (each JPG re-save adds new losses), or any image with transparency you need to preserve (JPG flattens transparency to solid white).

How to use PNG to JPG

1. 1Drop one or more PNG files onto the upload area (drag-multi-select for batches)
2. 2Wait for each image to decode — typically 50-200ms per file on desktop, longer on phone for high-DPI screenshots
3. 3Preview shows the JPG output alongside the original PNG so you can spot any quality regression
4. 4Download — single file downloads as .jpg, multi-file downloads as a .zip with the JPG name preserved per source

Frequently asked questions

Will my PNG-to-JPG conversion be noticeably lower quality?

Depends on the source. For photographs (faces, landscapes, product shots), at 92% JPEG quality the difference is invisible to the naked eye even at 200% zoom — the encoder is dropping high-frequency detail your visual system doesn't register. For screenshots of text, UI elements, logos, or line art, you WILL see compression artefacts around the sharp edges — the JPEG DCT (discrete cosine transform) doesn't handle hard transitions well. Quick rule: photographs → safe to convert, anything with text or sharp edges → keep as PNG or convert to WebP instead.

How much smaller will the JPG be vs my source PNG?

For photographic content, 5-10× smaller is typical (a 4 MB PNG photo becomes 400-800 KB as JPG). For screenshots, savings vary wildly — a screenshot of a colourful landing page might shrink 3×, a screenshot of plain text on white might only shrink 1.5× because JPG's compression model is optimised for natural images, not artificial ones. WebP usually beats JPG by another 20-30% on either source type.

What happens to PNG alpha transparency on export?

It flattens to solid white. JPG has no alpha channel — there's no spec-supported way to preserve transparency in a JPEG file. The Canvas composites the source PNG against a white background before encoding, which is the universal default. If you need a different background colour, either edit the PNG first (e.g. /image/change-background-color or in any editor) or convert to WebP/PNG instead.

Does the conversion preserve EXIF metadata?

Yes — camera model, lens, ISO, capture timestamp, and GPS coordinates (if the source PNG has them) survive to the JPG output. PNGs from cameras and phones typically carry EXIF; PNGs from screen captures and design tools typically don't. If you specifically want to strip metadata before sharing publicly, run the output JPG through /image/remove-metadata.

Why batch limit of 50 files?

Browser memory pressure. Each PNG decode allocates a Canvas bitmap proportional to width × height × 4 bytes (RGBA). A 4000×3000 PNG uses ~48 MB during decode. Batching 50 of those sequentially is fine; processing them in parallel would OOM the tab on most mobile devices. Drop them in one batch, the tool processes them in series and bundles into a ZIP automatically.

Why not just use WebP instead?

WebP is usually the better choice technically — it supports transparency, animates, and is 20-30% smaller than JPG at equivalent quality. The reason JPG is still useful: universal compatibility. Some older portals, email systems, and printers reject WebP. JPG is accepted everywhere. Convert to JPG when the destination explicitly wants JPG; use /image/convert-image to pick WebP for general modern web use.

1. 1For a quick PNG-vs-JPG quality sanity check on a specific image, convert it once and zoom to 200% in the preview. If text edges look fuzzy or skin tones look slightly muddy, the source isn't a good JPG candidate — stay on PNG.
2. 2When converting screenshots for a tight portal cap, try WebP first via /image/convert-image. It's typically 30% smaller than JPG at the same visual quality AND handles text edges cleaner.
3. 3Batch-converting a folder of phone photos for cloud backup? Convert AND strip EXIF (via /image/remove-metadata after) in one pass — saves on storage AND on the embarrassing GPS-leak risk if you ever share one of the photos publicly.

How does it compare?

TinyPNG and CloudConvert run server-side, cap free use to a daily quota, and upload your file to their servers (which is the wrong default for personal photos). Photoshop, Affinity Photo, and Preview convert locally but require the desktop app. This tool runs in any browser at native resolution, no daily cap, no upload, no watermark, and uses the same canvas-based JPEG encoder the macOS Preview app uses under the hood.

Related guides

Editorial walk-throughs that go deeper on the workflow most people use this tool for.

Related tools

More free tools. No signup, no watermarks.