Convert AVIF to JPG on Android

Open Chrome on your Android phone, navigate to aviftojpg.top and drop your AVIF file into the tool. Chrome decodes it in the browser — no upload, no app install — and saves the JPG straight to your Downloads folder. That is the whole workflow: three taps, one file, done.

This works because Chrome for Android has shipped a native AV1 image decoder since Chrome 85, released in August 2020. Any Android phone that has received a Chrome update in the last few years can decode AVIF files without any help from the operating system. You do not need Android 12, you do not need a hardware AV1 decoder chip, and you do not need to install a separate codec. If Chrome opens, it can decode AVIF.

The converter runs entirely on-device. Your photo never leaves the phone, which matters when the image is a document scan, an ID photo, or anything you would rather not send through a third-party server. Close the tab and the file is gone from memory.

The system photo gallery is a separate app from Chrome, and it depends on Android's media framework rather than Chrome's internal decoder. AV1 decoding in that framework began arriving in the Android 12 era, but the actual rollout varied considerably: some devices got it through a system update, others through a Google Play system component update, and others have not received it at all depending on the manufacturer and how long the device is still in active support.

The result is that the same AVIF file that displays perfectly in Chrome can produce a grey box or an error icon when you open the Downloads folder in Google Photos or the stock gallery app. This is not a corrupted file. The image is fine — the gallery just does not have a decoder for it. Converting to JPG before sharing or archiving is the practical fix.

The same limitation applies to most messaging apps on Android. If you try to share an AVIF from your Downloads folder through WhatsApp, Telegram, or a social platform, the app may show a preview but the recipient on an older device may see nothing, or the platform may silently reject the upload. JPG is the format every Android app has supported for over a decade, so converting to JPG removes the compatibility variable entirely.

Most Android users encounter AVIF files in one of three ways, and none of them involve the camera app. Your phone's camera shoots in JPG, HEIF, or sometimes RAW — it will not produce AVIF files under normal settings. The screenshots and screen recordings your phone generates are PNG or MP4.

• Saved from a web page. Chrome on Android has served AVIF images since 2020. When you long-press an image on a modern website and tap "Save image," you get an AVIF if that is what the server sent. The file lands in your Downloads folder labeled something like image.avif.
• Transferred from another device. A designer, developer, or photographer on a Mac or PC may send you AVIF files over email, Slack, or AirDrop. They are a standard web delivery format on those platforms, so the sender may not realize the recipient's gallery cannot display them.
• Downloaded from a content platform or cloud storage. Some stock photo services and design asset libraries now deliver AVIF by default because the files are smaller. If you download an asset from one of these services, check the file extension — it may not be the JPG or PNG you expected.

In all three cases, the AVIF is exactly what it looks like: a real image file that Chrome can display and this converter can re-encode. The problem is downstream compatibility, not the file itself.

Here is the exact sequence, including how to find the file on a typical Android device:

• Step 1 — Open Chrome and go to the converter. In Chrome's address bar, type aviftojpg.top and load the page. The tool area loads in the browser with no install prompt.
• Step 2 — Tap the drop zone to browse files. Tapping the upload area opens Android's file picker. Navigate to Downloads (or wherever your AVIF landed), then tap the file. The converter accepts multiple files — tap the first, then long-press others to select more before confirming.
• Step 3 — Wait for conversion. Chrome decodes the AVIF and re-encodes it as JPG on the phone's CPU. A typical web-saved image finishes in under two seconds. A large transfer from a desktop might take four or five seconds on a mid-range phone.
• Step 4 — Save the JPG. Tap the download button next to the converted file. Chrome saves it to your Downloads folder. For a batch, use the "Download all as ZIP" button and extract it afterward.
• Step 5 — Share or open the JPG. The JPG in Downloads opens in every gallery app, shares to every messaging app, and attaches to every email without any compatibility issues.

If you plan to convert AVIF files regularly, bookmark the converter in Chrome. On Android you can also add it to the home screen: tap the three-dot menu in Chrome and choose "Add to Home screen." It opens like an app but runs entirely in the browser with no installation and no background permissions.

