Two formats, two different jobs
Knowing when to convert PNG to JPG — and when not to — saves most people more bandwidth than any other single image decision. The two formats exist for different jobs, and using the wrong one is like using a screwdriver as a hammer: it works, but everything takes longer and looks worse. This post covers the rule for choosing, the one thing you lose in the conversion, and a workflow for converting batches without mistakes.
PNG is lossless, which means it preserves every pixel exactly. JPG is lossy, which means it throws away fine detail to shrink the file. For photographs, that tradeoff is a bargain: a 4-megabyte PNG photo typically becomes a 300-kilobyte JPG with no visible difference. For graphics with sharp edges — logos, icons, text, screenshots — that same tradeoff is a bad deal: JPG compression smears crisp edges into blurry halos that everyone can see.
The rule of thumb is simple: photos become JPG, graphics stay PNG. A sunset photo, a product shot, a portrait — convert to JPG. A logo on a transparent background, a diagram with text labels, a UI screenshot — keep as PNG. When in doubt, zoom in to 100 percent on an edge after conversion; if the edges look clean, JPG was fine.
The transparency trap
The one thing you genuinely lose converting PNG to JPG is transparency. JPG has no alpha channel, full stop — a point web.dev's guide to choosing the right image format makes when it maps each format to the jobs it handles well. A logo that floated on a transparent background will come out of the conversion on a solid background — usually white, sometimes black depending on the tool. This is the single most common conversion mistake: someone converts their transparent logo to JPG for a website, and suddenly it sits in an ugly white box on a colored page.
There are two honest fixes. If the image must stay transparent, do not convert — use the PNG. If you know exactly where the image will live, flatten it onto the matching background color first: a logo on a white website page converts perfectly to JPG once the transparency is replaced with white, because the background blends invisibly. What you cannot do is keep transparency and get JPG's small file size at the same time; that combination belongs to formats like WebP and AVIF, and the MDN image format guide maps out where each of them wins.
Now the how. The conversion itself takes seconds in any image tool. The part people get wrong is the quality setting. When converting, you are applying lossy compression to an image for the first time, so you have the full range of quality to play with. A quality setting of 80 to 85 percent is the sweet spot for photographs: files shrink dramatically and the artifacts stay invisible at normal viewing distance. Dropping to 60 percent saves more bytes but introduces visible blotches in smooth gradients like skies.
Quality settings and the screenshot mistake
A mistake that compounds quietly: converting a PNG screenshot to JPG at low quality. Screenshots are graphics — text, sharp edges, flat colors — exactly what JPG handles worst. If you must convert a screenshot, keep the quality at 90 or above, or better yet, reconsider whether it should be a JPG at all. Documentation pages full of mushy screenshots are almost always the result of someone batch-converting everything to JPG at the default setting.
Batch conversion is where a little planning pays off. Sort your images before converting: photos in one folder, graphics with transparency in another, screenshots in a third. Convert only the photos folder to JPG. This sounds obvious, but the typical messy conversion job is someone selecting an entire downloads folder — logos, photos, screenshots together — and converting all of it, then discovering the transparent logos and screenshots are ruined.
FreeToolsBox's Image Converter handles the conversion step itself: upload the PNG, pick JPG, download the result. Use it for the photo folder after you have done the sorting. It keeps the workflow in the browser with no installs, which matters most for batch jobs where you just want to move through files quickly.
Batch conversion without regrets
After converting, run the JPGs through FreeToolsBox's Image Compressor as a second pass. Conversion sets the format; compression fine-tunes the file size. The converter gives you a standard JPG, and the compressor squeezes out the remaining slack — often another 20 to 40 percent — without visible change. Two quick steps, one tiny file.
A worked before-and-after makes the difference concrete. Take a 3840-by-2160 phone screenshot of a photo-heavy page saved as PNG: roughly 6 megabytes. Converted to JPG at 85 percent quality: roughly 700 kilobytes, visually identical for the photographic parts. That same screenshot's text edges show slight softening — acceptable for sharing, not for archival. Now take a logo PNG with transparency at 1200 pixels wide: 300 kilobytes. Converted to JPG, the file is 90 kilobytes but the transparency is gone, replaced by a white box. On a dark website, that white box is a design disaster. The photo was a win; the logo was a loss. Same tool, different judgment.
Color shifts are a subtler issue worth one paragraph. PNGs can carry color profiles; JPGs can too, but some converters strip the profile during conversion. If your converted photo looks slightly washed out or shifted next to the original, the profile was dropped. The fix is a converter that preserves metadata, or simply comparing the before and after side by side. For casual web use this rarely matters; for photography portfolios it can.
A before-and-after that shows the stakes
Resolution needs a mention because people conflate it with format. Converting PNG to JPG does not change the pixel dimensions — a 2000-pixel-wide PNG becomes a 2000-pixel-wide JPG. If the file is still too big after conversion, the problem is dimensions, not format, and the fix is resizing first, then converting. Format and size are two separate levers; pull both in the right order.
What about WebP and AVIF? They are newer formats that beat both PNG and JPG in most cases — WebP supports transparency and lossy compression together, and AVIF compresses even further. The catch is compatibility: some older tools, email clients, and print workflows still expect JPG. For anything that leaves your control — client deliverables, uploads to third-party sites — JPG remains the safe universal choice. For your own website where you control the pipeline, WebP is worth considering — we compared all three formats side by side in WebP vs JPEG vs PNG.
The reverse conversion deserves a warning: converting JPG to PNG does not recover quality. The detail JPG discarded is gone forever; wrapping the file in a lossless container just makes it bigger without making it better. People do this hoping to fix a bad conversion, but it only inflates the file. Always convert from the best original you have.
The clean end-to-end workflow
Here is the clean workflow end to end. Gather your images and sort them: photos to convert, transparent graphics and screenshots to leave alone. Check the background situation for anything with transparency — if a transparent image must become JPG, flatten it onto its destination background color first. Convert the photos to JPG at 80 to 85 percent quality. Resize anything that is larger than its destination needs. Run the results through the compressor. Spot-check edges and backgrounds at 100 percent zoom.
One last check before you call it done: open the converted JPG on the actual background where it will live. A logo flattened onto white looks perfect on a white page and terrible on a dark one, and this is the kind of thing you only catch by looking. Thirty seconds of verification beats re-doing a whole batch.
So the honest summary: convert PNG to JPG for photographs bound for the web, keep PNG for anything with transparency or sharp text edges, sort before batch converting, and treat compression as a separate final step. It is a small decision, but it is one you make hundreds of times — getting it right once pays off forever.
Email apps, file naming, and the final spot-check
Email and messaging apps are a special case worth calling out. Most of them recompress images automatically when you send them — WhatsApp famously shrinks photos aggressively. If you are converting to JPG specifically to send through one of these apps, you can often skip the conversion entirely and let the app handle it, since it will compress regardless. But if the recipient needs the full-quality file, send it as a document instead of a photo, and do your own conversion and compression first so you control the quality.
File naming during batch conversion saves real confusion. When a folder ends up with photo.png and photo.jpg side by side, it is easy to attach the wrong one. A simple convention — originals in a folder called masters, converted files in a folder called web-ready — keeps the pipeline clean. Archive or delete the working copies once the finals are in place; a folder full of photo-final-v2-really-final.jpg helps nobody.
One final check catches the mistakes automation misses: open three or four converted files at random and compare them against their PNG originals side by side. Look at edges, backgrounds, and any text. If those samples are clean, the batch is clean — conversion settings apply uniformly, so spot-checking is genuinely representative. It takes a minute, and it is the difference between assuming the batch worked and knowing it.