TinyFileLab

Home›Convert›Image to PNG

Nothing is uploaded — it all runs on your device

Convert any image to PNG

Lossless pixels and a real alpha channel — plus an honest answer about what converting a JPEG to PNG can and cannot do for it.

Drop any images here JPG, WebP, AVIF, GIF, BMP, SVG, HEIC — several at once
Longest side

PNG has no quality dial, so this is the only way to control the size of the output. A full-resolution phone photo saved as PNG lands somewhere between 15 and 40 MB.

Transparency

Keep it is what you want almost always. Flattening is for the occasional form or printer that rejects an alpha channel outright, and for cutting the size of a mostly-empty image.

No file selected yet
Nothing leaves your deviceNo server sees your files. Turn off your wi-fi and it still works.
No queue, no daily capConvert as many files as you want, as often as you want.
No watermark, no accountYou get a clean file, with the original filename.

What PNG is for

PNG stores every pixel exactly as it was handed over. Nothing is approximated, nothing is thrown away, and saving the same file fifty times changes nothing. It also carries a real alpha channel, so a cut-out logo keeps its transparent corners instead of acquiring a white box. Those two properties are the whole reason to convert into PNG, and they are why it is the default for screenshots, diagrams, icons, UI assets and anything that will be edited again later.

This page accepts anything your browser can decode — JPG, WebP, AVIF, GIF, BMP, SVG, and HEIC on Safari — identifies it from its first bytes rather than its extension, and writes a standard 8-bit PNG. Several files at a time, each with its own download, and a ZIP once there is more than one.

Converting a JPG to PNG does not repair it

This is the single most common misunderstanding about this conversion, so it is worth being blunt. JPEG compression is lossy and permanent. The blocky edges around text, the mottling in a blue sky, the coloured fringes around a dark line on white — those are baked into the pixels. PNG will preserve them perfectly and faithfully, at three to ten times the file size. It cannot reconstruct what the JPEG encoder discarded, and neither can anything else.

So converting JPG to PNG is worth doing when the file is about to be edited repeatedly, pasted into a document that will mangle it further, or handed to a tool that refuses JPEG. It is not worth doing to “improve quality”, and it is a bad idea for storing photographs: a folder of holiday pictures converted to PNG will be many gigabytes for no visible gain.

Size, and the only dial you have

PNG has no quality setting. Its compression is lossless, so the only way to make the output smaller is to hand it fewer or simpler pixels. That is what the longest-side control does, and it is a genuine resample with smoothing, not a display trick.

How much the file grows depends entirely on the content. Screenshots, flat-colour graphics and line art often come out smaller than the JPEG they came from, because PNG compresses large runs of identical colour extremely well. Photographs go the other way — grass, skin and sky have no repeating patterns to exploit, so a 2 MB HEIC or a 1 MB JPEG can easily become 20 MB. If that number is a problem, either scale down first or stay with JPG.

Transparency, animation and the odd corner cases

Alpha is preserved by default: a transparent WebP, AVIF or GIF comes out as a transparent PNG. The flatten options exist for the occasional upload form or print workflow that rejects an alpha channel outright, and for the case where an image is mostly empty and filling it makes the file much smaller.

Animated sources produce one still frame. PNG's animated cousin, APNG, is not what browsers give you from a canvas, so there is no honest way to offer it here — if the movement matters, keep the original or convert it to GIF instead. SVG is rasterised at the size written into the file; if you want to choose the export width precisely, SVG to PNG is built for exactly that. And as with every conversion on this site, EXIF does not survive: the output is pixels, not camera history.

Common questions

Will converting to PNG improve the quality of my JPG?

No. Whatever the JPEG encoder discarded is gone for good; PNG will store the damaged pixels perfectly and take up several times the space doing it. Convert for editing, transparency or compatibility, not for repair.

Why is the PNG so much larger than the original?

Because PNG throws nothing away while JPEG, WebP, AVIF and HEIC all do. Photographs are the worst case — a ten to twentyfold increase is normal. Screenshots and flat graphics often shrink instead.

Is transparency preserved?

Yes, by default. A transparent PNG, WebP, AVIF or GIF keeps its alpha channel all the way through. Choose one of the flatten options only if something downstream refuses files with transparency.

What happens to an animated GIF or WebP?

You get the first frame as a still PNG. Browsers do not expose an animated-PNG encoder, so offering one here would mean shipping a whole encoder for a format almost nothing asks for.

Is the output 8-bit or 16-bit?

Eight bits per channel, RGBA. That is what the browser canvas produces. A 16-bit source such as a raw export or a scientific TIFF will be reduced to 8-bit, which is fine for anything destined for a screen and not fine for further heavy editing.

Does anything get uploaded or stored?

No. The decode, the resize, the PNG encode and the ZIP all happen inside this page. There is no server component to send a file to, and nothing is kept after you close the tab.