Transparent AVIF logo
- Input
- A 96×64 AVIF created from an alpha PNG, 1,689 bytes, with transparent corners around colored shapes.
- Output
- A 2,290 byte JPEG in RGB mode. The transparent regions were filled before compression.
AVIF → JPG flattened our transparent AVIF derivative into RGB JPEG pixels, growing 1,689 bytes to 2,290 bytes at quality 90.
From real runs
| Element | Result | What happens |
|---|---|---|
| Visible pixels | Kept | The decoded AVIF image content was written into a standard JPEG that our image engine opened as RGB. |
| Transparency | Lost | The alpha channel from the AVIF made from our PNG was flattened because JPEG has no transparent pixels. |
| Background fill | Changed | A green background option was accepted for flattening, though JPEG compression nudged sampled colors slightly. |
| Metadata | Lost | The output JPEG reported JFIF fields only, not the AVIF color and auxiliary metadata package. |
| File size | Changed | The transparent 1,689 byte AVIF became a 2,290 byte JPEG at the tested quality setting. |
| Compression generation | Changed | The route decodes AVIF and then applies JPEG compression, so it adds a new lossy generation. |
The decoded AVIF image content was written into a standard JPEG that our image engine opened as RGB.
The alpha channel from the AVIF made from our PNG was flattened because JPEG has no transparent pixels.
A green background option was accepted for flattening, though JPEG compression nudged sampled colors slightly.
The output JPEG reported JFIF fields only, not the AVIF color and auxiliary metadata package.
The transparent 1,689 byte AVIF became a 2,290 byte JPEG at the tested quality setting.
The route decodes AVIF and then applies JPEG compression, so it adds a new lossy generation.
We converted our AVIF sample (15 KB) with Image engine on 2026-10-20. It took 34 ms and produced a 40 KB JPEG file, 2.6× larger than the input. The engine raised 2 warnings, listed below.
Input · sample.avif · 15 KB
1200 × 800 px, avif
Output · sample.jpg · 40 KB
1200 × 800 px, baseline
AVIF → JPG does not recognize text in screenshots or scanned pages. Convert with OCR if the goal is searchable content rather than image compatibility.
ImageMagick 7 with AVIF support
magick in.avif -background white -alpha remove -quality 90 out.jpgCodec support and color handling depend on the ImageMagick build installed on your machine.
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=jpg.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.avif" -F "from=avif" -F "to=jpg" \
-F 'options={"width":0}' \
--output output.jpg| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing JPEG | number | 0 |
| height | Writing JPEG | number | 0 |
| fit | Writing JPEG | contain · cover · fill | contain |
| quality | Writing JPEG | number | 90 |
| background | Writing JPEG | string | #ffffff |
| stripMetadata | Writing JPEG | boolean | true |
No. The image has to be flattened because JPEG is opaque. Set the background color before converting artwork with soft edges.
AVIF is usually a denser modern codec. Our 1,689 byte AVIF became a 2,290 byte JPEG after flattening and JPEG encoding.
No. It makes the file easier for JPEG-only systems to read, but it cannot restore detail already discarded by AVIF compression.