How browser-based AVIF to PNG decoding works
This converter decodes AV1 image frames directly inside your browser tab and re-encodes them as lossless 32-bit PNG files without uploading a single byte. According to the AOMedia AV1 Image File Format (AVIF) Specification, AVIF packages AV1-compressed still images (avif) and sequences (avis) inside an ISOBMFF container.
If you only need a smaller photographic file without transparency, you can export non-transparent AVIF photos as compact JPG files instead of generating heavy lossless PNGs.
Decoding AV1 frames and EXIF orientation locally
When you drop files into Drop AVIF images here, the browser calls createImageBitmap() with imageOrientation: "from-image" so portrait photos rotate upright automatically. Each decoded frame is drawn at its native width and height onto an offscreen 2D canvas with no background fill.
Because Output format: PNG is locked on this page, the encoder writes pure RGBA pixels with zero lossy compression artifacts. Clicking More formats switches to the multi-format converter if you ever need WebP or JPG mid-session.
Each pixel stores 32 bits across four 8-bit channels, preserving subtle alpha gradients from 0% transparent to 100% opaque without stair-stepped fringes around curved icons.
Canvas dimension limits and animated AVIF sequences
Every browser enforces a 2D canvas memory ceiling to prevent tab crashes on mobile devices. This tool clamps oversized inputs to a maximum side of 4096 px and 16,777,216 total pixels, scaling large camera originals proportionally while keeping aspect ratios exact.
Animated AVIF sequences carrying the avis container brand are decoded to their first static frame on the 2D canvas. Static UI assets, icons, and product cutouts convert pixel-for-pixel without losing edge sharpness.
When should I convert AVIF to PNG instead of JPG?
Pick PNG whenever your AVIF image contains transparent backgrounds, crisp text overlays, UI screenshots, or flat-color logos that blur under lossy compression. Choose JPG only for continuous-tone photographs where small download size matters more than alpha transparency or razor-sharp edges.
| Asset type | Best target format | Alpha transparency | Typical file size impact | Edge sharpness |
|---|---|---|---|---|
| Transparent logo or icon | PNG | Preserved (32-bit RGBA) | Larger than AVIF | Exact pixel edges |
| Software or UI screenshot | PNG | Preserved if present | Larger than AVIF | Crisp text and lines |
| Camera or product photo | JPG | Replaced with solid matte | Compact | Slight lossy smoothing |
| Modern web hero graphic | WebP | Preserved | Compact | High with lossy/lossless |
| Print or legacy editor import | PNG | Preserved (32-bit RGBA) | Larger than AVIF | Zero generation loss |
Under the W3C Portable Network Graphics (PNG) Specification Third Edition, PNG stores lossless Deflate-compressed 32-bit RGBA data. If your exported PNG turns out wider than your CMS or newsletter layout allows, pass it through a browser-based pixel resizer to trim dimensions cleanly.
Preserving alpha transparency and crisp pixel edges
Transparency and sharp vector-like edges are the main reasons designers convert modern AVIF assets back to PNG. While JPG flattens see-through regions onto a solid background color, PNG writes an independent 8-bit alpha channel alongside 8-bit red, green, and blue values.
Why lossless PNG files grow larger than AVIF
AV1 intra-frame coding achieves dramatic compression by predicting pixel blocks and discarding imperceptible high-frequency detail. When HTMLCanvasElement.toBlob() encodes image/png, the MDN HTMLCanvasElement.toBlob() Reference notes that PNG ignores any lossy quality parameter.
As a result, a 120 KB AVIF photograph often expands to several megabytes as a lossless PNG. That size jump is normal and confirms that no further lossy quantization was applied during conversion.
Opening converted PNG assets in legacy design editors
Many older desktop photo editors, word processors, print RIP stations, and content management systems still reject .avif uploads. Converting those assets to .png gives you universal compatibility across every operating system without sacrificing transparent cutouts.
Before converting a large batch of camera originals, you can verify color profiles and camera tags before decoding to inspect dimensions and embedded metadata on the source files.
Batch exports, color orientation, and metadata privacy
Every conversion runs in memory inside your browser tab, making it safe for unreleased product mockups, confidential UI screenshots, and personal photos. Multi-file batches are packaged into a single downloadable ZIP archive once encoding finishes.
Automatic EXIF orientation and metadata removal
As documented in the MDN createImageBitmap() Web API Reference, decoding with imageOrientation: "from-image" bakes rotation tags directly into the pixel grid. Re-encoding that canvas to PNG strips all original EXIF camera tags and GPS coordinates from the output file.
If you need to share original JPG or PNG files without re-encoding their pixels, you can strip camera location tags from original photos directly.
Tip: If you are converting dozens of high-resolution AVIF photos strictly for email or web galleries where transparency is unnecessary, switch to JPG or compress the resulting PNGs afterward to avoid multi-megabyte attachments.
Downloading single PNG files or multi-file ZIP archives
Dropping one AVIF image gives you a direct .png download button alongside the Compress and Put in a PDF next-step shortcuts. Dropping two or more files enables Convert N images to PNG and bundles every converted PNG with unique filenames into one ZIP archive.
You can also mix WebP, JPG, and HEIC images into the same batch without running separate conversions. Every output receives a clean .png extension with duplicate filenames automatically numbered so nothing overwrites inside the ZIP.