What AVIF actually is

AVIF — the AV1 Image File Format — is an image format built on top of the AV1 video codec. The Alliance for Open Media finalized AV1 in 2018 and AVIF followed in early 2019, designed to do for images what AV1 was doing for video: deliver better compression than anything that came before, royalty-free.

And it does. At the same visual quality, an AVIF file is roughly 10–20% smaller than WebP and 40–60% smaller than JPEG. Take a 1080p photo that weighs 320 KB as a quality-90 JPEG: the same photo as a quality-60 AVIF is around 130 KB, with no visible difference. On a page with twenty images that's a few hundred KB saved per view — meaningful for Core Web Vitals and meaningful for your CDN bill.

That compression advantage is why AVIF is spreading. Netflix, Shopify, Cloudflare, Imgix, Cloudinary, and WordPress all ship AVIF variants today. If you're downloading images from the modern web, you're going to start seeing .avif files — and that's where the trouble starts.

The compatibility problem

AVIF lives comfortably inside a browser tab and uncomfortably almost everywhere else. As of late 2026, here's the honest map of what opens AVIF and what doesn't.

What does NOT support AVIF

  • Windows File Explorer (preview pane and thumbnails). Windows 10 and Windows 11 do not decode AVIF out of the box. The preview pane shows a generic icon, thumbnails stay blank, and double-clicking opens Photos — which also can't decode AVIF without help. You can install the AV1 Video Extension from the Microsoft Store, which adds the codec system-wide, but most users haven't.
  • macOS Finder Quick Look. This one catches people off guard. Safari 16+ renders AVIF fine on web pages, but Finder's Quick Look (the spacebar preview) and Finder thumbnails were still inconsistent through macOS 13 Ventura and only stabilized in macOS 14 Sonoma.
  • Photoshop pre-23.2 (released February 2022). Anything older — including the CS6 install on a lot of design machines — needs the AVIF codec plugin from Adobe. Same story for GIMP before 2.10.32, which added native AVIF in 2022.
  • CMS and DAM systems. WordPress core accepts AVIF uploads since 6.5, but plenty of legacy CMS platforms (Drupal 7 sites, older Joomla, custom-built admin tools, several popular e-commerce backends) reject AVIF at upload or store it without generating previews.
  • Email clients. Outlook for Windows (the desktop app, not the new web-based one) does not render AVIF inline. Older Apple Mail clients on macOS 12 and below don't either. Embedded AVIF in HTML email is invisible to roughly 30% of email clients in 2026.
  • Office software. Word, PowerPoint, and Excel on Windows don't render AVIF when embedded as a picture. LibreOffice handles it inconsistently depending on the system codecs installed.

What does support AVIF

  • All modern browsers — Chrome 85+, Firefox 86+, Edge 85+, Safari 16+, Opera 71+, plus every major mobile browser. If your image is going to be viewed in a browser, AVIF is safe.
  • Modern image viewers — IrfanView with plugins, ImageGlass 9+, macOS Preview on Sonoma+, Photos app on iOS 16+ and macOS 13+.
  • Modern design tools — Photoshop 23.2+, Affinity Photo 2, Figma (since 2023), GIMP 2.10.32+.
  • Most cloud photo services — Google Photos, iCloud Photos, Dropbox preview, Imgur all handle AVIF.

The pattern is clear: inside a browser, AVIF works. Outside a browser, AVIF is a coin flip. If you downloaded an AVIF and now need to do something with it — edit it, email it, embed it, hand it to a designer — conversion is the practical answer.

AVIF to JPG: maximum compatibility

JPG is the most universally supported image format on Earth. Every device, every operating system, every email client, every browser, every CMS, every Office app, every printer, every phone from 2005 onward opens JPG. If compatibility is the goal, JPG is the answer.

Convert AVIF to JPG when:

  • You're emailing the image and don't want to guess whether the recipient's client renders AVIF.
  • You're placing the image in a Word doc, PowerPoint, or PDF.
  • You're uploading to a CMS, DAM, or e-commerce backend that rejects AVIF.
  • You're sending a screenshot to a non-technical client.
  • You're printing the image through a service that doesn't accept AVIF.
  • You want a file that opens identically on a 2008 laptop and a 2026 phone.

JPG doesn't support transparency, so if your AVIF has an alpha channel, those areas become black (or white, depending on the encoder) when converted to JPG. For photos this doesn't matter. For logos, icons, or product cutouts, it does — use PNG instead.

AVIF to PNG: lossless and transparency

PNG is a lossless format. It supports full 8-bit alpha transparency and decodes everywhere JPG does, plus design tools that prefer PNG for layered work. If your AVIF has transparency or you need to do further editing without compounding loss, convert to PNG.

