Converter · No upload

Convert PNG to JPG on your device

Convert PNG images to JPG at the quality you choose, with transparent areas filled white.

The sample is a 240×120 PNG drawn in this tab, with a translucent stripe. JPG has no transparency, so that stripe lands on white, and the re-encode is lossy at the quality you set.

Files already converted keep the quality they were made at; add them again to convert at a new setting.

Read here — Statusidle Files— OutputJPG Network since file read—

Undecodable PNGs fail, with browser reasons where available, and so do images too large for the browser’s canvas, which are not shrunk to fit. One JPG per file, default 0.92; quality changes affect pending encodes. An animated PNG becomes one still; the row does not flag it. Transparency is flattened onto white, 16-bit input becomes 8-bit, and text chunks, location data and colour profile are dropped. Takes .png.

How this converter works

The File API reads the selected PNG into memory, and the browser decodes it without an extra converter library. The page fills a canvas with white and draws the image over it, so transparent areas land on a white background. The canvas is then encoded as JPG at the selected quality and offered as a download link, all inside the tab.

The network meter uses PerformanceObserver, your browser’s resource-timing feed, to count the entries logged from the first file opened. Earlier page requests are not included, and neither are WebSocket connections, which this page does not open. For a separate check, watch the browser’s Network panel, or disconnect after the page has loaded and convert a file: a conversion that finishes offline needed no server. The methodology page explains the meter’s limits and the other checks.

JPG encoding is lossy, and the detail it discards cannot be restored. An animated PNG gives a single still JPG, with no choice of frame, and the output is 8-bit sRGB. Keep the PNG original for later editing or if you need the motion.

Frequently asked questions

Is my image uploaded anywhere?
No. The browser decodes the PNG, draws its pixels on a canvas and encodes the JPG in this tab. The network meter counts resource-timing entries from the first file read onward; earlier page requests and some network channels are outside its view. The methodology page explains how to check a conversion with the browser’s network tools or offline.
What happens to transparent areas?
They are flattened onto white, because JPG has no alpha channel. If you need transparency, keep the PNG or choose a format such as WEBP.
What quality setting should I use?
Start with the default 0.92 and look at the output. Try 0.7 when a smaller copy for sharing matters more than fine detail, or go higher if you can see artifacts; no setting makes every image look unchanged. Text and sharp-edged graphics show JPEG artifacts readily. Make each new JPG from the PNG, and avoid re-encoding JPG copies.
Will the JPG always be smaller than the PNG?
No. JPG’s lossy encoding often shrinks photographs, but PNG already compresses flat graphics, screenshots, logos and line art efficiently, and converting those to JPG can make the file larger while adding fuzzy text or edge artifacts. Each result row shows the original and output sizes, so compare size and appearance, and keep the original PNG.
Is metadata kept in the JPG?
No. The PNG’s text chunks and any location or creation metadata it holds are not copied through the canvas. The JPG encoder may write its own format metadata, so check the exported copy if particular fields matter to you.

Related tools