AVIF logo returned to an editor
- Input
- A 96×64 AVIF with transparent corners, created from PNG artwork and saved at quality 90.
- Output
- A 3,575 byte RGBA PNG. The empty corner was transparent, and the output had an ICC profile key.
AVIF → PNG kept the transparent corners of our alpha AVIF and expanded the 1,689 byte source to a 3,575 byte PNG.
From real runs
| Element | Result | What happens |
|---|---|---|
| Alpha channel | Kept | The transparent AVIF corner decoded to RGBA PNG with a zero alpha value in the sampled pixel. |
| Visible AVIF artifacts | Kept | PNG stores the decoded AVIF result losslessly, including compression artifacts already present in the source. |
| ICC profile | Kept | The AVIF-to-PNG output exposed an icc_profile key when opened with our image engine. |
| Text metadata | Lost | Text chunks from the original PNG used to create the AVIF were still absent after AVIF → PNG. |
| File size | Changed | The 96×64 transparent AVIF grew from 1,689 bytes to 3,575 bytes as a lossless PNG. |
| Bit depth | Changed | The output opened as 8-bit RGBA PNG, so this is not a high-bit-depth preservation route. |
The transparent AVIF corner decoded to RGBA PNG with a zero alpha value in the sampled pixel.
PNG stores the decoded AVIF result losslessly, including compression artifacts already present in the source.
The AVIF-to-PNG output exposed an icc_profile key when opened with our image engine.
Text chunks from the original PNG used to create the AVIF were still absent after AVIF → PNG.
The 96×64 transparent AVIF grew from 1,689 bytes to 3,575 bytes as a lossless PNG.
The output opened as 8-bit RGBA PNG, so this is not a high-bit-depth preservation route.
We converted our AVIF sample (15 KB) with Image engine on 2026-10-20. It took 265 ms and produced a 67 KB PNG file, 4.4× larger than the input. The engine raised 1 warning, listed below.
Input · sample.avif · 15 KB
1200 × 800 px, avif
Output · sample.png · 67 KB
1200 × 800 px, 8-bit, colour type 6
AVIF → PNG can make a screenshot easier to inspect in older tools, but it still contains pixels. Use OCR routes before or after conversion when text extraction is the real task.
ImageMagick 7 with AVIF support
magick in.avif out.pngThe PNG preserves decoded pixels, not the source image before AVIF compression.
The HTTP API and the MCP server run the exact engine this page uses (Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=avif&to=png.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.avif" -F "from=avif" -F "to=png" \
-F 'options={"width":0}' \
--output output.png| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing PNG | number | 0 |
| height | Writing PNG | number | 0 |
| fit | Writing PNG | contain · cover · fill | contain |
| quality | Writing PNG | number | 90 |
| background | Writing PNG | string | #ffffff |
| stripMetadata | Writing PNG | boolean | true |
Yes in the measured alpha case. The output opened as RGBA and the corner pixel had zero alpha.
PNG stores decoded pixels losslessly. AVIF's compact compression is lost when the image is expanded for editing compatibility.
No. Metadata that disappeared during PNG → AVIF did not come back when we converted the AVIF to PNG.