Convert AVIF to PNG when:

  • You need to preserve transparency (logos, icons, product images with cutout backgrounds).
  • You're going to edit the image in Photoshop, GIMP, or Affinity and want a clean intermediate.
  • You're doing pixel-precise design work where JPG artifacts would be visible.
  • You're saving screenshots or UI captures where sharp text matters.
  • You need to feed the image into a tool that prefers PNG (most design and print pipelines).

The catch is file size. PNG is lossless and uncompressed-ish, so a photo that was 95 KB as AVIF routinely becomes 2 MB or more as PNG. For a 12-megapixel phone photo, expect 10–25 MB. PNG was never designed for photos; it's for graphics, screenshots, and anything with sharp edges. If your AVIF is a photo and you're just trying to make it openable, JPG is almost always the better choice.

The quality math: double encoding

This is the part most guides skip, and it's the part that bites people.

Most AVIF files in the wild are lossy. They've already thrown away information the eye is bad at seeing — high-frequency detail in flat areas, subtle color gradients. The AV1 encoder is exceptionally good at this; that's why the files are so small.

When you convert AVIF → JPG, you're encoding an already-lossy image with a second lossy encoder. JPEG's DCT-based compression adds its own artifacts — blocky 8×8 cells, ringing around high-contrast edges, color subsampling. Stack JPEG artifacts on top of AVIF artifacts and the result is visibly worse than either alone.

The fix is to use a high JPG quality setting — q92 or higher. At q92, JPEG adds minimal additional artifacts and the visible quality is close to the AVIF source. At q75 (a common default for web), the double-encoding penalty becomes obvious: smooth skies develop banding, fine text picks up halos, and skin tones get a plastic look.

Here's a real-world example from a test batch. A 4K landscape photo:

| Source | Quality setting | Size | Visual quality | |---|---|---|---| | Original AVIF (q60) | — | 412 KB | Reference | | AVIF → JPG | q75 | 318 KB | Noticeable banding in sky | | AVIF → JPG | q88 | 540 KB | Clean, slight softening | | AVIF → JPG | q95 | 920 KB | Indistinguishable from AVIF | | AVIF → PNG | lossless | 14.2 MB | Identical to AVIF pixels |

The takeaway: if you care about quality, push JPG quality above 90. The file gets larger but stays clean. If file size is the priority and quality loss is acceptable, q80 is the floor — anything below compounds the AVIF artifacts badly.

AVIF to PNG: no quality loss, big size cost

PNG is lossless, so converting AVIF → PNG preserves every pixel exactly as the AVIF decoder produced it. There's no double-encoding penalty because there's no second lossy step.

But the file size balloon is dramatic:

  • A 95 KB AVIF photo routinely becomes a 2–4 MB PNG — a 20–40× increase.
  • A 400 KB AVIF hero image can become 12 MB or more as PNG.
  • An AVIF with transparency typically becomes a PNG 10–20× larger than the source.

The reason is structural. AVIF's AV1 compression throws away data and stores what remains efficiently. PNG stores every pixel's RGB value, compressed only with zlib. For photos, PNG is the wrong tool; for graphics and screenshots, it's the right one.

What you lose: 12-bit color and HDR

This is the subtle one. AVIF supports 10-bit and 12-bit color depth, while JPG and standard PNG are 8-bit. That's 1,024 or 4,096 values per channel versus 256.

For most web content this doesn't matter — most monitors are 8-bit and most photos don't have gradients smooth enough to show banding at 8-bit. But for HDR photos, sunset skies, smooth studio backgrounds, and high-end product photography, the difference is visible. AVIF also supports HDR transfer functions (PQ, HLG) and wide gamut color spaces (Display P3, Rec. 2020) that get clipped when you convert to 8-bit JPG or PNG.

When you convert AVIF → JPG or AVIF → PNG in a standard browser pipeline, the 10-bit or 12-bit source gets quantized down to 8-bit. Wide-gamut colors get mapped to sRGB. HDR metadata is discarded. The result looks fine on a standard monitor but loses the range the original AVIF was carrying.

For 95% of use cases, the 8-bit downgrade is invisible and not worth worrying about. For photography work where color depth matters, know that you're losing it on conversion.

Browser-based conversion vs installing a codec

When AVIF won't open, you have two routes.

Option 1: Install an AVIF codec

On Windows, the AV1 Video Extension from the Microsoft Store adds system-wide AVIF decoding. After installation, File Explorer, Photos, and any app using the Windows imaging APIs will open AVIF natively. On macOS, upgrading to Sonoma or later fixes Finder Quick Look.

The codec route makes sense if you work with AVIF files regularly and want them to "just open" everywhere on your machine. The downside: it only fixes your machine. The file you send to a client, a colleague, or an upload form still has the same compatibility problem on their end.

Option 2: Convert in the browser

Browser-based conversion decodes the AVIF using the browser's native AVIF support (every modern browser has it), draws the pixels to an in-memory canvas, and re-encodes as JPG or PNG. No codec installation, no software download, no upload to a server.

