IntactFile

AVIF to PNG — lossless, in your browser, nothing uploaded

Drop an AVIF and get a lossless PNG back — with transparency intact. AV1 decodes natively in modern browsers, so the whole conversion runs on your machine.

Your file never leaves your device — conversion runs in your browser. 0 bytes uploaded.

Drop a AVIF image file hereTap to choose a AVIF image file

Decodes the AV1 image in your browser and re-encodes it as PNG. Nothing is uploaded.

100% in your browser. 0 bytes uploaded — open DevTools → Network and watch. Your file is read, never sent.

In short

AVIF (AV1 Image File Format) stores AV1-coded pixels in an ISO base-media box container. Because AV1 decodes nativelyin current browsers, this converter is a clean, truthful operation: your browser decodes the image, draws it to a canvas, and re-encodes it as alossless PNG that keeps the alpha channel. You get a real .png — pixel-exact to what the AVIF decoded to, with transparency preserved. Nothing is uploaded, and you can confirm that in the Network tab.

Why convert AVIF to PNG?

Two reasons dominate. Transparency: if your AVIF has transparent regions — a logo, an icon, a cut-out product shot — PNG is the format that keeps them; JPG would flatten them onto white.Losslessness: PNG never discards detail, so it's the safe choice when the image will be edited further or composited, and you don't want to stack more compression on top. PNG is also supported everywhere, which matters when the software downstream doesn't yet understand AVIF. The cost of all this is file size — read on.

The honest fidelity caveats

PNG's losslessness is real but often misunderstood. The PNG is a pixel-perfect copy of what the AVIF decoded to — not of the original scene. AVIF is a lossy format, so whatever detail its compression already discarded is gone before PNG ever gets involved; PNG cannot bring it back. So converting AVIF → PNG does not "upgrade" the image; it freezes the current pixels with no further loss.

Two more specifics. File size: because PNG doesn't throw anything away, a PNG of a photograph is frequently several times larger than the source AVIF — expect big files for detailed photos.Bit depth: the browser canvas is 8-bit sRGB, so 10/12-bit HDR or wide-gamut AVIFs are reduced to 8-bit sRGB in the PNG. What's kept exactly: the pixel dimensions and the alpha channel.

Why "no upload" is verifiable, not a slogan

The AVIF is read with the browser's file APIs and decoded by the same native AV1 support browsers use to display AVIF on the web; the PNG is encoded from a <canvas> right in the page. No request carries your image. Prove it yourself: open DevTools, select the Network tab, drop a file, and watch nothing leave — the same principle behind ourzero-upload proof page. The free photo ceiling is 50 MB; over that the tool says so and points topricing, still without uploading anything.

If the file is damaged, repair it first

This converter can only work on an image the browser can decode. If your AVIF was truncated mid-download, carries a garbage prefix from a recovery tool, or has a broken box structure, the AV1 decoder will refuse it — and no honest converter can produce a PNG from pixels that never decoded. The tool runs a local structural scan and, when it finds damage, links you to repair AVIF to rebuild the container. Repair first, then convert the repaired copy here.

FAQ

How do I convert AVIF to PNG?

Drop an AVIF above. Modern browsers decode AV1 — the codec inside AVIF — natively, so the image is decoded on your machine, drawn to a canvas, and re-encoded as a lossless PNG. A Download button appears with the finished .png, transparency intact. Nothing is uploaded: the file is read with the browser's own file APIs and never sent to a server.

Is PNG lossless — does it restore the AVIF's original quality?

PNG encoding itself is lossless, so the PNG is a perfect, pixel-exact copy of what the AVIF decoded to. What it cannot do is recover detail the AVIF's own lossy compression already threw away — that information isn't in the file, and no format can invent it back. In other words: PNG faithfully preserves the decoded image, not the original camera capture. It's the right choice when you want no further quality loss from here on.

Does the PNG keep transparency?

Yes. PNG supports an alpha channel, so any transparency in the AVIF is preserved exactly — no white background is baked in. This is the main reason to pick PNG over JPG: logos, cut-outs, icons and UI assets keep their transparent edges.

Should I use PNG or JPG?

Use PNG when you need transparency, or a lossless copy for further editing, or you're converting graphics, screenshots and flat-color art. Use JPG when you're converting a photograph and want a small, universally compatible file. The trade-off is size: a PNG of a photo is often several times larger than the equivalent JPG, because PNG doesn't discard detail to save space.

What happens to HDR or 10-bit AVIF images?

The browser's 2D canvas works in 8-bit sRGB, so a 10-bit or 12-bit HDR / wide-gamut AVIF is tone-mapped and clamped to 8-bit sRGB during conversion. The PNG we produce is 8-bit-per-channel. For standard images this is invisible; a true HDR master destined for a color-managed pipeline is the one case where this matters.

My AVIF won't convert — is it broken?

Maybe. The tool reads the file locally and, if the browser's AV1 decoder refuses it, runs a structural scan. Genuine container damage is flagged and linked to the AVIF repair page; a structurally intact file that still won't decode usually just needs a newer browser. We never produce a PNG from an image the browser couldn't actually decode.

Related: smaller photo files — AVIF to JPG · just look at it — AVIF viewer · broken file — repair AVIF