PNG to JPG: when (and when not) to make the switch

PNG to JPG is the most common image conversion on the web, and the reason is simple: file size. A 4000×3000 photo saved as a PNG can easily reach 15 MB; the same photo as a quality-92 JPG drops to under 2 MB with no visible difference at normal viewing distance. Multiply that by an album of 30 photos and you've gone from 450 MB to 60 MB — the difference between failing to attach to an email and sending it without a thought.

But not every PNG should become a JPG. The trade is real, and it's worth understanding before you bulk-convert a folder you'll regret later.

When PNG to JPG is a no-brainer

• Photos. JPG was literally designed for photographs. Its compression discards information your eye doesn't easily notice — gradient detail, shadow noise, micro-textures — and keeps the parts that matter.
• Web hero images. Page weight is a ranking factor in Google's Core Web Vitals. Converting a 3 MB PNG hero to a 200 KB JPG can shave a full second off LCP.
• Email attachments. Gmail caps at 25 MB; Outlook varies. JPG conversion is often the difference between sending and not.
• Social uploads. Most platforms re-compress to JPG anyway. Pre-converting gives you control over the quality target instead of inheriting their defaults.

When PNG to JPG is a mistake

• Screenshots with text. JPG's compression artifacts are most visible on sharp edges — exactly what text is. Stay PNG (or use WebP).
• Logos and graphics. Crisp colour boundaries get fuzzy. The 50-80% file size saving isn't worth the visual hit.
• Images with transparency. JPG doesn't support transparent backgrounds — they become white (or whatever fill colour you set) on conversion. If you need transparency, stay PNG or go WebP.
• Source material you'll edit again. JPG is lossy. Each save discards more detail. For files you'll re-edit, keep PNG (or a real source format like TIFF).

The quality slider is the whole game

JPG quality runs from 1-100 (or 0-1 as a decimal). The default in most tools sits around 90-92, which is effectively invisible from the source at normal viewing distance. The interesting thing about JPG quality is that it's logarithmic: dropping from 100 → 95 saves ~30% file size with zero visible change. 95 → 85 saves another 30% with a difference only visible if you zoom in and pixel-peep. Below 85, artifacts start showing up on close inspection.

For most workflows, 90-92% is the sweet spot. For aggressive web optimization where bandwidth matters, 80-85% is acceptable. Below 75, you're trading away visible quality for marginal additional savings.

How to convert PNG to JPG in your browser

Our JPG ↔ PNG converter handles batches in one shot. Drop your PNG files, pick JPG as the target format, set the quality slider, and download. The conversion runs entirely in your browser using the Canvas API — your photos are never uploaded to a server, which matters if you're converting personal photos, medical records, or sensitive client work.

For one-off conversions, the Universal Converter works just as well — drop a single PNG, pick JPG, done.

The transparency gotcha

Transparent PNGs become opaque when converted to JPG. By default we fill the background with white, which is usually what you want. If you need a different background colour — say to match a website's brand — convert the PNG to JPG only after compositing it onto your target background, otherwise the white edges will look out of place.

For images that genuinely need transparency, WebP is the modern answer: it supports alpha channels like PNG but compresses photo-like content nearly as efficiently as JPG. The Universal Converter can produce WebP output too.