PNG to JPG Converter
This re-encodes PNG images as JPEG at quality 0.92, entirely in your browser. JPEG has no transparency, so anything see-through in the original is painted onto a white background first. That makes it a good trade for photographs and a poor one for screenshots, logos and anything built out of sharp text.
Click to choose files or drag and drop
Supported types: image/png, .png (Max: 50 MB)
Transparency is flattened onto white, permanently
JPEG has no alpha channel. Every image is drawn onto a solid white rectangle before it is encoded, so anything transparent in the PNG comes out white. Partial transparency blends instead of vanishing. Anti-aliased edges, soft drop shadows and feathered glows are mixed with white in proportion to their opacity. That is why a converted logo can look correct on a white page and show a pale fringe, or an obvious box, on a dark one. None of this is recorded anywhere. The white is baked into the pixels, so converting the JPG back to PNG just gives you an opaque image. The background is always white and there is no color picker, so if you need a different color behind the artwork, composite it in an image editor first and convert after that.
Convert photos. Think twice about screenshots.
PNG is lossless, and it compresses long runs of identical pixels very efficiently. That is exactly what screenshots, UI exports, charts and line art are made of. JPEG works the other way. It splits the image into 8x8 blocks and throws away fine detail, which leaves ringing: faint speckle clinging to hard edges. Black text on a light background, one-pixel borders and flat-color boundaries show it first. Color is also stored at lower resolution than brightness, so thin colored lines and colored text smear worst. The file size argument can reverse too. A screenshot re-encoded at 0.92 is often larger than the PNG it came from. Photographs are the opposite case. They have no hard edges and plenty of gradient, so JPEG models them well, and the same photo kept as PNG is usually several times bigger for no visible gain.
What quietly changes besides the compression
Re-encoding alters a few things beyond file size. 16-bit PNGs drop to 8 bits per channel, because JPEG stores nothing deeper. The image is drawn on an sRGB canvas, so a wide-gamut Display P3 file, which is what recent iPhones and Macs produce, is converted to sRGB and very saturated colors can shift. Text chunks and any embedded color profile are not carried over; the output holds pixels and nothing else. The base filename stays the same and only the extension changes. Files are converted one after another rather than in parallel, and any image larger than roughly 268 megapixels in total area is refused by the browser canvas.
How to convert PNG to JPG
- Drop your PNG files onto the upload area, or click it to browse. Adding several at once is fine; they are converted one after another.
- Press 'Convert to JPG'. Each image is drawn onto a white background before encoding, so give any file that had transparency a proper look before you keep it.
- Read the size badge on each row. Green means the JPEG came out smaller. Amber with a plus sign means it grew, which is a strong hint that image should stay a PNG.
- Download files individually, or use 'Download all' to take them as one ZIP when you converted more than one. 'Start over' clears the list.
Frequently Asked Questions
My logo now has a white box around it. Can I get the transparency back?
No. The transparent pixels were blended with white before encoding, and JPEG has nowhere to store an alpha channel, so that white is now ordinary image data. Converting the JPG back to PNG gives you a PNG with an opaque white rectangle, not the original cutout. Keep the source PNG and re-export from it whenever you need transparency again.
Why did my screenshot get bigger instead of smaller?
PNG compresses long runs of identical pixels extremely well, and a screenshot is mostly flat blocks of color. JPEG cannot exploit that, and it spends bits describing the fine detail it introduces around text and edges. At quality 0.92 the result is frequently larger than the file you started with, which is what the amber badge in the results list is telling you. For that kind of image the honest answer is to keep the PNG.
Will small text still be readable afterwards?
It stays legible, but it stops looking clean. JPEG works on 8x8 pixel blocks and discards high-frequency detail, so hard edges pick up faint speckle known as ringing, most visible around dark text on a light background. Screenshots of documents, code and interfaces are the worst case for this. Photographs contain almost no edges of that kind and hold up fine.
What does quality 0.92 mean, and can I lower it?
It is the JPEG encoder setting on a scale from 0 to 1, and it is applied to every file here. 0.92 sits deliberately near the top: on photographs the difference is hard to spot even at full zoom, while the file is still far smaller than a lossless original. There is no slider, because a lower setting makes the edge artifacts above much more obvious for very little extra saving. Each run encodes from your source file, so converting the same image twice does not stack up losses.
Does the file get uploaded anywhere?
There is no upload step on this page. Your browser decodes the PNG, draws it to a canvas and asks that same browser to encode a JPEG, so the bytes never leave the tab's memory. No server receives the image, which means there is nothing sitting somewhere to expire or be deleted later, and no retention policy you have to trust.