About this tool
PNG to JPG Converter, Convert PNG to JPG in Your Browser
Drop a PNG and download a JPG at the quality you choose. Transparent pixels get a white background by default (JPG has no alpha channel). Runs entirely in your browser. Your images never leave your device.
Why use OmegaPix
-
Massive size reduction : PNG of a photo is usually 5-10× the size of an equivalent JPG. Converting a typical PNG photo drops it from 4 MB to 400 KB.
-
Adjustable quality : Auto picks the visually-lossless sweet spot (q85). Manual lets you push lower for email caps or higher when quality matters more than size.
-
No upload : mozjpeg encoder runs in your browser via WebAssembly. Confidential or personal images stay on your device.
How it works
Drop your PNGs
Batch is fine, convert dozens at once with one click.
Pick quality
Auto (q85) is right for most uses. Manual quality slider for full control.
Download the JPGs
Each gets a .jpg extension. Save individually or download all as a ZIP.
Frequently asked questions
How much smaller will my JPG be?
Depends on content. Photos: 80-90% smaller than the PNG source. Screenshots: 50-70% smaller (with some quality cost on text). Logos and graphics: similar size or larger.
What happens to transparent pixels?
They're flattened against a background colour (default: white). JPG doesn't support transparency. If you need transparency preserved, convert to WebP instead.
Will the conversion be lossy?
Yes, JPG is a lossy format. Quality 85 (default) is visually identical to the source. Going lower trades quality for size.
Can I batch convert?
Yes. Drop as many PNGs as your device memory allows. Download each individually or grab them all as a ZIP.
Is anything uploaded?
No. Verify in DevTools → Network during a conversion. Your PNGs never reach a server.
What about animated PNG (APNG)?
Only the first frame converts, JPG is a single-image format. For animated content, use a video format instead.
How does this compare to PNG to WebP?
WebP is smaller AND supports transparency AND has lossless mode. For web delivery, WebP is the better target. JPG is right when you need universal compatibility (email, older software, embedded systems).
Can I keep EXIF metadata?
PNG doesn't have EXIF. There is no metadata to preserve, so the output JPG starts clean (no GPS, no camera info).
Why is the output sometimes larger than expected?
Tiny PNGs (< 50 KB), flat-colour graphics, small icons, can be larger as JPG because of the format's overhead. For these, keep PNG or convert to WebP-lossless.
How big a PNG can I convert?
Up to 50 MB per file on desktop, 25 MB on mobile. The memory guard prevents browser crashes on very large files.
When to use this tool
Email attachments
PNG photos easily exceed Gmail's 25 MB cap. JPG conversion fits comfortably.
Universal compatibility
Some older software, embedded systems, and email clients prefer JPG over PNG.
CDN bandwidth savings
Web photos in PNG format waste bandwidth. JPG cuts CDN bills by 80%+ for photographic content.
When not to use this tool
Screenshots and graphics
JPG adds halos around text and sharp edges. Keep screenshots and logos as PNG (or convert to WebP-lossless).
You need transparency
JPG cannot store alpha. Transparent pixels become solid white (or the background colour you pick). For transparency, convert to WebP instead.
Editing the file again
JPG re-compression is cumulative. If you'll edit the output further, keep the PNG until export.
Technical details
Why PNG photos are big
PNG uses DEFLATE compression over raw pixels, efficient for line art and flat colour, weak for the high-variation pixel data in photographs. A 4000×3000 photo as PNG-32 is often 12-20 MB. Same photo as JPG q85: 1.5-2 MB.
How JPG handles transparency
JPG has no alpha channel. Transparent PNG pixels must be flattened against a background colour before encoding. OmegaPix defaults to white (most common, looks neutral); you can swap to black or any hex colour if needed.
Quality sweet spot
q85 is the visually-lossless target, most viewers can't distinguish it from q100 at normal screen distance. q80 saves another 15%. q70 introduces visible halos on sharp edges. q60 is noticeably degraded.
Real numbers
A 1920×1080 PNG screenshot (~2 MB) → JPG q85: 280 KB (-86%). A 4032×3024 photo PNG (~16 MB) → JPG q85: 1.8 MB (-89%). A 1080×1080 social square PNG → JPG q85: ~150-300 KB depending on complexity.
Your files stay on your device
PNG decoding and JPG encoding both run inside your browser. mozjpeg compiles to WebAssembly, the same encoder Google and major CDNs use, just running locally. Verify in DevTools → Network during conversion: zero outgoing requests carry image bytes.