Crop

Circle crop image Crop image

Optimize

Compress image Remove background Upscale image

Modify

Resize image

Convert

Other

Convert JPG to PDF

Stuck With an AVIF? Make It a PNG

Rescue a file no editor will open, turned on this page into a PNG that holds every transparent pixel.

or drop the image here

Quick answer

Change an AVIF into a PNG with transparency carried over and lossless quality. Drop one file and the browser decodes the AVIF using the support it already ships, then writes the pixels back as a lossless PNG on your own device, with nothing sent out. Hand it several at once and Araluma passes them to our server to do the work in a single run, and the download is cleared within about 2 hours. This direction has nothing to warm up, since decoding AVIF and encoding PNG are both native to every current browser, so a lone file is done in a fraction of a second. Transparency rides along the whole way. AVIF and PNG each carry a full alpha channel, so cut-outs, logos, and stacked layers reach the PNG with the exact transparent regions they started with. The PNG comes out heavier on purpose, because it stores every pixel in full while AVIF leans on hard lossy compression, so reckon on three to ten times the original weight. The pair earns its keep when an AVIF will not open in an editor, a mail client, or a platform that has yet to learn the format.

Turning an AVIF into a PNG

Turning an AVIF into a PNG

Drop an AVIF into the upload area or tap to browse for one. The browser decodes the AVIF with its own support and writes it back as a lossless PNG. Both halves are native, so there is no module to fetch and no pause to warm up. Most photos clear in under a second. When it finishes, the readout sets the original AVIF size next to the fresh PNG size, and that PNG will plainly be the bigger of the two. Hit Download to keep it under the original base name with a .png extension. From that moment the file behaves like any ordinary PNG and opens in whatever app you point at it.

Transparency comes through

Transparency comes through

AVIF and PNG both carry a full alpha channel, so the conversion walks every transparent pixel across untouched. Nothing is flattened and no fill slides in behind the image. If the AVIF shows a subject floating on a clear canvas, the PNG you save shows that same subject on the same clear canvas, ready to drop into a layout, a deck, or a page over any backdrop. Compare that with a JPG, which owns no alpha and paints a solid color where the gaps were. AVIF to PNG leaves the mask whole, which is the very reason to take this route instead of AVIF to JPG whenever the asset depends on transparency.

Why the PNG weighs more

Why the PNG weighs more

AVIF gets tiny by throwing away detail the eye misses and keeping a dense little summary of the picture. PNG does the reverse, holding every pixel just as it was decoded with no further squeeze. Convert one to the other and the converter unpacks that dense AVIF back into full pixels and stores them without loss, which simply takes more room. Three to ten times the AVIF size is the usual spread, set by the content. None of that signals a problem. You are swapping bytes for two things worth having, a file every tool can open and a lossless master you can edit again without stacking on a second helping of compression damage.

AVIF or PNG, which fits

AVIF or PNG, which fits

Stay on AVIF for pictures served from a modern site where you know the visitor's browser and each kilobyte earns its place. Switch to PNG the moment the file has to open somewhere that still cannot read AVIF: older viewers, mail clients, document editors such as Microsoft Word, forum scripts, content systems with no AVIF upload path, and Photoshop builds older than 2025. PNG also suits anything you mean to keep editing, handing you a lossless copy you can save over and over without piling up loss. Think of AVIF as the format for delivery and PNG as the one for editing and reach. The destination tells you which to grab.

Where your file is handled

Where your file is handled

It comes down to how many files you hand over. With a single AVIF the whole job runs in the browser's image engine, with nothing sent out. Want proof? Open DevTools, sit on the Network tab, and convert something: not one outbound image request shows up the whole time. Hand over two or more at once and Araluma passes them to our server, which decodes and re-encodes them in a single run and returns one download. Files worked on the server are handled and then cleared within about 2 hours, we keep no copy of your images, we never ask you to sign in, and we put them to no use beyond the conversion you started. Either way the result is the same lossless PNG, with the same alpha channel held intact.

What still refuses AVIF

What still refuses AVIF

Plenty of software only made room for AVIF very recently. Through 2026 the usual refusers are most mail clients, with Gmail and Outlook among them, Microsoft Word and the rest of the Office suite, Photoshop releases before 2025, several content systems including some WordPress and Squarespace upload widgets, a handful of forum scripts, and every build of Internet Explorer. The current browsers, meaning Chrome from 85, Firefox from 93, Safari from 16.4, and Edge from 121, all open it without help. Whenever the tool in front of you belongs to that refusing group, sending the file to PNG is the shortest path to getting it accepted.

How it works

  1. Add your AVIF

    Drag the AVIF into the upload area, or tap it to open a picker and grab one from your computer, phone, or tablet.

  2. Let it finish

    The browser decodes the AVIF on its own and builds a PNG. Nothing has to load first, so the run is quick at most sizes.

  3. Glance at the sizes

    The readout puts the AVIF size next to the new PNG size. Count on the PNG running three to ten times bigger than the source.

  4. Keep the PNG

    Tap Download to save the file under its original base name with a .png extension, set to open in any app.

Keep converting

Squeeze a transparent original the opposite way, or settle on WebP for reach without leaping all the way to PNG.

PNG to AVIF AVIF to WebP

Frequently asked questions

What's the point of AVIF to PNG?

A lot of tools still will not take an AVIF. Mail clients, older Photoshop and other design apps, Microsoft Word, many upload boxes, and forum platforms all turn it down. A PNG, though, opens in every viewer and app there is. Converting is the fastest route to a file those tools will accept, and PNG doubles as a lossless master if you plan to keep editing the picture afterward.

Is transparency held onto?

