AVIF to JPG: How to Convert AVIF Files on Any Device

Why Everything Is Suddenly an AVIF File

Websites serve AVIF because it makes pages faster, and the tooling that produces it switched on largely without asking anyone. AVIF (AV1 Image File Format) stores still images using the open-source AV1 video codec, developed by the Alliance for Open Media, and it typically produces far smaller files than JPEG at the same visual quality (web.dev).

The numbers explain the adoption. WordPress 6.5 added native AVIF support and cited files "up to 50% smaller than JPEGs while maintaining the same image quality" - and WordPress sites can now auto-convert every uploaded JPEG to AVIF. Image CDNs do the same negotiation silently: if your browser says it accepts AVIF, that is what gets delivered. So when you right-click and save a product photo, a recipe image, or a wallpaper, you increasingly get an .avif file whether or not anything on your computer can open it.

Browser support is no longer the problem. As of the May 2026 usage data on caniuse.com, 93.42% of global browser traffic supports AVIF: Chrome since version 85, Firefox since 93, Safari fully since 16.4, and Edge since 121. The gap is on the desktop: image viewers, older editors, upload forms, and company systems that expect a JPEG and reject anything else. That gap is exactly why "avif to jpg" is one of the most-asked conversion questions on the web right now, with the same thread recurring across r/techsupport and photography forums.

The Fastest Way to Convert AVIF to JPG

The fastest route is a purpose-built converter in your browser: open mochify.app/avif-to-jpg, drop the file in, download the JPG. No account is required for up to 3 images per session, and a free account raises that to 25 images per month with a 20MB per-file limit.

Two things make this route worth choosing over a random converter site. First, the encoder: Mochify re-encodes to JPEG with Google's jpegli, which produces noticeably better quality per byte than the legacy encoders most converters use (more on the data in the quality section below). Second, the privacy model: your image is streamed into server RAM at api.mochify.app, encoded, returned, and wiped immediately - no disk writes, no logs containing file data, nothing retained after the request completes.

You can also skip the format decision entirely. Mochify's Magic Flow interface takes plain English, so a prompt like "convert these to JPG for email and strip all metadata" handles the format, the quality, and the EXIF cleanup in one pass. There are no settings panels to learn; you describe the result you want.

Got a folder of them? Paid tiers batch up to 25 files at a time, which turns a scraped product catalog or a client's mixed-format handoff into one job instead of twenty-five tabs. Try it now.

Convert AVIF to JPG on Windows

Windows can open and convert AVIF natively, but only after you install a free codec, which is the step most people are missing. Photos, Paint, and File Explorer thumbnails all depend on the AV1 Video Extension from the Microsoft Store. Without it, double-clicking an AVIF gets you an error or a prompt to buy or download a codec.

The native route, step by step:

1. Install the AV1 Video Extension from the Microsoft Store (Photos usually links to it directly when it fails to open an AVIF).
2. Open the .avif file in Paint.
3. Choose File → Save as → JPEG picture.

That works fine for one file. It gets tedious at five and unworkable at fifty, and Paint gives you no control over the JPEG encoder or metadata handling. For anything beyond a quick one-off, a batch tool is the better answer: drop the whole set onto the AVIF to JPG converter instead.

One more Windows note: if you just need to see the image rather than convert it, drag it into any modern browser tab. Chrome, Edge, and Firefox all render AVIF without any extensions.

Convert AVIF to JPG on Mac

macOS has handled AVIF natively since Ventura (macOS 13): Preview opens it, Quick Look previews it with the spacebar, and Safari renders it. Converting is a four-click job:

1. Open the .avif file in Preview.
2. Choose File → Export.
3. Set Format to JPEG and pick a quality level.
4. Save.

On Monterey or earlier, there is no native support - Preview simply will not open the file. Rather than installing third-party Quick Look plugins on an old OS, the simpler route is the browser: view it in Safari or Chrome, or convert it directly with Mochify's converter, which runs in any modern browser regardless of your macOS version.

Preview's export does the job for single files, but like Paint it applies the system encoder with minimal control, and batch exporting through Preview means selecting carefully and hoping. For folders of files, batch conversion with an explicit prompt ("convert all of these to JPG, max quality, strip metadata") is faster and more predictable.

Command-Line and Batch Conversion

For scripted or repeatable conversion, you have two solid options: a general-purpose image tool like ImageMagick, or Mochify's own CLI. ImageMagick converts AVIF with a one-liner (magick input.avif output.jpg) when built with AVIF support, and it runs entirely on your machine - a good fit if you already have it installed and the defaults suit you.

The Mochify CLI (mochify, installed via brew install mochify on macOS, curl binaries on Linux, or cargo install) takes the natural-language approach to the terminal:

mochify -p "convert everything in ./downloads to JPG and strip all metadata" ./downloads/*.avif

Authenticate once with mochify auth login (browser-based OAuth; credentials are saved locally to ~/.config/mochify/credentials.toml) and the same account and limits as the web app apply. One architectural point worth being straight about: the CLI is a client over the Mochify API, not a local encoder. Your images travel over HTTPS to api.mochify.app, are encoded in RAM by the same C++ engine as the web app, come back to your machine, and the originals are wiped from the server immediately with nothing written to disk. If you need conversion that never touches a network, ImageMagick is the honest recommendation; if you want jpegli output, batch prompts, and one workflow across web, terminal, and AI agents, that is what the CLI is for.

The same applies to agent workflows: Mochify's local and hosted MCP servers and the REST API (POST /v1/prompt on api.mochify.app) all accept the identical plain-English instruction, so an automated pipeline can handle AVIF-to-JPG conversion the same way you would by hand. See how the Mochify MCP server works for the full setup.

Will Converting AVIF to JPG Lose Quality?

Usually not visibly, but it is worth understanding what actually happens. Almost every AVIF you meet in the wild is already lossy-compressed, and converting it to JPG is a second lossy encode. The conversion cannot add quality back; the goal is to preserve what is there while producing a file every application accepts.

Three honest caveats:

• Encoder choice matters more than people think. JPEG encoders are not equal. In a controlled study, raters preferred jpegli-encoded JPEGs 54% of the time over libjpeg-turbo and MozJPEG output, while jpegli used 2.8 bits per pixel against their 3.8 and 3.5. A weak converter can visibly degrade your image at the same file size a good one preserves it. Mochify uses jpegli for exactly this reason; our Jpegli guide covers the quality-per-byte story in depth.
• HDR and deep color get flattened. AVIF supports 10-bit and 12-bit color and HDR; JPEG is 8-bit SDR. An HDR AVIF gets tone-mapped down during conversion, which changes the look more than the compression itself does. The same tradeoff applies when converting pro-camera HIF files to JPG, and the practical advice matches: for sharing and compatibility, convert; for editing headroom, keep the original.
• Transparency does not survive. JPEG has no alpha channel. An AVIF with a transparent background gets flattened onto a solid one. If you need the transparency, convert to PNG or WebP instead of JPG.

And a note on direction: converting AVIF to JPG makes the file bigger. In the Chrome codecs team's published comparison, AVIF leads JPEG XL, WebP, and JPEG on compression efficiency across the tested sets. You are trading bytes for compatibility, which is a perfectly good trade when a form, a client, or an app demands a JPEG. For your own website, the better move is usually the reverse - see our guide to WebP, AVIF, and JPEG XL in 2026 before converting a site's images back to JPEG wholesale.

Cheat Sheet: Every AVIF to JPG Route

FAQ