Free, in your browser — your image never leaves you. Transparent areas become white.
or drop the image here
Converting…
RoundCut converts PNG to JPG entirely in your browser using the platform's native image encoder. The file is never uploaded. Transparent areas of the PNG are flattened to white in the JPG, since JPG does not support transparency. The output is typically 30 to 50 percent smaller than the original PNG at near-lossless quality for photographs.
Drop a PNG file on the upload area (or click to pick one). The conversion runs the moment the file lands — there is no "Convert" button to chase. When the result is ready, the stats line shows the input and output size, and the Download button saves the JPG to your device.
JPG has no alpha channel, so any transparent pixel in your PNG must be replaced by a solid color. The conversion flattens transparency to white. If you need a different background color, paint it onto the PNG in your editor before converting — or keep the PNG and place it over the destination background directly.
Keep PNG for logos, icons, screenshots with sharp text, line art, anything with transparency or that you will edit again. Switch to JPG for photographs, hero images on a webpage, anything destined for social platforms that recompress JPG anyway. JPG files are typically 30–50 percent smaller than the equivalent PNG, which matters for page-load speed.
The JPG output is encoded at a near-lossless setting tuned for photographs — visually indistinguishable from the source PNG to the naked eye, and typically 30 to 50 percent smaller than the original. Graphics with sharp edges, fine text, or hard color transitions may show subtle JPG artifacts at any quality setting; for those cases the PNG itself is the right format and converting is a downgrade. There is no quality slider — the chosen setting is what every conversion uses.
The conversion runs in the browser's native image engine. Nothing is uploaded, nothing is logged, nothing is queued on a server. If you open DevTools and watch the Network panel while you convert, you will see zero outbound image requests. The same code path runs on every browser — there is no server fallback.
Yes — JPG uses lossy compression. The encoder is tuned to a near-lossless setting, so for photographs the result is visually indistinguishable from the source PNG. Graphics with sharp edges, fine text, or solid color blocks may show subtle artifacts no matter the setting; for those, stay on PNG. If you may need to edit again, keep the original PNG and treat the JPG as the export.
JPG does not support transparency. The conversion flattens transparent pixels to white. If you need a non-white background, paint the color onto your PNG in an editor before converting, or keep the PNG so the transparency stays available.
Yes. The encoder strips EXIF, IPTC, and XMP metadata. ICC color profile is sometimes preserved (depends on the browser), so the result is sRGB-safe but other profiles are not guaranteed. If you need EXIF intact, use a dedicated metadata editor before or after converting.
Your file never leaves your browser. The conversion runs entirely on your device using the platform image engine — no upload, no server, no data collection. You can verify it with DevTools open: there are zero outbound image requests during conversion.
Not yet — the current version converts one file at a time. Batch conversion is planned for a later release.
Not in this tool — the encoder uses a single near-lossless setting that matches what photographers and the web expect. If you need a much smaller file for thumbnails, or a much larger one for print, use a dedicated compress tool after the conversion (or before, if you also want to resize).
