Convert PNG to JPG
Quietly. In your browser. No upload.
Drop your .png file
or click to browse · max 50MB
or paste with ⌘V
PNG is the format you reach for when you need transparency or pixel-exact precision — screenshots, UI mockups, line art. JPG is the format you reach for when file size matters more than fidelity — photos, social media, web pages with many images. Converting from PNG to JPG is the right move when you're starting from a screenshot or design file and need a smaller, more shareable image. The cost is the alpha channel (transparent regions become solid color, white by default) and a small amount of detail loss at sharp edges.
When you'd use it
Smaller screenshots
A 4K macOS screenshot is often 5–10 MB as PNG. The same image at JPG quality 90 is typically 500 KB–1 MB without any visible difference. If you're sending screenshots over Slack or email, the recipient will appreciate the smaller file.
Web and email-friendly photos
Most CMSs, newsletter platforms, and image-heavy templates favor JPG. You'll get faster page loads and better compatibility — many older email clients have quirks with PNG that they don't have with JPG.
Photographs saved as PNG
If you exported a photo from an editing app as PNG, you have a file that compresses badly. JPG is what cameras and phones produce natively, and re-encoding to JPG at quality 90+ recovers most of the size you'd expect.
How it works
-
Your file never leaves the browser.
-
Conversion runs locally via WebAssembly and Canvas.
-
Download. No account, no history.
Technical notes
PNG is lossless and supports an alpha channel; JPG is lossy and is always opaque. When you convert, every transparent pixel must be replaced with a solid color — by default this tool fills white, but you can change the background color above. Detail loss is concentrated at sharp edges (text, line art, logos). For images that are mostly photographic, the loss is invisible at quality 85 and above. For images with lots of text or line work, stay at quality 95+ or consider PNG → WebP instead, which keeps transparency and compresses smaller.
Frequently asked
What happens to my PNG files?
Nothing leaves your browser. The conversion runs locally on your device using WebAssembly and the Canvas API. No file is uploaded to a server — including ours.
Is the converted JPG identical to the original?
JPG is a lossy format. The output is visually very close to the original at quality 90+ and considerably smaller. Use the quality slider above to trade size for fidelity.
Is there a file size limit?
There is no hard cap, but very large files (hundreds of MB) may be slow on older devices because everything happens in your browser's memory.
Do you collect data on my file or my use?
Your file is invisible to us — it never leaves your browser. For aggregate page-view counts we use Cloudflare's server-side edge logs (no JavaScript beacon runs in your browser). We display Google AdSense ads on conversion result pages; the AdSense script loads on every page and may set advertising cookies after you accept the consent banner (Google Consent Mode v2 asks first). The ads see the page URL and standard browsing signals — they never see your file, because the file never leaves your device.
Will the JPG be smaller than the PNG?
Almost always. For photographic content, JPG at quality 90 typically produces files 5–10× smaller than PNG. For images with sharp edges or large flat color areas, the gap is smaller — sometimes JPG is only 2× smaller, and for very simple graphics PNG can occasionally win.
Why does my converted image look slightly different?
Two reasons. First, JPG is lossy: it discards visual information that humans typically don't notice but isn't pixel-identical to the original. Second, transparent pixels in your PNG were replaced by the background color above. If you need pixel-identical output, convert to WebP instead, or stay with PNG.