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 is important. AVIF is not a broken format. It is a very efficient image format built for the web . It supports lossy and lossless compression , transparency , animation , wide color and HDR . The problem typically begins after the file has exited the browser. An AVIF might look good on a web page, but the same file might be refused by a print kiosk, an older design app, a job-application form or a CMS field that was created before AVIF became common.
So the real question is not "Is AVIF good?" It’s “Where does this exact file 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 for when you are surfing. It’s less great if you right-click a product photo, download a reference image off a website, get 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
JPG or PNG by default, don't. Pick a format for what the next app or person needs.
| What you are doing next | Best output | Why |
|---|---|---|
| Sending a normal photo by email | JPG | Small enough, familiar, easy to preview |
| Uploading a profile photo or ID-style image | JPG | Most forms expect JPEG/JPG for photos |
| Ordering prints | JPG | Photo labs and print portals usually handle JPG cleanly |
| Saving a logo with a transparent background | PNG | JPG would remove transparency |
| Exporting a sticker, cut-out, or overlay | PNG | Keeps the alpha channel |
| Sharing a screenshot with text and UI lines | PNG | Keeps sharp edges cleaner than JPG |
| Preparing website images | Usually keep AVIF, with fallback | Better compression for modern browsers |
| Archiving the original download | Keep AVIF too | Conversion creates a copy, not a better master |
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 . This means that the image is decoded and re-encoded on your device, instead of being uploaded to a server. This is why you’d want a browser-local converter instead of some random upload tool for private photos, screenshots, documents, client work, internal design assets, etc.
To make a JPG copy:
- Open the AVIF to JPG converter.
- Drop one or more
.aviffiles into the page. - Leave the output format set to JPG.
- Keep the quality around 90% for a good default.
- Click Convert.
- 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 support 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? Size. An AVIF photo that is tiny can become a very large PNG . PNG is not meant to compress photographic detail like AVIF or JPG .
If you have a huge PNG export, before trying to compress it, ask yourself one question: does this image really need transparency? Or a JPG copy is usually the better compatibility file. If yes, leave the PNG, only downscale 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.
Transparent AVIF to JPG, the transparent pixels have to be converted to regular pixels. Depending on the exporter and viewer, the result may be displayed on a white, black or otherwise solid background. It may look fine in a preview on a white page, but when put on a colored design the file will not be transparent.
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 on a dark slide.
What happens to color, HDR, and wide gamut
AVIF can contain more advanced image data than a basic JPG workflow, such as high dynamic range and wide color gamut in capable pipelines. The official AVIF documentation also mentions support for transparency, animation and layered image use cases.
When you convert in a browser canvas, the browser will decode the source image, draw the visible pixels, and export a new file. That’s good for compatibility, but it isn’t the same as keeping all of the original AVIF container. Depending on the browser, display, and export path, HDR or wide gamut material may be tone mapped or normalized to normal viewing.
This is generally not a practical problem for everyday web downloads, and regular photos. In many cases the converted JPG or PNG is the correct 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, decrease the JPG quality first. If it is still too big, resize dimensions after converting. File size limits are generally a mix of 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 handy, but if your folder is a mix of photos and graphics, it’s easy to make a bad batch decision.
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:
- Convert one photo to JPG at 90%.
- Convert one transparent or graphic file to PNG.
- Open both outputs.
- Check file size, transparency, and edge quality.
- 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 deciding what target format to use before you create a folder full of files you have to do over.
Privacy and metadata
The converter works within your browser. Your AVIF file is decoded in the browser, drawn onto an off-screen canvas, and exported as a new JPG or PNG blob via the browser’s image export API. The practical privacy benefit is simple: you do not have to upload the original file to a server to be able to convert it.
This re-encoding route also means the output is a new image file from pixels. Metadata in the original container, such as camera information or other non-pixel information, usually does not get passed along in the same way it would from a desktop editor that preserves metadata.
That is useful if you want a clean compatibility copy. It is not a substitute for an archival workflow. If you want to keep the original metadata, go with 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.
Use a modern version of Chrome, Edge, Safari or Firefox. If that does not work, the file might be corrupted, incomplete, mislabeled or encoded in a way your browser can not 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.
A full photo probably doesn’t have PNG as the correct output. If there is no transparency use JPG. Use PNG only if you need transparent or sharp edge graphics.
The color looks different.
Leave the AVIF as it is and try another browser. Test the file in the app you’re trying to send it to. If the image was part of an HDR or wide-gamut workflow, a compatible JPG or PNG might not look the same.
The upload form still rejects the converted file.
File size, extension, pixel dimensions and color mode requirements. Some forms will refuse valid image files if they are too large or their dimensions are outside the accepted range.
Should you keep AVIF after converting?
Usually, yes.
Delivery copies are to be JPG and PNG. They solve a compatibility problem for a given destination. They do not enhance the original AVIF, and a JPG export is no 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 if it was just a downloaded convenience file and you only need the converted copy.
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.
Plain English: Keep AVIF if you are optimizing a website Convert to JPG if you need a normal photo that will work in a conservative workflow Convert to PNG if you need transparency or crisp graphic detail