Convert PNG to JPG to shrink screenshot file sizes for sharing, email, or upload.
Drop one or many - all convert to JPG. Per-row progress, batch convert, ZIP download.
PNG screenshots are huge - a single 4K screenshot can easily hit 8-10 MB because PNG stores every pixel losslessly. Converting to JPG typically cuts that to 1-2 MB with no visible quality difference for most screen content. It's the right move for emailing screenshots, posting to chat, or attaching to bug reports where the recipient just needs to see the image, not edit it.
JPG doesn't support transparency, so we flatten any transparent areas onto a white background before encoding. Sharp text and thin lines pick up a small amount of compression softening at the default quality setting (Q=92), but at typical viewing distances it's imperceptible. For pixel-perfect screenshots, keep the PNG.
The clearest case for PNG-to-JPG is screenshot file size. macOS and Windows both default to PNG for screen captures (Cmd+Shift+4 on Mac, Win+Shift+S on Windows). PNG was a great default in 1995 when monitors topped out at 800x600; on a 5K display in 2025 a single screenshot can hit 15-20 MB. Most use cases (email, chat, bug reports, documentation) don't need lossless precision - they need a small file that opens quickly. JPG at high quality is the right answer.
Compare the format strengths: PNG wins for graphics with sharp edges (icons, logos, UI mockups), transparency, repeated solid-color regions (which PNG compresses very efficiently), and any case where you'll edit and re-save (no lossy degradation). JPG wins for photographs, photo-realistic content, and any case where file size matters more than pixel-perfect preservation. Screenshots straddle both worlds; the answer usually comes down to "will I edit this again?" - if no, JPG is fine.
A common workflow: take screenshots all day in PNG (the OS default), then bulk-convert to JPG when you're ready to share or archive. Some teams run the conversion automatically on a folder - going from a 2 GB "screenshots" folder to a 200 MB version with no visible quality loss. The same principle applies to design exports: PNG masters in source control, JPG renders for distribution.
A 6 MB PNG screenshot becomes a 600 KB JPG. Faster to send, faster for the recipient to see inline.
Most email systems aggressively recompress images anyway. Sending a JPG up-front avoids one round of degradation and stays under attachment caps.
Jira, GitHub, and Linear all accept PNG, but a folder of 20 PNG attachments adds up fast. JPG keeps the ticket loading quickly.
File-size caps on web forms (typically 5 MB) bite when uploading screenshots. JPG nearly always slides under.
Bulk-converting an archive of screenshots cuts cloud storage costs without losing the content. Keep PNG masters elsewhere if needed.
Twitter, Instagram, and LinkedIn recompress all uploads through JPEG anyway. Pre-converting lets you control the quality instead of letting their pipeline guess.
PNG is a lossless image format with alpha-channel transparency. Larger than JPG for photos, but ideal for screenshots, logos, and graphics with sharp edges.
JPG (JPEG) is the dominant lossy image format on the web - small files, near-universal support, but no transparency. Best for photos and high-frequency detail.
Drag a PNG onto the converter above, or click the box to pick one from your device.
We've preselected JPG as the output format. Change it from the dropdown if you want a different target.
Click Convert and wait for the progress bar to finish. Download the JPG when it's ready.
Convert JPG to PNG for editing, archiving, or when you need a lossless copy.
Shrink PNG files to WebP without losing transparency - smaller files, same quality, every modern browser.
Turn one or more PNG screenshots into a single PDF for sharing, printing, or archiving - free, browser-only.