It is held onto. A full alpha channel lives in both AVIF and PNG, so clear regions in the AVIF arrive clear in the PNG. There is no flattening and no fill dropped behind the subject. That is exactly where JPG falls short, lacking alpha and turning every clear pixel solid. Out of the PNG the mask is set to sit over any backdrop you place beneath it.

Does the PNG end up bigger?

Yes, every time, and by plenty. AVIF squeezes hard with lossy compression. PNG keeps each pixel with no lossy step at all. So converting one to the other grows the file on purpose, commonly three to ten times the AVIF's size. That is the format doing its job, not breaking. The bargain is universal reach plus a lossless editing copy, paid for in extra bytes.

Does converting cost any quality?

The conversion itself costs none. PNG is lossless and writes each pixel exactly as the browser decoded it from the AVIF. Any loss you might worry about already happened back when the lossy AVIF was first made. Saving to PNG holds onto whatever the AVIF carries but cannot bring back detail the original encode threw out. The PNG is a true copy of the decoded source, no sharper and no softer.

Why won't my AVIF open?

The format is recent enough that older software often skips it, including Photoshop before 2025, the bulk of mail clients, Microsoft Word, some forum scripts, and various content upload systems. A PNG sidesteps all of that, being the longest-standing and most broadly accepted raster format there is. Chrome, Firefox, and Safari read AVIF on their own, but step outside the modern browsers and the format is still earning its place.

Is converting here safe?

It comes down to how many files you hand over. A single AVIF is converted entirely in your browser through its own image engine, with nothing sent out, which you can check in DevTools: while the conversion runs, the Network tab shows no outbound image requests at all. Handing over two or more at once passes them to our server to work in a single run, and those files are cleared within about 2 hours. We keep no copy of your images and we never ask you to sign in. Either way you get the same lossless PNG.

The details

Notes from the team on craft, formats, and the small decisions behind a good round crop.

Why decoding AVIF is native and quick
Encoding AVIF is hard work, but decoding it is wired into every modern browser. Chrome, Firefox, Safari, and Edge all carry a native AVIF decoder inside their image pipeline, the same one that paints AVIF pictures sitting in a web page. That means converting to PNG pays no warm-up and pulls in no extra code. The browser reads the AVIF, unpacks it into a pixel buffer in memory, and passes those pixels to the native PNG writer. The whole thing wraps in well under a second for most real images, large photos included. Only the PNG-writing side shifts a little between browsers, and even the slowest seen, near 122 milliseconds for a megapixel on WebKit, feels instant in use.
The backwards-feeling growth in size
A conversion that inflates a file feels wrong, yet AVIF to PNG is precisely that. AVIF turns small by shedding visual detail nobody notices at a normal distance, so its artifacts are real but hidden in ordinary viewing. PNG plays it the other way, recording every pixel just as decoded with no extra loss, using only the lossless DEFLATE scheme. What you get back faithfully mirrors the decoded AVIF pixels with nothing added. Since the AVIF already let some detail go, the PNG cannot beat a PNG made from the untouched original, but it stays honest to what the AVIF kept. A spread of three to ten times the AVIF size is routine and expected, never a fault to chase.
Editing pipelines that lean on this pair
Designers and developers keep landing AVIF files out of automated pipelines, delivery networks, and modern content exports, then have to open them in tools that never learned AVIF. Converting to PNG gives a lossless copy holding the same pixels the AVIF held. From there the editing happens in Photoshop, Figma, Sketch, or whatever else, with no fresh compression creeping in. Once the edit is done and bound for the web, it can go back out as AVIF or WebP. The whole shape treats AVIF as the delivery format and PNG as the working stage in between, which is the arrangement today's software gets along with best. The PNG step charges nothing extra past the loss the source AVIF already wore.
Tracing the alpha across the conversion
AVIF keeps its transparency on a separate encoded plane beside the color. Decode an AVIF and the browser hands back a color pixel buffer and an alpha mask buffer both. The pipeline brings them together at full transparency and then writes the pair out as a PNG. PNG stores that mask losslessly, an 8-bit channel riding on every pixel. The PNG that results holds the same color and transparency the browser pulled from the AVIF, set for compositing. Soft gradients live. Feathered rims live. Half-transparent pixels live. The lone loss is whatever the AVIF's own lossy pass put on the alpha plane when it was first built, which tends to be a faint fringe you only catch at a hard zoom.
When the web really does want PNG
Even in 2026 a few web spots insist on PNG. Newsletter images have to be PNG or JPG, since most mail clients read images on the server side and refuse AVIF. Social platforms split: some take AVIF on upload and re-encode it, others just decline. Print routes built on software PDF pipelines often want PNG for transparent layers, because AVIF is no part of the PDF imaging model. Link-preview images do better as PNG or JPG, as the scrapers behind them run where AVIF decoding may be missing. For each of those, dropping to PNG is not a retreat but the right answer given what waits at the far end. The reach is worth the heavier file.
How the handling differs from a typical online tool
Most online AVIF to PNG services run on a remote server: you upload, the server decodes the AVIF and encodes a PNG, and the result comes back down, held there until that provider's wipe schedule fires, usually left vague. Araluma splits the work by how much you hand over. A single AVIF is decoded and re-encoded entirely in your browser, so nothing is sent out in that case. When you convert two or more at once, the batch goes to our server, which does the decode and encode in a single run and returns one download. Those files are handled and then cleared within about 2 hours, without asking you to sign in and with no use beyond the conversion you started. Nothing is stored for the long term and nothing is shared. For anyone carrying client assets, unreleased product shots, or sensitive material, the honest shape of the trade is this: one file stays with you, a batch passes through our server only to build your PNGs, and nothing lingers.