How to Convert AVIF to JPG or PNG: The 2026 Compatibility Guide

Quick answer: convert AVIF to JPG for compatibility, PNG for transparency

If you downloaded an .avif file and it will not open, the fix is usually simple:

• Use JPG for photos, email attachments, profile pictures, print orders, marketplace listings, CMS uploads, government forms, and any place that mainly wants a normal picture file.
• Use PNG for logos, screenshots, icons, stickers, product cut-outs, UI mockups, and anything with a transparent background.
• Keep AVIF when the image is staying on a modern website and the site already serves a JPG, PNG, or WebP fallback for older workflows.

That last point matters. AVIF is not a broken format. It is a very efficient image format built for the web, with support for lossy and lossless compression, transparency, animation, wide color, and HDR. The problem usually starts after the file leaves the browser. A web page can display an AVIF cleanly, but the same file may be rejected by a print kiosk, an older design app, a job-application form, or a CMS field that was built before AVIF became common.

So the practical question is not "Is AVIF good?" It is "Where does this exact file need to go next?"

Why AVIF files show up more often now

AVIF stands for AV1 Image File Format. It stores still images using AV1 compression inside an image container. In normal language: it can make web images much smaller without looking obviously worse.

That is why image CDNs, website builders, and performance-focused sites increasingly serve AVIF to browsers that support it. Smaller images can reduce page weight, improve perceived speed, and help important page elements load sooner. MDN and web.dev both recommend using modern formats such as AVIF or WebP with fallback images when compatibility matters.

This is great when you are browsing. It is less great when you right-click a product photo, download a reference image from a website, receive an AVIF in a chat, or export an asset from a modern pipeline and then need to use it somewhere mundane.

Common "why will this not open?" situations include:

• A school, visa, job, or government upload form only lists JPG, JPEG, PNG, or PDF.
• A print service accepts a JPG photo but rejects the AVIF original.
• A teammate cannot preview the file on a managed work laptop.
• An older image editor imports PNG and JPG but does not understand AVIF.
• An email client sends the AVIF as an attachment instead of showing a preview.
• A marketplace image uploader checks the extension before it checks the actual file.

HEIC files from iPhones run into a similar workflow problem: the format may be technically strong, while the receiving system is still picky.

AVIF to JPG or AVIF to PNG: choose by destination

Do not choose JPG or PNG by habit. Choose the format based on what the next app or person needs.

The short version:

• JPG is the compatibility photo format.
• PNG is the compatibility graphics format.
• AVIF is usually the delivery format for modern websites.

AVIF vs WebP has more detail on web delivery trade-offs, but for conversion work the table above is enough most of the time.

How to convert AVIF to JPG in PhotoTools

PhotoTools converts AVIF files locally in your browser. That means the image is decoded and re-encoded on your device instead of being uploaded to a server. For private photos, screenshots, documents, client work, and internal design assets, that is the main reason to use a browser-local converter instead of a random upload tool.

To make a JPG copy:

1. Open the AVIF to JPG converter.
2. Drop one or more .avif files into the page.
3. Leave the output format set to JPG.
4. Keep the quality around 90% for a good default.
5. Click Convert.
6. Download each file, or download the batch as a ZIP.

For most photos, 90% is the quiet middle ground: high enough that the result still looks like the original, low enough that the file does not balloon for no reason.

Use a lower setting, such as 80-85%, when the destination has a strict file-size limit and you are sharing a casual photo. Use a higher setting, such as 95%, when the file is going to a client, a print workflow, or another person who may crop or inspect it. Do not use 100% as a magic quality setting. It can create a much larger file without making a downloaded AVIF meaningfully more "original."

How to convert AVIF to PNG when transparency matters

Choose PNG when the file has see-through pixels or sharp graphic detail. That includes:

• Logos on transparent backgrounds.
• Product cut-outs.
• Stickers and overlays.
• Screenshots with small text.
• UI mockups.
• Icons, badges, and diagrams.
• Images that will be layered over another design.

To make a PNG copy, open the AVIF to PNG converter, drop in the AVIF file, convert, and download the PNG.

PNG does not use the same quality slider logic as JPG. It is a lossless export format for the decoded pixels, so it is good for preserving edges and transparency. The trade-off is size. A tiny AVIF photo can become a very large PNG because PNG is not designed to compress photographic detail the way AVIF or JPG does.

If a PNG export looks huge, ask one question before compressing it: does this image actually need transparency? If not, a JPG copy is usually the better compatibility file. If yes, keep the PNG and reduce dimensions only if the receiving app has a size limit.

This guide explains why PNG files can be much larger than JPG.

What happens to transparent backgrounds

This is the place where many AVIF conversions go wrong.

AVIF can store transparency. PNG can store transparency. JPG cannot.

When you convert a transparent AVIF to JPG, the transparent pixels have to become ordinary pixels. Depending on the exporter and viewer, the result may appear on a white, black, or otherwise solid background. Even when the preview looks acceptable on a white page, the file will not remain transparent when someone places it on a colored design.

Use this quick check:

• If the image is a photo with no transparent cut-out, JPG is fine.
• If the image must sit on top of another background, use PNG.
• If the edge of a cut-out looks pale, jagged, or boxed in after conversion, export PNG and preview it on both a light and dark background.

This is especially important for product images, watermarks, creator stickers, and logo files. A logo that looks fine in a white email can look broken when placed on a dark slide.

What happens to color, HDR, and wide gamut