javascript
// The browser pipeline, simplified const img = await decodeAvif(file); // browser's native AVIF decoder const canvas = drawToCanvas(img); const blob = await canvas.toBlob('image/jpeg', 0.92); // q92 to limit double-encoding artifacts save(blob, 'converted.jpg');

The browser route makes sense when:

  • You need to send the converted file to someone else (it solves their compatibility problem, not just yours).
  • You're on a machine where you can't install codecs (work computer, shared machine, locked-down corporate laptop).
  • You have a one-off conversion and don't want to mess with system settings.
  • You need to batch-convert a folder of AVIF files.

This is what the SynoxTools converter does — drop an AVIF, pick JPG or PNG, set quality, download the result. Everything runs locally in your browser; nothing gets uploaded.

How to convert AVIF to JPG or PNG, step by step

  1. Open the image converter.
  2. Drag and drop your .avif file (or click to browse). You can drop multiple files at once.
  3. Pick the output format:
    • JPG for photos, email, documents, and max compatibility.
    • PNG for transparency, screenshots, design work, and lossless editing.
  4. If you chose JPG, set quality:
    • q95 if quality matters and size doesn't (best for editing intermediates).
    • q92 as the default — visually indistinguishable from the AVIF, reasonable size.
    • q80 as the floor — smaller files, slight artifacting acceptable.
  5. Click Convert.
  6. Download the result. For multiple files, download them all as a ZIP.

The whole thing takes a few seconds per image. No account, no upload, no waiting in a queue.

Batch conversion: when you have a folder of AVIFs

If you've downloaded a batch of images from a stock site, scraped a folder of assets, or received a zip of AVIFs from a designer, you don't want to convert them one at a time. The batch converter handles folders of AVIF files in a single pass:

  1. Drag in 10, 50, or 500 .avif files.
  2. Pick the output format (JPG or PNG) and quality.
  3. The browser processes each file locally and bundles the results into a single ZIP.

On a typical laptop, expect roughly 0.3–0.5 seconds per image for AVIF → JPG at q92, and 0.1–0.2 seconds per image for AVIF → PNG (PNG encoding is faster because there's no quantization step). A folder of 200 AVIF files converts to JPG in about 90 seconds, entirely in your browser.

A note on memory: AVIF decoding is CPU-intensive, and converting very large batches can hit memory limits. If you're processing thousands of images, work in chunks of a few hundred at a time.

Common pitfalls

A few things that trip people up:

  • JPG doesn't support transparency. If your AVIF has an alpha channel and you convert to JPG, transparent areas become solid black or white. Use PNG for anything with transparency.
  • AVIF can have animations. A multi-frame AVIF (rare but exists) converts to a static JPG or PNG — only the first frame survives. For animated images, use GIF or animated WebP instead.
  • Color profiles may shift. AVIF can carry ICC profiles and HDR metadata that don't survive JPG/PNG conversion cleanly. If color accuracy matters, check the result against the original on a calibrated monitor.
  • EXIF metadata is stripped in browser conversion. The canvas pipeline drops EXIF. If you need to preserve camera metadata, use a tool that explicitly handles EXIF — or accept the loss; for most conversions, EXIF doesn't matter.
  • Some AVIFs are HDR. Converting an HDR AVIF to standard JPG produces a flat, washed-out SDR image. Browser-based tools generally do a simple tonemap; the result is usable but not what the original HDR looked like.
  • Maximum AVIF dimensions are 8192×8192. Larger AVIFs are tiled. Browser converters handle them fine, but very large source files can be slow.

A practical decision framework

Ask yourself two questions.

1. Where is this image going?

  • Email, Office doc, legacy CMS, printer → JPG at q92.
  • Photoshop, design tool, anything needing transparency → PNG.
  • Web page (modern browsers only) → keep the AVIF.

2. Is quality or size more important?

  • Quality → PNG (lossless) or JPG at q95.
  • Size → JPG at q85, accept slight artifacting.
  • Both → JPG at q92, the practical sweet spot.

The rule of thumb: JPG for sharing and compatibility, PNG for editing and transparency, keep AVIF for web serving. Most users converting AVIF files want JPG at q92 — it's the answer 80% of the time.

A note on the format war

AVIF isn't going away. It's the format the web is moving toward, and the compatibility gaps will close over the next few years as Windows and macOS ship codecs by default and the long tail of legacy software catches up. JPEG XL is also emerging as a competitor, with better encoding speed than AVIF and similar compression — but its browser support is still rocky in 2026, and the format politics around it (Google's objections, Apple's quiet adoption) make its trajectory uncertain.

For now, AVIF is the best format for serving images on the web and the most annoying format for doing anything else with them. The conversion path is short, runs in your browser, and costs nothing. Keep your originals in AVIF when you can; convert to JPG or PNG when you must.