Convert PNG to JPG — the honest guide (quality, transparency, batch)

The short version

1. Drop your .png file on the converter.
2. Leave quality at 85 (the sweet spot — invisible loss, big size win).
3. If your PNG has transparency, pick a background colour (default white). JPG can't store transparent pixels — we have to fill them.
4. Click Download. Done.

If that's all you needed, go. The rest of this post is for when the result looks wrong, when you're converting hundreds of files, or when you're deciding whether to convert at all.

Why anyone converts PNG to JPG

PNG is lossless. Every pixel is preserved exactly. That's great for screenshots, logos, diagrams, and anything with crisp edges or flat colour. The cost is file size: a typical 1920×1080 photo saved as PNG is 3–5 MB. The same photo as JPG at quality 85 is 200–400 KB. That's a 10× difference for no visible quality loss on a photo.

People convert PNG to JPG for one of three reasons:

• Smaller file size for upload — email attachments, web forms, chat apps, WordPress media libraries. Most CMS platforms cap uploads at 2–10 MB, and a PNG photo blows past that instantly.
• Maximum compatibility — JPG is the lowest common denominator. Every browser, every photo kiosk, every old piece of software reads it.
• Somebody (a boss, a form, a printer) asked for it. This is the most common reason. Just convert and move on.

What you lose going PNG → JPG

This is the part most tutorials skip. Three things can change when you convert:

1. Transparency (always)

JPG has no alpha channel. Any transparent or semi-transparent pixel in the PNG has to be painted onto a solid background before encoding. Our tool lets you pick the colour — white by default, because that matches most documents and web pages. If your logo was meant to sit on a dark page, pick black (or the actual hex colour) in the advanced settings.

If you need transparency, don't convert to JPG. Keep the PNG, or export as WebP instead — WebP supports alpha and compresses better than PNG. JPG is simply the wrong target when you need a see-through background.

2. Lossless precision (always)

JPEG is lossy. The encoder throws away high-frequency detail your eye rarely notices and fills in the gaps with blocky DCT coefficients. At quality 85 you can't see it on a photo. On a screenshot with sharp text edges, black-on-white UI, or a line drawing, you can. Red text on white becomes faintly pink and fuzzy. Diagonal lines pick up halos.

