AVIF to JPG Converter — Free, Fast & Private

AVIF is a genuinely impressive format. Netflix ran the headline experiment back in 2020 and found that AVIF compressed photographic content roughly 50% smaller than JPEG at the same visual quality — on a site that streams to a quarter of a billion people, half the image bytes is not a rounding error, it is serious money. Google, Apple and Amazon all sit in the Alliance for Open Media behind the codec for the same reason. So no, this page is not here to tell you AVIF is bad. It is here because the format's weakest spot has always been compatibility, and in 2026 that spot is still weak.

The split is strangest on mobile, where you would expect everything to converge. Apple has stuck with HEIC — its own successor to JPEG — as the default capture format on iPhone since iOS 11, and only added AVIF decoding in Safari 16 during late 2022. Google went the other way: Android 14 ships with AVIF support baked in at the platform level, and Pixel-generation cameras increasingly push AVIF and HEIC outputs through app pipelines. The result is that the same photo can be a perfectly normal file on one person's phone and an unopenable mystery on the next. Neither camp is wrong; they just picked different futures, and everyone else's software has to cope.

Desktop is where the failure gets personal, though. Plenty of applications simply refuse to open an .avif file: older photo editors, content management systems, email clients, office suites, print-shop software, the photo kiosk at the drugstore. Windows is a particularly rich source of these failures — more on the infamous 0x88982f07 error below. JPG, meanwhile, has been the universal image format for over three decades. Every device, browser, and piece of software made in the last 30 years can read it. When you need reach rather than byte-level efficiency, JPG is the pragmatic choice.

Converting AVIF to JPG makes your images instantly shareable. If you are preparing photos for a marketplace listing, attaching images to a job application, uploading artwork to a platform that only accepts JPG, or sending pictures to a client who cannot open AVIF, this tool solves the problem in seconds. JPG files also embed cleanly into documents, spreadsheets, and PDFs without worrying about rendering support.

It helps to know the timeline, because it explains who can and cannot open your files. Chrome shipped AVIF by default in version 85, in September 2020. Firefox followed in version 93, October 2021. Safari — always the slowest of the three to adopt image codecs — held out until version 16 in September 2022. Opera and Edge inherited support through Chromium, so the modern browser world is covered. But "modern browsers" is a narrow slice of the software universe.

Everything outside the browser updates on a timescale measured in years or decades. Enterprise fleets run five-year-old Windows images. WordPress, the software behind roughly 40% of the web, only grew solid AVIF handling in recent releases, and older installs silently reject it on upload. Camera RAW workflows, print RIP software, POS systems and PDF processors were all built assuming JPEG or PNG inputs. A file that works in Chrome on your machine can fail in four different places between your desktop and the recipient's printer. That long tail is exactly the gap a JPG conversion closes.

If you have ever double-clicked an AVIF on Windows and been greeted by a cryptic code, here is what you were looking at. Windows imaging components report decode failures as hexadecimal error codes, and 0x88982f07 (WINCODEC_ERR_COMPONENTNOTFOUND) is the one that appears when no installed codec can handle the file — Windows' blunt way of saying "I don't know what this is." It shows up constantly with AVIF, because the AVIF codec is a separate Store download on many Windows versions rather than something preinstalled. You can confirm what a suspicious file actually is by opening it in a hex editor: every genuine AVIF starts with the bytes 00 00 00 xx 66 74 79 70 61 76 69 66 — that's the "ftypavif" brand signature near the start of the file. A JPEG, by contrast, always begins with FF D8.

The failures rarely announce themselves that politely, though. Common ones look like this:

• Email gateways strip or quarantine AVIF attachments, because corporate mail filters whitelist formats they recognise — and AVIF often is not on the list.
• CMS uploads reject the file with a bland "unsupported media type" message, leaving you to guess whether it is the format, the extension or the server config.
• Social platforms re-compress aggressively. Instagram's image pipeline is tuned around JPEG, and third-party measurements through 2023 found AVIF-source uploads getting squeezed hard — with quality effectively throttled by around 30% compared to what a clean JPEG upload preserves. Converting to JPG before uploading gives you control over that last compression step instead of leaving it to an algorithm.
• Print workflows refuse AVIF outright in most shops, because the RIP software expects JPEG, TIFF or PDF.

Each of these has the same fix: hand the platform a JPG. It costs you a few hundred extra kilobytes per image; the alternative costs a rejected listing, a bounced email or an afternoon of debugging.

Unlike most online converters, this tool does not send your images to a server. The entire conversion pipeline runs inside your own browser using standard web APIs: your file is decoded locally with the browser's built-in AVIF decoder, redrawn onto an HTML canvas, and re-encoded as a JPG — all in memory, on your device. Nothing is uploaded, stored, or logged anywhere. You can watch it happen yourself: open the browser's Network tab while converting and you will see no request carrying image data, because there is no backend to receive one.