Phones have less available memory than laptops, and that ceiling matters for large AVIF conversions. The decoder produces a raw pixel buffer before the JPG encoder runs: a 12-megapixel image decoded to RGBA uses roughly 48 MB just for the pixel data, plus additional memory for the encoder and output buffer. That is well within what a modern Android phone can handle for a single file.

Where you may notice pressure is with very large images or large batches. If you drop in twenty high-resolution images at once, the browser may slow down or fail on the later files as memory fills. The practical approach is to convert in batches of a few at a time, especially on phones with less available RAM or older SoCs. The converter processes files one at a time in a queue, so partial batches still work — you just download more than one ZIP.

Small-to-medium images — web-saved photos, downloaded assets, files shared from messaging apps — typically convert without any issue. The memory ceiling only becomes relevant with very large files, such as full-resolution exports from a desktop editor transferred to the phone for distribution.

A common mistake when encountering AVIF files for the first time is to rename the extension: changing image.avif to image.jpg in a file manager app. This does not convert the file. The bytes inside stay identical — still AV1-encoded image data in an ISOBMFF container — and most apps that try to open the renamed file will reject it or show a "file is damaged" error, because the extension says JPG but the file signature says something else entirely.

The correct operation is re-encoding: decode the AV1 image data to raw pixels, then compress those pixels using the JPEG algorithm and write the result to a new file. That is what this converter does. The output is a genuine JPEG file that any app or device can open, not a renamed AVIF wearing a JPG label.

This distinction also explains why converting to JPG reduces file size from a large AVIF. Wait — AVIF files are already small. Why is the JPG smaller? Because the AVIF you received was compressed at a quality level that produces a small delivery file. The JPG you get back is also compressed at a reasonable quality setting, producing a comparably sized file. What the JPG does not do is preserve the AVIF's exact compression quality — it is a new lossy encode, so keep the original AVIF if you want the source. See more on how AVIF and JPG compare technically.

Some Android file manager apps added AVIF preview support as part of broader AV1 decoder updates. Google Files, Samsung's My Files, and similar apps on newer devices may show a thumbnail and even open an AVIF for viewing. Whether you see this depends on your device, your Android version, and the app version — behavior varies enough that "try it and see" is genuinely the answer.

Even when a file manager can display an AVIF, it almost never offers a "Save as JPG" or "Convert" option. Viewing and re-encoding are different capabilities. The file manager decodes the image for display but does not expose a path to write a re-encoded version to a new file. You would need a dedicated image editing app that supports both opening AVIF and exporting JPG — and on Android, that category is thin.

The browser converter fills that gap without requiring any additional app. It uses Chrome's decoder (the same one the file manager may be calling) and adds the re-encoding and save step that the file manager leaves out. For batch conversions, the ZIP download option makes it practical to convert a folder's worth of AVIF files without tapping through them individually.

Once you have a JPG in your Downloads folder, it works everywhere. Android's share sheet offers it to every installed app that accepts images. The most common destinations all handle JPG without any configuration:

• Messaging apps. WhatsApp, Telegram, Signal, and Google Messages all display JPG inline in the chat, including in previews before the recipient downloads the full image. AVIF may display in the app but fail on the recipient's device if their OS does not have a decoder.
• Email attachments. JPG is the universally safe attachment format for images. Recipients on older Android versions, older iPhones, or desktop mail clients from any era will open it without issue.
• Web forms and upload fields. Job application portals, government forms, and document upload systems often restrict accepted types to JPG and PNG. An AVIF attachment may be silently rejected with a vague "invalid file type" message. Converting to JPG before uploading avoids that friction.
• Social platforms. Instagram, Twitter/X, LinkedIn and similar platforms accept JPG uploads from Android without any issues. Some platforms re-encode on their servers regardless of input format, but they apply their own compression to a file they can actually read — and they may not be able to read an AVIF at all on older backend infrastructure.

Android 12, released in October 2021, was the first version where Google formally added AVIF decoding to the Android media framework. Before that release, the operating system itself had no built-in way to decode AVIF files — individual apps could bundle their own decoders, and Chrome did exactly that, but the system-level support that gallery apps, file managers, and background services rely on simply was not there.