If you're converting a screenshot, don't use JPG. PNG stays PNG. Or switch to our reverse tool if someone already handed you a JPG screenshot with artefacts and you need to re-host it cleanly (though you can't recover detail that was thrown away).

3. 16-bit depth and wide colour (if your PNG had them)

Most PNGs are 8-bit sRGB. Some exports from Photoshop, Affinity, or raw-photo workflows are 16-bit with a wide-gamut colour profile (Adobe RGB, Display P3, ProPhoto). JPEG caps at 8-bit and is usually tagged sRGB. Converting collapses the extra precision. For screens, this is invisible. For print, ask first.

What the quality slider actually controls

Our tool exposes a quality slider from 30 to 100. It sets the JPEG quantization strength — how aggressively the encoder rounds off DCT coefficients in each 8×8 block.

• 100: minimum quantization. File is big. There's still loss because JPEG's colour subsampling kicks in by default — just very little. Use only if the file will be re-edited.
• 85 (our default): matches what most DSLRs save out of camera and what Photoshop's "High" preset targets. Visually identical to the source at normal viewing distance.
• 70–80: acceptable for web, email, social media. Small softening visible at 100% zoom.
• 50–60: visible blocks on gradients, skies, flat colour. Use only with a hard size budget.
• Below 50: obvious artefacts. Don't.

Real numbers from a 1920×1080 phone photo (original PNG: 4.1 MB):

• Quality 100: 1.8 MB
• Quality 90: 620 KB
• Quality 85 (default): 380 KB — looks identical to the PNG
• Quality 75: 240 KB — looks identical unless you pixel-peep
• Quality 60: 150 KB — faint softening, noticeable only on side-by-side compare
• Quality 40: 85 KB — clearly degraded, visible blocks on the sky

How our tool compares (honestly)

PNG to JPG is commodity functionality. Every serious image tool does it. The question is what you're optimising for. Here's where each option actually wins:

The honest summary: if you already pay for Photoshop, use it for anything colour-critical. If you're on a Mac and need one file converted right now, Preview is fine. For everything in between — batch work, no-sign-up quick conversions, files you'd rather not upload to a stranger — our PNG to JPG tool is the fastest path.

Batch vs one-off

For a single PNG, any tool works. Batch is where the differences show up. Three real workflows:

A folder of screenshots

Drop the whole folder on the tool. We process them sequentially in the browser, show progress per-file, and ZIP the output. No upload, so it scales to hundreds of files as long as each stays under the per-file cap. Filenames are preserved with.jpg swapped for .png.

Exports from a design tool

Figma, Sketch, and Affinity let you export as PNG in bulk. Drop the whole export folder on PNG to JPG, leave quality at 85, pick a background colour that matches where the assets will live. That's it. If the assets need to stay transparent, you shouldn't be converting to JPG in the first place — export directly as JPG from the design tool, or keep PNG.

Recurring pipeline

If you're doing this weekly, three options work well: our public API (/api/docs — bearer-authed, zero-retention, target=jpeg on the image endpoint), sharp locally (Node / npm), or CloudConvert's paid API. For one-off or ad-hoc batches, the drag-and-drop tool beats a scripted pipeline every time.

Where our tool works well — and where it doesn't

Works well

• One-off conversions of photos, screenshots, exports
• Batches of up to a few hundred small-to-medium PNGs
• Privacy-sensitive files (stays in your browser for small sizes)
• Anything where you just want the file and don't want to sign up

Doesn't work (well) yet

• Files over the free-tier cap — paid plans lift to 1.5–5 GB per file, but free stops at 4 MB
• Wide-gamut (Display P3, Adobe RGB) colour profile conversion — we preserve the profile but don't offer a conversion dropdown yet
• Turning a JPG screenshot back into a clean PNG — once JPEG has thrown away detail, it's gone. See JPG to PNG for the reverse direction when you start with a PNG-worthy source.

Tips for the best result

• Keep quality at 85 unless you have a reason. Going higher bloats the file for no visible gain. Going lower looks bad on anything with text or sharp edges.
• Pick the background colour to match its destination. Logo going on a white slide? White. Going on a dark website? Use that hex. Default white is usually fine.
• Strip EXIF unless you need it. Screenshots don't carry EXIF. Phone photos do, including GPS. Our default is strip — toggle on "Preserve EXIF" in advanced settings only when you need the capture date or camera details.
• If the source is a screenshot, reconsider. PNG-to-JPG is the wrong move for text-heavy images. Try compressing the PNG as PNG first (optipng-class optimisation), or keep it as PNG.
• For photos destined for the web, consider WebP. WebP compresses 25–35% smaller than JPG at the same perceptual quality and is supported by every modern browser. If you already have WebP files and need JPG for a legacy target, our WEBP to JPG tool does the reverse.

Common questions

Will I lose quality converting PNG to JPG?

At quality 85 on a photo, no — not visibly. On a screenshot, logo, or line drawing, yes — JPEG blurs the sharp edges that made PNG a good choice in the first place. Rule of thumb: photos tolerate JPG, graphics don't.

What happens to transparent pixels?

They get painted onto a solid background before encoding. Our tool defaults to white but lets you pick any colour in the advanced settings. If your graphic needs a transparent background, don't convert to JPG — keep it as PNG or use WebP.

Is this tool really free?

Yes, up to 4 MB per file, unlimited conversions per day, no watermark, no sign-up. Paid tiers raise the per-file cap for larger files and lift the batch size. Quality and speed are identical across tiers.

Do my files get uploaded to your server?

Small PNGs are decoded and re-encoded entirely in your browser — the bytes never leave your machine. Larger files use direct-to- storage upload, get processed in memory, and are auto-deleted within the hour. No disk writes, no database, no analytics on file contents.

Can I convert JPG back to PNG?

Yes — our JPG to PNG tool does the reverse. But note: JPG's loss is permanent. Converting back to PNG just wraps the already-degraded pixels in a lossless container. The quality you threw away is gone.

Which is better, PNG or JPG?

Neither. They solve different problems. PNG for graphics with sharp edges, text, transparency, or anything you'll re-edit. JPG for photos where you care about file size. If both apply or neither is obvious, WebP is usually the right modern answer.

Ready?

PNG to JPG →. Drop a file, pick a background colour if you have transparency, click download. Free, in your browser, no sign-up.