• 100% local processing — your files never leave your browser, which makes it safe for private photos, client work, and confidential documents.
• No account, no watermark, no queue — the tool is free and works without registration.
• No file size limits imposed by us — the only limit is the memory your own device can spare.
• Works offline — once the page is loaded, you can convert images even if your connection drops. A server-based converter cannot pass that test.

The quality slider (50–100%) controls the JPG compression level, and picking a value is the one decision that actually changes your output. Here is how to think about it. JPEG encoding cuts the image into 8×8 pixel blocks and throws away frequency data — at high settings the discarded data is invisible noise; at low settings it becomes blockiness around sharp edges and mosquito noise near text. The damage is not linear: quality 95 might produce a file 40% larger than quality 75 while looking identical, and quality 40 halves the size again while looking obviously wrecked.

For most photographs, quality 60–80 is the sweet spot on the browser's encoder scale — files land dramatically smaller than the maximum while staying visually indistinguishable from the source. Stay around 80 for images with fine text, product shots with hard edges, or anything headed to print. Drop toward 60 for web banners and social uploads where the platform will re-compress anyway. Push toward 90–100 only for archive masters, and accept the size. There is one honest caveat: the exact mapping between slider position and encoder quality varies slightly between browsers, so treat the numbers as guidance and judge the preview, not the digit.

Also worth knowing: conversion cannot restore information the AVIF already lost. If the source file was saved aggressively, the JPG faithfully reproduces what is there. Always convert from the highest-quality AVIF you have, not a copy that has already been squeezed once. And because transparency cannot exist in JPG, any transparent areas in the source AVIF are flattened onto a white background — if you need transparency preserved, use the AVIF-to-PNG converter instead.

Here is a failure mode specific to format conversion that bites photographers more than anyone else. Since roughly 2015, cameras and phones store photos upright and record how to display them in an EXIF orientation tag — the pixel data sits in landscape, and a flag says "rotate 90° before showing." Modern software reads that flag and shows everything correctly, so nobody notices the arrangement. Until, that is, a conversion step quietly drops the tag: some decoders do not read it, some JPG encoders do not write it, and the output comes out sideways or upside down.

The safe practice takes two seconds: after converting a batch, glance at one image from each source device in the results list. If any come out rotated, you have learned something about that file's metadata before it reached a client. This page renders the image through the browser's own decoder — which honours orientation — and bakes the rotation into the pixels, so what you see in the preview is what the JPG contains. That is the more robust arrangement: orientation carried in pixels survives every downstream tool, while orientation carried in metadata depends on the next program in the chain reading it correctly. It is one more reason a converted file can be more portable than the original.

Drag in as many AVIF files as you need — the tool builds a queue and converts them one by one, showing live status for every item. Each finished image shows its original and converted size side by side, so you can immediately see the effect of your settings. Download files individually, or grab everything at once as a ZIP archive when you have converted two or more images.

Batches behave sensibly under pressure. A corrupted or exotic file gets flagged in the list while everything else keeps converting — a single bad image out of two hundred never poisons the run. The quality slider applies to the whole batch: adjust it, hit "Reconvert all", and compare the sizes until the balance is right. Expect the arithmetic to be roughly linear — a 12-megapixel photo is about nine times the pixels of a 1280×720 web image, so it takes about nine times as long per file. A recent laptop shrugs this off; a mid-range phone will warm up on batches above a few dozen large images, so keep the tab in the foreground while it runs.

If you run a website, you do not actually have to choose between AVIF and JPG for your visitors — the modern approach is to store the best format and let the CDN negotiate. Image CDNs like Cloudflare, Fastly and imgix inspect the browser's Accept header on every request: a Chrome 100+ visitor advertising AVIF support gets the AVIF variant (roughly 50% smaller), an older client falls back to the JPG. Done properly, this is invisible to users and saves real bandwidth at scale — that is precisely the setup Netflix's 2020 results pointed toward.

Manual conversion like this page fits everywhere that negotiation cannot reach: the email to a client, the marketplace listing, the print order, the CMS that predates Accept-header negotiation. A reasonable workflow keeps AVIF as your storage master and exports JPG copies the moment a file needs to leave that circle. You keep the compression benefit where it pays and pay the compatibility tax only where it is actually owed. There is a fuller write-up of that trade-off, with format history, on the dedicated AVIF-to-JPG guide page.

Three modern formats compete for the spot that JPEG has held for 30 years, and understanding their actual numbers helps explain why you are converting in the first place. WebP — Google's 2010 codec — typically saves 25–35% over JPEG at the same visual quality on photographic content. AVIF, built on the AV1 video codec and finalised as an image format in 2019, goes further: real-world measurements put it 50–55% smaller than JPEG and 20–30% smaller than WebP at equivalent SSIM scores. Netflix's 2020 compression study across 500+ clips confirmed an average 20% gain over WebP. Google's own Squoosh benchmarks, run at quality 60 on a 1920×1280 test image, showed AVIF at 67 KB against WebP at 91 KB and JPEG at 127 KB — roughly half the bytes for the same perceptual result.

