Convert PNG to JPEG — Free & Instant
100% browser-based · No upload · No file size limit · Canvas API · Batch mode
Key Takeaways
Yes — JPEG is lossy. But at 85% quality, the output is visually indistinguishable from the original PNG on any screen. The key rule: always convert from your original PNG master file, never from a previously-converted JPEG.
85% for web and email. 90–92% for social media uploads (Instagram re-compresses on upload, so give it high-quality source material). 92–95% for print. Never go below 70% — JPEG block artifacts become clearly visible.
JPEG has no transparency support at all. Any transparent pixels in your PNG are filled with white because JPEG simply cannot store per-pixel opacity. Use WebP or keep PNG if you need to preserve a transparent background.
Photos: 60–80% smaller. A 4 MB PNG portrait typically becomes 600–900 KB at 85% quality. Screenshots with flat colors or text: only 20–40% smaller, because JPEG's DCT algorithm is tuned for photographs, not flat graphics.
JPEG for all photos and realistic images — dramatically improves Core Web Vitals LCP score. PNG for logos, icons, and UI elements that need transparency or pixel-perfect sharpness. WebP for maximum performance (25–35% smaller than JPEG, transparency support).
100% private. All conversion runs in your browser using the HTML5 Canvas API. Your image files are never uploaded to any server. Nothing is stored, logged, or transmitted. No account, no watermarks, no file size limit. Free forever.
How to Convert PNG to JPEG
The converter is embedded on this page — already set to PNG → JPEG. No redirect needed.
Drag & drop one file or a whole batch. Multiple images convert in parallel so large sets finish quickly.
The default 85% is visually identical to the original but meaningfully smaller. Raise to 92% for print work.
Files download automatically as each one finishes — no waiting, no email links, no expiry timers.
Why Convert PNG to JPEG?
PNG is lossless — every pixel is stored perfectly, which is why PNGs can be enormous. JPEG is designed for photographs, where its smart compression sheds detail your eyes can't detect. Here's when the switch makes sense:
- 📧 Emailing photo proofs — mail servers often reject large PNGs. JPEG slides through at a fraction of the size; clients reviewing photos on screen can't tell the difference at 85% quality.
- 📝 Blog & CMS uploads — WordPress, Squarespace, and most platforms load pages faster with JPEG photos than bulky PNG exports from Figma or Photoshop.
- 💾 Clearing storage fast — a folder of raw PNG exports can shrink from gigabytes to megabytes in one batch conversion.
- 🚀 Faster page loads — JPEG photos are 5–10× smaller than PNG at near-identical quality, directly cutting Largest Contentful Paint time.
- 🖥️ Legacy software compatibility — older Windows apps, scanners, and design tools sometimes choke on large PNGs. JPEG has worked everywhere since the 1990s.
- ⚠️ Transparency caveat — if your PNG has a transparent background (checkerboard), it becomes white after conversion. Use PNG or WebP if transparency must be preserved.
Choose Your Quality Setting: By Use Case
The right JPEG quality setting depends on where the image is going. Too high and you waste bandwidth; too low and compression artifacts become visible. Find your destination below — then use that quality in the converter above.
| Use Case | Quality | Why |
|---|---|---|
| Blog / website photos | 80–85% | Invisible quality loss on screens. Maximum LCP / PageSpeed benefit. 60–80% smaller than PNG. |
| Email attachments | 75–82% | Email renders at screen DPI. Target under 500 KB. Always convert from PNG original, not a JPEG. |
| Instagram / Facebook / Twitter | 90–92% | Platforms re-compress on upload. Give them high-quality input to maximize their output quality. |
| Print (A4, letter, poster) | 92–95% | Print review requires higher fidelity. 95% is visually lossless at print viewing distances. |
| E-commerce (Shopify, WooCommerce) | 82–88% | Platforms apply their own CDN compression. 85% gives a clean source without over-engineering. |
| WordPress media upload | 88–92% | WordPress re-encodes at 82% by default. Upload at 90% → WordPress at 82% = two lossy passes. Consider uploading WebP instead. |
| Thumbnails / icon sets | 70–80% | Small display means artifacts invisible. Maximum byte savings. Avoid for images with text or logos. |
Features
100% Private
Your images are processed locally in your browser. Nothing is ever uploaded to a server.
Quality Control
Fine-tune JPEG quality from 10% to 100% to hit the exact size vs. fidelity balance you need.
Batch Convert
Drop dozens of PNGs at once — images convert in parallel using a multi-worker pool.
Completely Free
No account, no credit card, no watermarks. Unlimited conversions, no strings attached.
Instant Results
Canvas API conversion — a typical photo finishes in under two seconds.
Works Everywhere
Any modern browser on desktop, tablet, or phone — no app to install.
Bulk PNG to JPEG Conversion
Need to convert an entire folder of PNG images to JPEG? Enable batch mode in the converter above — no file count limit, everything processes in your browser, and you can download all converted JPEGs as a single ZIP.
Toggle "Batch convert" in the options panel. The drop zone expands to accept multiple PNG files at once.
Drag and drop as many PNG files as you need. Use "Add more files" to append images after the initial drop.
The quality slider applies to every file in the batch — one setting converts the entire folder consistently.
Download each JPEG individually or grab them all in one ZIP. 100% in your browser — nothing uploaded.
PNG vs JPEG — What's the Difference?
PNG uses lossless DEFLATE — every pixel is stored exactly, producing larger files. JPEG uses lossy DCT compression, discarding imperceptible detail for dramatically smaller sizes.
PNG supports a full 8-bit alpha channel (smooth semi-transparency). JPEG has no transparency — pixels that were transparent become white after conversion.
PNG: logos, screenshots, illustrations, UI graphics, anything with text or sharp edges. JPEG: photographs, product images, blog photos, hero images — anywhere file size matters.
A typical 4 MP photo: PNG ≈ 12 MB, JPEG at 85% ≈ 1.5 MB. That's an 87% size reduction. For web delivery, JPEG wins by a wide margin for photographic content.
Software Reference: PNG to JPEG in Every Tool
How PNG to JPEG conversion works across the most common design and editing applications — including what settings each tool exposes and where Convertlo fits in the workflow.
| Software | PNG → JPEG Method | Quality Control | Recommended Workflow |
|---|---|---|---|
| Adobe Photoshop | File → Export → Save for Web | 1–12 scale (12 = max, ≈95%) | Use "Save for Web" at quality 8–10 for web; 11–12 for print delivery |
| GIMP | File → Export As → .jpg | 0–100% slider | Free and full-featured. Enable "Show preview" to compare sizes before export |
| Figma | Export panel → JPEG format | No quality slider (fixed) | Export as PNG from Figma → convert here for quality control. Figma's JPEG export quality cannot be tuned. |
| Canva | Download → JPG format | No quality control | Download as PNG for maximum quality → convert here at 85% for web delivery |
| Affinity Photo | File → Export → JPEG | 1–100% slider | Excellent quality control. Includes chroma subsampling options and ICC profile embedding |
| Adobe Lightroom | File → Export → JPEG | 0–100% quality | Best for RAW → JPEG workflows. Has color space and metadata embedding options |
| Mac Preview | File → Export → JPEG | Low / Medium / High / Best | Quick single-file conversion. "High" ≈ 85%. Batch: use sips CLI or Convertlo |
| Windows Photos / Paint | Save as → JPEG | None (fixed ~90%) | Fine for casual use. For web optimization use Convertlo to hit exact quality targets |
| Convertlo (this tool) | Drop PNG → Convert | 10–100% full slider | Free, batch, resize, crop. Best when Figma/Canva give no quality control. 100% browser — no upload. |
Task-Completion Workflows
Step-by-step workflows for common PNG to JPEG conversion scenarios — covering the right quality setting, tool order, and pitfalls to avoid for each destination.
- Export from Figma as PNG (not JPEG — no quality control in Figma)
- Drop the PNG here → set quality to 88%
- Upload the JPEG to WordPress Media Library
- WordPress will re-encode at its 82% default on the way in
- Finish design in Figma or Canva, export as PNG at 2× resolution
- Convert here at 92% quality (Instagram recompresses — give it high quality source)
- For Instagram grid posts: crop to 1:1 (1080×1080) using the crop tool above
- Upload JPEG to Instagram — Stories/Reels accept JPEG directly
- Enable Batch mode → drop all PNG photos at once
- Set quality to 80% (target under 500 KB per image)
- Download all as ZIP → send the ZIP or individual JPEGs
- Keep the original PNG files as your master archive
- Start with PNG from your photo editing software
- Use the resize tool → set width to 1000–2000px (platform recommendation)
- Convert at 85% quality
- Upload JPEG to Shopify or WooCommerce
- Convert PNG to JPEG at 82% for immediate LCP improvement
- Then convert the JPEG to WebP for a further 25–35% reduction
- Serve WebP with JPEG fallback using HTML picture element
- Run Google PageSpeed Insights to confirm LCP improvement
- Enable "Batch convert" toggle in the converter above
- Drop all PNG files from your folder at once (no limit)
- Set quality once — applies to all images in the batch
- Click "Download ZIP" to get all JPEGs in one archive
Did You Know?
In 1996, Unisys started enforcing patents on the LZW algorithm used in GIF. The PNG format was created by the internet community as a free, patent-unencumbered alternative. The name is sometimes jokingly expanded as "PNG's Not GIF" — a programmer's recursive acronym.
The Joint Photographic Experts Group published the JPEG standard in 1992, making it one of the oldest digital image formats still in daily use. Despite its age, JPEG remains the most common photo format on the internet — a testament to how well its compression algorithm was designed.
JPEG splits an image into 8×8 pixel blocks and applies a Discrete Cosine Transform (DCT) to each one, storing only the most visually significant frequencies. This is why heavily compressed JPEGs show blocky "JPEG artifacts" — you're literally seeing the block grid when too much data is thrown away.
PNG can store 16-bit values per color channel (48-bit total), capturing vastly more color gradations than JPEG's 8-bit limit. This makes PNG the format of choice in professional photography and medical imaging workflows, where color precision and bit depth matter more than file size.
Extensive perceptual quality research has shown that JPEG quality settings above 85% produce files visually indistinguishable from the original on any normal display. This is why web performance guides universally recommend 80–85% as the sweet spot — you get maximum compression with zero perceptible quality loss.
PNG's compression layer uses the DEFLATE algorithm — the exact same algorithm inside ZIP and gzip files. This means a PNG is technically a DEFLATE-compressed raw pixel stream. Some tools can even open the raw pixel data inside a PNG using ZIP utilities, though you'll just see uncompressed bitmap data.
The jpegtran tool can rotate a JPEG image in multiples of 90° without decoding and re-encoding the pixel data — preserving the original quality perfectly. Most image editors don't use this technique and re-encode on every save, which accumulates quality loss over time. Always start from your PNG original when possible.
When NOT to Convert PNG to JPEG
JPEG is the wrong choice in several common situations. Knowing when to stay in PNG — or switch to WebP — prevents irreversible quality loss and broken designs.
JPEG fills all transparent pixels with white. A PNG logo for a website overlay becomes a white-boxed image in JPEG format, breaking your design entirely.
JPEG's DCT algorithm operates in 8×8 pixel blocks. On sharp edges — text, thin lines, UI screenshots — this creates visible blurring and ringing artifacts, even at 85% quality.
Keep PNG as your working master. Convert to JPEG only for final delivery. Every edit-and-save cycle on a JPEG re-applies lossy compression, compounding artifacts each pass.
PNG supports 16-bit per channel (48-bit total). JPEG only supports 8-bit. Converting a 16-bit scientific, medical, or RAW-processed PNG to JPEG permanently discards half the color precision.
JPEG's algorithm is optimized for photographic gradients. Solid-fill vector-style illustrations get minimal size reduction (only 20–40%) and visible DCT artifacts around color boundaries.
If your PNG was created from a JPEG (screenshot a JPEG, or "Save as PNG" from a JPEG), the DCT artifacts from the original JPEG are already baked in. Converting back to JPEG re-encodes those artifacts — quality loss is compounded.
Troubleshooting Common Problems
My JPEG has a white background — the PNG had transparency
This is expected. JPEG has no alpha channel support — all transparent pixels must be filled with a solid color before JPEG encoding. The converter fills them white. If you need to preserve transparency, use WebP (convert with the PNG to WebP converter). For logos on colored backgrounds, match the fill color to your background before converting.
The JPEG looks blurry on text and sharp edges
JPEG is designed for photographs, not screenshots or text. The DCT block algorithm creates visible artifacts on sharp horizontal/vertical edges at any quality setting. For screenshots, diagrams, or images with text: keep as PNG, or use WebP lossless mode. If you must use JPEG, set quality to 95%+ to minimize the effect.
My JPEG file is larger than the original PNG
This happens at 90–100% quality settings. JPEG at 100% stores near-full-precision DCT coefficients and can actually exceed PNG file size for flat-color images. JPEG is only smaller than PNG for natural photographic content at 85% or lower. Reduce the quality slider to 80–85% for web delivery.
Colors look slightly different in the JPEG output
Two possible causes: (1) If your PNG was 16-bit (from Lightroom or a camera RAW processor), JPEG reduces it to 8-bit — subtle gradients lose precision. (2) Color profile mismatch: if your PNG embeds a non-sRGB profile (Display P3, ProPhoto), some browsers display it differently than the sRGB JPEG output. The Canvas API converts to sRGB on export.
Batch conversion is slow for large files
The Canvas API decodes and re-encodes each image sequentially for very large files. The converter runs 2–4 images in parallel based on your device's CPU cores. For a folder of 50+ large PNGs, expect 1–3 minutes total. Individual progress is shown per file in the batch list.
The Convert button stays disabled
The converter detects the file type by reading the file signature (magic bytes), not just the file extension. A file named .png but containing JPEG or WebP data will not be accepted as PNG input. Check the actual format by right-clicking → Properties → "Type of file". Rename if needed and re-upload.
Glossary
Portable Network Graphics. Lossless raster format using DEFLATE compression. Supports full 8-bit alpha transparency and 16-bit color. Best for screenshots, logos, and graphics.
Joint Photographic Experts Group. Lossy format using DCT compression. No transparency support. 8-bit color. Dominant photo format since 1992. Files 5–10× smaller than PNG for photos.
The mathematical core of JPEG. Converts 8×8 pixel blocks from spatial to frequency domain. High-frequency detail (imperceptible to human vision) is discarded to achieve compression.
Per-pixel transparency layer. Values 0 (fully transparent) to 255 (fully opaque). PNG and WebP support alpha. JPEG does not — transparent pixels become white on conversion.
Data encoding where original data is perfectly recoverable. PNG uses DEFLATE (lossless) — every pixel stored exactly. No quality loss, but larger file sizes than lossy formats.
Compression that permanently discards some data. JPEG discards high-frequency visual detail that human vision struggles to detect. Once discarded, original data cannot be recovered.
JPEG quality setting (1–100%). Controls DCT quantization aggressiveness. At 85%, output is visually indistinguishable from original. At 70% and below, block artifacts become visible.
Lossless compression algorithm used in PNG (and ZIP, gzip). Combines LZ77 and Huffman coding. A PNG is essentially a DEFLATE-compressed raw pixel stream in a standard container.
Compounding quality degradation from repeated lossy re-encoding. Converting JPEG→PNG→JPEG applies lossy compression twice on the same image, magnifying artifacts. Always start from PNG.
Browser-native HTML5 API for 2D pixel manipulation. Convertlo uses Canvas API to decode PNG pixel data and re-encode as JPEG entirely in your browser — no server upload required.
Bits per color channel. PNG: 8-bit or 16-bit per channel. JPEG: 8-bit only. A 16-bit PNG from Lightroom or Photoshop loses half its color precision when converted to JPEG.
JPEG technique storing luminance at full resolution but reducing chrominance resolution. Human vision is more sensitive to brightness than color, so 4:2:0 subsampling has minimal visible impact.
Frequently Asked Questions
Will transparent areas in my PNG be preserved?
How much smaller will my JPEG be?
What quality setting should I use?
Does PNG to JPEG conversion reduce quality?
Why can't I open my PNG in Outlook or Word?
Is this PNG to JPEG converter free?
Can I batch convert multiple PNGs to JPEG?
Is PNG or JPEG better for photos?
Why are PNG files so much larger than JPEG?
Does my PNG file get uploaded to a server?
Can I convert PNG to JPG on iPhone?
Will converting PNG to JPEG improve my website SEO?
The Complete PNG to JPEG Guide
Everything you need to know about converting PNG to JPEG — what actually happens during the conversion, why JPEG has no transparency, how to choose the right quality for every use case, and the universal rule every designer should follow.
What Happens During PNG to JPEG Conversion
When you convert a PNG to JPEG, the browser's Canvas API first fully decodes the PNG — reading every pixel's red, green, blue, and alpha values from the DEFLATE-compressed stream. The alpha channel (transparency) is then composited against a white background, because JPEG has no mechanism to store per-pixel opacity. The resulting RGB pixel grid is then encoded using the JPEG algorithm: the image is split into 8×8 pixel blocks, each block is run through a Discrete Cosine Transform (DCT), which converts spatial pixel values into frequency components. High-frequency coefficients (imperceptible fine detail) are quantized (rounded) aggressively based on the quality setting. Finally, the quantized coefficients are Huffman-coded into the output JPEG stream.
Why JPEG Has No Transparency
JPEG was standardized in 1992 specifically for photographic images. Photographs have no concept of transparency — a pixel is always some color. The JPEG standard was therefore written with no alpha channel. In contrast, PNG was designed in 1996 explicitly to support transparency (replacing GIF), which is why it has a full 8-bit alpha channel. The consequence: every transparent pixel in a PNG becomes opaque white in a JPEG. This is not a bug — it is a fundamental format limitation. Workaround: if you need both small file size and transparency, convert to WebP instead, which supports alpha channel and is 25–35% smaller than JPEG.
The 85% Rule — Why It Works
Decades of psychovisual research have consistently found that JPEG quality settings above approximately 85% produce outputs that are visually indistinguishable from the original under normal viewing conditions. This is because the human visual system is significantly less sensitive to high-frequency luminance changes and has even lower sensitivity to color detail. The JPEG quality factor controls how aggressively DCT coefficients are quantized (rounded) in each 8×8 block. At 85%, only the high-frequency coefficients your eyes genuinely cannot see are heavily rounded — the result looks identical to the PNG at 1/5 to 1/10 the file size. At 100%, almost no quantization occurs and files can actually exceed PNG in size. At 70%, block artifacts become clearly visible on smooth gradients and fine edges.
Choosing Quality for Your Workflow
The optimal quality depends on the destination: 80–85% for web photos (invisible quality loss on screens, maximum LCP benefit). 75–82% for email (target under 500 KB, screen DPI means high quality wastes bytes). 90–92% for social media (Instagram, Facebook re-compress on upload — give them high-quality source). 92–95% for print review (higher fidelity for print-viewing distances). One important nuance: platforms like WordPress (82% default), Instagram, and Shopify apply their own compression when you upload. This means uploading at 100% quality still results in a re-encoded output — factor this in when choosing your export quality.
PNG vs JPEG vs WebP — When to Use Each
Use JPEG for photographs and realistic images on the web — it achieves 60–80% smaller files than PNG for photographic content at visually identical quality. Use PNG for screenshots, logos, icons, UI graphics, and any image requiring transparency, text sharpness, or 16-bit color precision. Use WebP for the best of both worlds — WebP is 25–35% smaller than JPEG for photos and supports a full alpha channel for transparency, with 97%+ browser support as of 2026. The practical production workflow: photographs go PNG → JPEG (for immediate compatibility) → WebP (for performance). Graphics with transparency stay as PNG or become WebP lossless.
Batch Conversion Best Practices
When batch converting a folder of PNGs to JPEG, set quality once before adding files — the same setting applies to the entire batch. Conversions run in parallel (2–4 images at a time based on your CPU cores), so 20 photos typically finish in 10–15 seconds. Download the batch as a ZIP for easy file management. The critical workflow rule: store your original PNGs permanently as masters. The JPEG batch outputs are delivery copies — treat them as disposable. If a client later needs higher quality or a different format, you can always re-convert from the original PNG without any generation loss.
People Also Ask
Is PNG Better Than JPEG?
It depends on the content. PNG is better for screenshots, logos, UI graphics, line art, and any image with flat colors, transparent areas, or text — because its lossless compression preserves every pixel exactly and supports a full alpha channel. JPEG is better for photographs, product images, and any realistic image — because its lossy compression achieves dramatically smaller files (60–80% smaller) at near-identical visual quality. The rule: PNG for graphics, JPEG for photos.
How Do I Convert PNG to JPG Without Losing Quality?
Set the JPEG quality slider to 85–92% when converting. At 85%, the output is visually indistinguishable from the original PNG on any normal display — the human visual system can't detect the difference. For print or images that will be edited further, use 92–95%. The critical point: always convert from your original PNG master, not from a JPEG. Converting JPEG→PNG→JPEG re-encodes lossy data and compounds quality loss each round.
Why Does My PNG Have a White Background After Converting to JPEG?
JPEG simply does not support transparency at all — it's a format limitation, not a bug. Any transparent areas in your PNG are displayed as white in the JPEG output, because the converter fills the alpha channel with white before encoding. If you need to preserve transparency, either keep the file as PNG, or convert to WebP — which supports full alpha channel transparency and is 25–35% smaller than JPEG for photographic content. Most modern browsers support WebP.
Can Converting PNG to JPEG Affect Image Colors?
Slightly, in two ways. First, JPEG uses lossy compression that can introduce very minor color shifts in smooth gradients and subtle tone transitions — invisible at 85%+ quality but potentially noticeable at low quality settings. Second, PNG supports 16-bit color channels (48-bit total), while JPEG only supports 8-bit (24-bit total). If your PNG was a 16-bit professional image, the JPEG output will reduce that to 8-bit. For standard 8-bit web images, colors look identical at 85%+ quality.
Should I Use PNG or JPEG for My Website?
Use JPEG for all photographs and realistic images on your website — it dramatically reduces file size and improves Core Web Vitals. Use PNG for UI elements, logos, and graphics that require transparency or pixel-perfect sharpness. For the best of both worlds — smaller than JPEG and supporting transparency — use WebP, which is now supported by 97%+ of browsers. Google PageSpeed Insights recommends WebP via its "Serve images in next-gen formats" audit. A practical rule: convert your PNG photos to JPEG immediately, and consider converting everything to WebP for production.