AVIF can carry more advanced image data than a basic JPG workflow, including high dynamic range and wide color gamut in capable pipelines. The official AVIF documentation also describes support for transparency, animation, and layered image use cases.

When you convert through a browser canvas, the browser decodes the source image, draws the visible pixels, and exports a new file. That is useful for compatibility, but it is not the same as preserving every part of the original AVIF container. HDR or wide-gamut material may be tone-mapped or normalized for ordinary viewing, depending on the browser, display, and export path.

For everyday web downloads and regular photos, this is usually not a practical problem. In many cases the converted JPG or PNG is the right practical output because the destination app expects a normal SDR image.

Be more careful when:

• The AVIF came from a professional HDR workflow.
• You are preparing cinema, 3D, product-color, or display-calibration material.
• You need the file as a long-term master.
• The receiving person will compare exact color values rather than just view the image.

In those cases, keep the original AVIF and export a JPG or PNG only as a compatibility copy.

Why the converted file can be larger

People expect conversion to make files smaller. With AVIF, the opposite often happens.

AVIF is already highly compressed. A 300 KB AVIF photo might turn into a 700 KB JPG at high quality, or a multi-megabyte PNG. That does not mean the converter failed. It means you changed from a modern compression format into a compatibility format.

Use these expectations:

• AVIF to JPG: often larger than the AVIF, but still reasonable for photos.
• AVIF to PNG: often much larger for photos, but correct for transparent graphics.
• AVIF kept as AVIF: usually best for modern web delivery.

If the final JPG is too large for an upload form, lower the JPG quality first. If it is still too large, resize the dimensions after converting. File-size limits are usually about both compression and pixel count.

The 2026 website image format guide covers when AVIF should stay in the web pipeline instead of being converted away.

Batch-converting AVIF files without making a mess

Batch conversion is useful, but it is easy to make a bad batch decision if your folder mixes photos and graphics.

Before converting 50 files, skim the thumbnails and split them into two groups:

• Photos, portraits, product shots, and background images -> convert to JPG.
• Logos, screenshots, icons, stickers, overlays, and transparent cut-outs -> convert to PNG.

Then run a small test:

1. Convert one photo to JPG at 90%.
2. Convert one transparent or graphic file to PNG.
3. Open both outputs.
4. Check file size, transparency, and edge quality.
5. Convert the rest only after the sample looks right.

PhotoTools supports dropping multiple AVIF files at once and downloading the results as a ZIP, so the slow part is not the conversion. The slow part is choosing the right target format before you create a folder full of files you have to redo.

Privacy and metadata

The converter runs in the browser. Your AVIF file is decoded locally, drawn to an offscreen canvas, and exported as a new JPG or PNG blob using the browser's image export API. The practical privacy benefit is simple: the original file does not need to be uploaded to a server for conversion.

This re-encoding path also means the output is a fresh image file made from pixels. Metadata embedded in the original container, such as camera details or other non-pixel information, is typically not carried over the same way it would be in a metadata-preserving desktop editor.

That is useful when you want a clean compatibility copy. It is not a replacement for an archival workflow. If the original metadata matters, keep the AVIF.

PhotoTools also has a separate metadata guide if you need to inspect what a photo contains before sharing it.

Troubleshooting AVIF conversion problems

The AVIF will not load in the converter.

Try a current version of Chrome, Edge, Safari, or Firefox. If the file still fails, it may be corrupt, incomplete, mislabeled, or encoded in a way your browser cannot decode.

The JPG has a white or solid background.

That is expected when the original had transparency. Export PNG instead.

The converted JPG is too big.

Lower the JPG quality to around 85%, then check the image at the size people will actually see it. If it is still too large, resize the image dimensions.

The PNG is enormous.

PNG is probably the wrong output for a full photo. Use JPG if there is no transparency. Use PNG only when transparency or sharp graphic edges matter.

The color looks different.

Keep the AVIF as the source, try a different browser, and test the file in the destination app. If the image came from an HDR or wide-gamut workflow, a compatibility JPG or PNG may not preserve the same appearance.

The upload form still rejects the converted file.

Check the extension, file size, pixel dimensions, and color mode requirements. Some forms reject valid image files because they exceed a size limit or use dimensions outside the allowed range.

Should you keep AVIF after converting?

Usually, yes.

Think of JPG and PNG as delivery copies. They solve a compatibility problem for a specific destination. They do not make the original AVIF better, and a JPG export is not a master file.

Keep AVIF when:

• The file came from your own export pipeline.
• You may need to make another version later.
• The image is part of a modern website.
• You care about the smallest web delivery size.
• The source may contain transparency, HDR, wide color, or metadata you do not want to lose.

Delete the AVIF only when it was just a downloaded convenience file and the converted copy is all you need.

Technical sources checked

This guide was reviewed against primary and developer-facing references:

• The Alliance for Open Media AVIF overview for AVIF capabilities such as transparency, HDR, wide color, animation, and browser support.
• The AV1 Image File Format v1.2.0 specification for the formal container and feature model.
• The MDN image file type and format guide for browser-oriented format behavior and fallback guidance.
• The web.dev image performance guide for using modern formats such as AVIF with compatible fallbacks.
• The MDN OffscreenCanvas convertToBlob() documentation for browser-side image export behavior.

In plain English: keep AVIF when you are optimizing a website, convert to JPG when a normal photo has to work in a conservative workflow, and convert to PNG when transparency or crisp graphic detail matters.