Convert PNG to JPG
Convert PNG to JPG in your browser: batch files, choose a background colour for transparency, set quality, download instantly.
- Runs in your browser
- Files are never uploaded
- Free, no account
JPG has no alpha channel, so transparent pixels are painted with the colour below.
Metadata is stripped. Re-encoding rebuilds the file from raw pixels, so EXIF — GPS coordinates, camera model, serial number, capture time — and any XMP or IPTC block are dropped. Pixels are written in sRGB.
Nothing leaves this tab. The encoders are WebAssembly builds of libjpeg-turbo (MozJPEG), libpng/oxipng, libwebp and libavif running inside a worker on your machine.
How to convert PNG to JPG
- Drop one or more PNG files onto the box above, or click it to browse. Whole folders of files are fine — they are queued and converted one after another.
- Pick a background colour. JPEG cannot store transparency, so every see-through pixel has to be painted with something. White suits most documents; black or a brand colour suits images destined for a dark page.
- Set the quality slider. 85 is a safe default for photographs; drop to 70–75 when you need the smallest possible upload.
- Check the before and after size shown next to each file, then save the JPG — or download the whole batch as one ZIP.
Everything runs in this tab. The PNG is decoded to raw pixels, composited over your chosen background, and re-encoded with MozJPEG compiled to WebAssembly. No file is uploaded, so there is no queue, no size cap imposed by a server and no copy of your image left behind on someone else's disk.
What actually changes when a PNG becomes a JPG
PNG and JPEG solve different problems. PNG is lossless: it stores every pixel exactly, keeps a full alpha channel, and compresses by finding repetition — which works brilliantly on flat colour and terribly on photographs. JPEG is lossy: it converts the image to a frequency representation and discards the high-frequency detail your eye is least sensitive to, which works brilliantly on photographs and badly on text and hard edges.
Three concrete consequences of the conversion:
- Transparency disappears. There is no alpha channel in a baseline JPEG. Transparent pixels become the background colour you picked, permanently.
- Sharp edges soften. Around black-on-white text and thin lines you will see faint halos, called ringing. This is inherent to the codec, not to the encoder used here.
- Metadata is dropped. The output is rebuilt from pixels, so EXIF, XMP and IPTC blocks — including GPS coordinates and camera serial numbers — do not carry across.
Choosing a quality value
Indicative results for a 1920 × 1080 photograph that starts as a 3.2 MB PNG. Your own numbers will differ with image content — noise and fine texture cost far more bytes than smooth sky — but the ranking holds.
| Quality | Typical size | What you would notice | Good for |
|---|---|---|---|
| 95 | ~900 KB | Nothing, even when pixel-peeping | Archival, print, further editing |
| 85 | ~380 KB | Nothing at normal viewing size | The default for almost everything |
| 75 | ~230 KB | Slight softening in fine texture | Web pages, email attachments |
| 60 | ~150 KB | Visible blocking in flat areas | Thumbnails, previews |
| 40 | ~95 KB | Obvious artefacts | Placeholder images only |
When you should keep the PNG
- Screenshots and UI captures. They are mostly flat colour and text, which PNG compresses better and reproduces exactly. A JPG screenshot is often larger and always uglier.
- Logos, icons and line art. Same reason, plus you usually need the transparency.
- Anything you will edit again. Each JPEG save re-quantises the image; repeated cycles compound the damage.
- Images with soft shadows over varied backgrounds. Flattening onto a single colour will show a visible rectangle wherever the page background differs.
If your goal is a smaller file rather than JPEG specifically, PNG to WebP is almost always the better trade: it keeps transparency, keeps edges sharp, and still beats JPEG on size. To go from PNG to any other format — or to convert a mixed pile of files at once — use the universal image converter.
Questions
What happens to transparent areas?
JPEG has no alpha channel, so every transparent pixel has to be painted with something. The tool flattens transparency onto the background colour you pick — white by default — and you can preview the result before saving.
What quality setting should I use?
For photographs, 80–85 is the point where most people stop being able to tell the JPEG from the original. Below about 70 you start to see blocking around sharp edges; above 92 the file grows quickly for very little visible gain.
Will a PNG screenshot of text look worse as a JPG?
Usually yes. JPEG uses a frequency transform that smears the hard edges of text and line art into visible ringing. For screenshots, diagrams and logos, keep the PNG or convert to WebP instead — both stay sharp.
Is the EXIF and colour data kept?
No. The image is rebuilt from raw pixels, so EXIF, XMP and IPTC blocks are dropped and the output is written as plain sRGB. That is usually what you want before sharing a file publicly.
Can I convert a whole folder of PNGs at once?
Yes. Drop in as many PNGs as you like — there is no per-batch cap and no daily quota, because the encoding runs on your own CPU rather than a metered server. Multiple outputs come back as a single ZIP.