Alpha logo export
- Input
- A 96×64 transparent PNG with overlapping semi-transparent shapes, two tEXt chunks, and an sRGB profile.
- Output
- A 1,689 byte AVIF at quality 90. A later AVIF → PNG conversion came back as RGBA with transparent corners.
PNG → AVIF kept alpha well enough to round-trip back to RGBA PNG, while our 1,084 byte sample became a 1,689 byte AVIF.
From real runs
| Element | Result | What happens |
|---|---|---|
| Transparency | Kept | The AVIF made from our transparent PNG round-tripped through AVIF → PNG with transparent corner pixels intact. |
| PNG text chunks | Lost | The Comment and Source strings from the PNG were not recoverable after converting through AVIF. |
| ICC profile | Changed | The AVIF path carried color information differently; the round-tripped PNG exposed ICC but not the original text chunks. |
| 16-bit grayscale | Changed | A 16-bit grayscale PNG converted successfully to AVIF, but this route is not a preservation path for sample depth. |
| Small graphics size | Changed | The 96×64 transparent PNG increased from 1,084 bytes to 1,689 bytes at quality 90. |
| Browser compatibility | Changed | The pair used the server our image engine API because AVIF output is not part of the browser image writer set. |
The AVIF made from our transparent PNG round-tripped through AVIF → PNG with transparent corner pixels intact.
The Comment and Source strings from the PNG were not recoverable after converting through AVIF.
The AVIF path carried color information differently; the round-tripped PNG exposed ICC but not the original text chunks.
A 16-bit grayscale PNG converted successfully to AVIF, but this route is not a preservation path for sample depth.
The 96×64 transparent PNG increased from 1,084 bytes to 1,689 bytes at quality 90.
The pair used the server our image engine API because AVIF output is not part of the browser image writer set.
We converted our PNG sample (20 KB) with Image engine on 2026-10-20. It took 173 ms and produced a 15 KB AVIF file, 24% smaller than the input. The engine raised 1 warning, listed below.
Input · sample.png · 20 KB
1200 × 800 px, 8-bit, colour type 6
Output · sample.avif · 15 KB
1200 × 800 px, avif
PNG → AVIF is an image delivery conversion. If the PNG is a scanned page, use OCR or Deep Read before replacing it with a harder-to-inspect image format.
ImageMagick 7 with AVIF support
magick in.png -quality 90 out.avifAVIF support depends on the installed codec stack, and metadata handling varies between builds.
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=png&to=avif.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.png" -F "from=png" -F "to=avif" \
-F 'options={"dpi":96}' \
--output output.avif| Key | Applies to | Type | Default |
|---|---|---|---|
| dpi | Reading PNG | number | 96 |
Yes in the tested alpha case. The AVIF converted back to PNG as RGBA with transparent corners.
Tiny flat artwork can be too small to benefit from AVIF compression. Our 1,084 byte PNG became a 1,689 byte AVIF.
It is fine for a delivery derivative, not for preservation. Keep the original high-bit-depth PNG if channel precision matters.