JPEG XL is the third contender: a 2022 ISO standard that matches or beats AVIF on compression and adds lossless re-encoding of existing JPEGs at around 20% smaller without any quality loss. It also handles HDR, 10-bit colour, and animation in a single format. The problem is support: as of mid-2026, only Safari 17+ and Firefox (behind a flag until 128) decode JPEG XL natively. Chrome removed its JPEG XL trial in version 110 and has not restored it. That leaves JPEG XL in an even narrower compatibility window than AVIF, which is itself narrower than WebP.

The practical takeaway for this tool: you are likely converting AVIF because downstream software — email clients, print shops, older CMS platforms — only understands JPEG. WebP has the same problem; it is not JPEG. If you need to compare how your source AVIF would look as a PNG instead of a JPG — for cases where transparency matters — the AVIF-to-PNG converter gives you that option with one click and the same local-only privacy guarantee.

WordPress core added AVIF to its permitted MIME type list in version 6.5, released in March 2024. Before that release, uploading an .avif file to the media library produced a silent "Sorry, this file type is not permitted for security reasons" error. Hosts running PHP-GD without the libavif extension will still reject AVIF uploads on 6.5+ because server-side thumbnail generation requires a codec, not just a MIME whitelist entry. Confirm your host supports AVIF by checking gd_info() for AVIF Support => true, or simply convert to JPG before uploading to sites where you do not control the server configuration.

Shopify added AVIF support for storefront image serving in late 2023, but the merchant admin media uploader still normalises most image uploads to JPEG or PNG on its own processing pipeline. Files uploaded through third-party app connectors and bulk import CSVs behave differently again — many third-party Shopify apps send images through their own CDN with their own codec support list. The safe rule: upload JPEG originals to Shopify product listings and let the CDN handle format negotiation downstream; use this tool to do that conversion before your bulk CSV import.

Microsoft Excel and the Windows Photo Viewer ship without a bundled AVIF codec. Inserting an AVIF into an Excel sheet produces either a blank placeholder or the same 0x88982f07 decode error seen in older Windows imaging components. Installing the "AV1 Video Extension" from the Microsoft Store (app ID 9MVZQVXJBQ9V) resolves the issue for Windows Photo Viewer and most Store apps, but does not automatically fix COM-based hosts like Office — Excel reads images through its own GDI+ pipeline, which stays JPEG/PNG/GIF/BMP/TIFF regardless of codec extensions. Converting to JPG remains the only reliable fix for Excel. For a step-by-step guide to the codec install, see the AVIF file opener guide.

AVIF supports a full 8- or 10-bit alpha channel: the format can store images with smooth, anti-aliased transparency at no penalty to compression efficiency. This is one area where AVIF beats JPEG outright — JPG has no transparency channel at all. Conversion to JPG therefore involves a compositing step: wherever the source pixel is transparent or semi-transparent, the canvas places a background colour, and the default is white. If your AVIF was a product cut-out shot against a transparent background, the output JPG will have a white background where the cut-out sits. That may be exactly what you want for a white-background marketplace, but it is the wrong choice for a dark-theme site or a layered design. Use the AVIF-to-PNG converter if you need the alpha channel preserved — PNG carries full transparency and has near-universal software support.

Animated AVIF is a more recent feature: the format specification allows multiple frames in a single .avif file, producing animations similar to GIF but at a fraction of the file size and with full colour depth. Browser support for animated AVIF followed the static-image support with a short lag: Chrome 85+ plays them, Firefox 93+ plays them, Safari 16+ plays them. The catch is that animated AVIF files are structured as an AVIF image sequence, and most non-browser decoders — including the Windows AV1 codec extension — only expose the first frame. When this converter encounters an animated AVIF it decodes and exports the first frame of the animation as a static JPG. It will not produce a GIF, a video file, or a multi-frame output.

A useful diagnostic trick: check your AVIF file size before uploading. A static AVIF photograph at 1920×1080 and quality 70 typically lands between 80–200 KB. If your file is several megabytes and ends in .avif, it is almost certainly animated or a burst sequence. In that case, decide whether the first frame is the image you want, or whether you need to extract a different frame using a tool like ffmpeg before converting — ffmpeg -i input.avif -vframes 1 -ss 00:00:02 frame.jpg pulls the frame at two seconds if you need a specific moment.

If your file will not even preview, the AVIF opener page walks through how to view an AVIF first — including the Windows codec download that fixes 0x88982f07. If you need transparency preserved instead of flattened, the AVIF-to-PNG converter handles that. For a longer treatment of format history, browser timelines and the AVIF-vs-JPEG trade-off, see the dedicated AVIF-to-JPG guide. Otherwise, scroll back up, drop your files, and you are done in seconds.