What Android 12 added was a software AV1 decoder integrated into the MediaCodec and BitmapFactory APIs. That means any app calling the standard Android image APIs — Google Photos, the stock gallery, Files by Google, and most third-party file managers — can decode AVIF without needing to bundle their own decoder, as long as the device is running Android 12 or later and has received the relevant update.

The rollout was not instant or uniform, though. Several factors affected whether a specific phone actually gained AVIF support even after Android 12 arrived:

• Manufacturer update schedules. Not every Android 12-capable phone received the update on day one. Carrier-locked devices and budget phones from some manufacturers lagged by months, and a few never received Android 12 at all despite being capable of running it.
• Google Play system updates. Google distributes some media codec updates through the Play Store rather than full OS updates. Devices on Android 12 that also received the relevant Play system update may have better AVIF handling than identical devices that did not. Checking for updates in both Settings and the Play Store can sometimes resolve a decoding gap.
• Hardware AV1 decoders. Phones with chips that include a hardware AV1 decoder — a feature that became more common from 2022 onward — benefit from faster decoding and lower battery use. Phones that rely entirely on software decoding can still open AVIF files but may take noticeably longer on very large images.
• Android 13 and later. Successive releases tightened AVIF integration and improved animated AVIF handling. If you are on Android 13 or 14 and still seeing blank thumbnails in the gallery, the most likely cause is that the gallery app itself has not been updated recently, not that the OS lacks a decoder.

The practical upshot: Android 12 on a well-maintained device should decode AVIF natively in most apps. Android 11 and earlier will not, regardless of the app. If you are unsure which version your phone runs, go to Settings → About Phone → Android version. Whatever the answer, the browser-based converter at aviftojpg.top works on any Android version that can run a recent Chrome build, because Chrome's decoder is independent of the OS version.

Even on Android 12 and later, you will occasionally encounter apps that cannot accept or display an AVIF file. The problem is not always the OS decoder — sometimes the app itself has a hard-coded list of accepted formats, or its file-picker filter excludes "image/avif" from the MIME types it will pass through. Knowing why the failure is happening helps you choose the right fix.

Scenario 1: the share sheet shows the app but the image arrives blank. The app received the file but could not decode it. This is typical of apps that have not been updated to support AVIF, even when the OS can decode the format. The fix is to convert to JPG first, then share the JPG. The converter at aviftojpg.top produces a standard-baseline JPG that every app can read.

Scenario 2: the target app does not appear in the share sheet at all. The app's intent filter does not include "image/avif" as an accepted type, so Android does not offer it as a share target. Again, converting to JPG resolves this immediately — JPG share targets are universal.

Scenario 3: an upload form rejects the AVIF with a validation error. Web forms that run validation on the file type — checking either the extension or the MIME type — will reject AVIF if the allowed list was written before the format was common. The fix is the same: convert to JPG before uploading. The resulting file is a plain JPEG with a .jpg extension and "image/jpeg" MIME type, which passes every upload validator written in the last two decades.

Troubleshooting steps if the converted JPG still does not work:

• Check the download completed. If Chrome's download notification disappeared quickly and the file is not in Downloads, a storage permission issue may have interrupted the save. Open Chrome, go to Settings → Site Settings → Automatic Downloads, and make sure the converter site is allowed.
• Verify the file extension. The converter saves files with a .jpg extension. If your file manager shows it without an extension or with .avif still attached, the download may have saved an incomplete file. Delete it and convert again.
• Clear the app cache on the receiving app. Some gallery and messaging apps cache thumbnail data aggressively. After receiving a new JPG file, force-stop the app and reopen it to trigger a fresh scan of the Downloads folder.
• Try a different file manager. Files by Google reliably reads both AVIF and JPG files and surfaces them by date in a single view. If your default file manager is not showing a newly converted file, Files by Google is a reliable fallback for locating it.

The conversion step takes under five seconds on most phones for a typical web image. Building it into a short habit — convert first, then share — avoids all of the compatibility questions at once, regardless of which app you are sharing to, which version of Android the recipient is on, or whether the destination is a web form, an email client, or a messaging app.