Convert AVIF to JPG on iPhone and iPad

Yes — and the support is solid. Apple added AVIF decoding to iOS and Safari in the 16.1 release, which shipped in late 2022. That means the Photos app, the Files app, Safari, and Chrome for iOS on any iPhone or iPad running iOS 16.1 or later can all display an AVIF file without installing anything extra. If you tap an AVIF link in Safari it renders. If you receive an AVIF in the Files app it previews. If someone shares one via AirDrop it lands in Photos and opens fine.

The catch is that "can display" and "can export as JPG" are two different things. iOS knows how to decode the format, but the built-in export paths — the Share sheet, the Save to Photos action, and the Files app's Quick Look — do not automatically re-encode to JPG on the way out. You end up with a file that looks fine on your own phone and causes confusion the moment it arrives somewhere that predates AVIF support.

The rest of this page covers the practical routes: a browser-based converter that works entirely on-device, the Photos app export flow, and the Files app path — plus the common traps to avoid before you send anything important.

AVIF is a great format for reading, but it creates friction in a surprising number of everyday situations. Email clients on older Android phones and Windows machines may show a broken image icon. Forms on government websites, school portals, and booking systems often include a file-type validator that passes JPG and rejects everything else. Photo apps in business software — HR systems, project management tools, CRM platforms — have image pickers that filter by extension, so a .avif simply never appears in the picker at all.

There is also the recipient problem. Sending a photo to a client, a teacher, or a recruiter is a transaction where you have no control over their setup. If they are on an older iPad, a Windows 10 laptop without the AV1 codec installed, or any version of Outlook, "I can't open this" is the reply you get back. Converting to JPG beforehand is the one step that eliminates the variable entirely. JPG has been universally readable for over three decades, and that matters when you need something to just work.

• Email attachments — many mail servers and clients strip or block unknown media types. JPG arrives without drama.
• Upload forms — government portals, school systems, and booking platforms typically allow only JPG and PNG.
• App image pickers — some iOS apps filter the photo library by extension, making AVIF files invisible in the picker.
• Recipients on older devices — iOS below 16.1, older Android, Windows without the AV1 codec extension, and legacy browsers cannot display AVIF.
• Office software — Word, PowerPoint, and most CRM tools accept JPG inline and may reject or mangle AVIF.

The simplest path on iOS uses this tool directly in Safari or Chrome — no app download, no account, and nothing uploaded to a server. Open aviftojpg.top in your mobile browser, tap the drop zone or the select button, and choose your AVIF file from the Photos library or the Files app. The converter decodes the file using iOS's own AVIF decoder and re-encodes it as JPG entirely on your device. When it finishes, tap the download button to save the JPG to your Files app, or use the Share sheet to send it directly or save it back to Photos.

This route works because Safari 16.1 includes a native AVIF decoder, so the browser already has everything it needs. The conversion runs locally in the browser sandbox: your file is decoded in memory, drawn onto a canvas, and exported as a JPG data URL. No bytes leave your phone. You can switch airplane mode on after the page loads and the converter keeps working — useful if you are dealing with sensitive images.

For a batch of images, drop them all at once. The tool processes a queue one file at a time and shows per-file status. When everything is done, the ZIP download button packages all the JPGs into a single archive that lands in your Files app under Downloads. From there you can share the whole ZIP or extract individual files.

One practical note on large files: mobile Safari has historically capped canvas memory, so a very high-resolution AVIF — the kind from a professional camera or a large scan — can fail on iPhone when the same file converts instantly on a laptop. If that happens, convert a few files at a time rather than the whole batch at once, and close other tabs to free up memory.

If the AVIF is already in your Photos library, there is a built-in path that sometimes produces a JPG, but it has one important condition: the image must actually be stored as an AVIF, not as HEIC. This distinction matters because the iPhone camera shoots in HEIC by default, not AVIF. Most AVIF files in your Photos library got there from the web, from AirDrop, or from a download — they were not shot on the camera.

To export from Photos: open the image, tap the Share button, and scroll down in the Share sheet to "Save to Files" or use an action that lets you pick the format. Some iOS versions show an "Options" button at the top of the Share sheet where you can choose "Most Compatible" — this forces JPEG output regardless of the original format. If that option is visible, tap it before completing the share action.

The "Most Compatible" setting does not always appear, and its behavior can vary between iOS versions. If you do not see it, or if the output still arrives as .avif, the browser route above is more reliable because the conversion step is explicit and controllable.

This distinction causes a lot of confusion, so it is worth being clear. HEIC and AVIF look similar — they both use the same ISOBMFF container structure — but the codec inside is completely different. HEIC uses HEVC (H.265), a video codec from MPEG. AVIF uses AV1, a royalty-free codec from the Alliance for Open Media. The iPhone camera shoots HEIC when "High Efficiency" is selected in Settings. AVIF files come from elsewhere: websites, design tools, web developers.

The reason this matters is that the conversion path is different for each format. iOS handles HEIC-to-JPEG natively in several places because HEIC is the camera format and Apple built the plumbing for it years ago. AVIF-to-JPEG does not have the same built-in shortcuts, which is why a browser converter is more reliable than hunting for an iOS menu. If you are not sure which format you have, open the file in Files, tap the info button, and check the file extension and MIME type. .heic or .heif = HEIC. .avif = AVIF. Do not guess from the thumbnail.

The two share one important characteristic: neither can be converted by renaming. Changing .avif to .jpg produces a file with a JPG extension and AVIF data inside it. Most applications that try to open it will fail or show a broken image, because they look at the file header bytes, not the extension, to decide how to decode it. The bytes say AVIF; the extension says JPG; the decoder gives up. Re-encoding through a converter is the only way to produce a real JPG.

If your AVIF is in the Files app rather than Photos, the situation is similar. Files can preview an AVIF just fine on iOS 16.1 and later — tap it and Quick Look renders it. But Quick Look is a viewer, not a converter. There is no built-in "Export as JPEG" option in Files.

The workaround from Files is to share the file to a tool that does the conversion. Tap the file, tap the Share icon, and choose whatever conversion app or action is available. If you have the browser open already, sharing to Safari and loading the file into the AVIF to JPG tool is one path. Some third-party file manager apps also include image conversion in their action menus if you have them installed.

The shortcut that does not work: renaming the file from .avif to .jpg inside Files. The file icon might change and it might even look like a JPG in the Files thumbnail view, but the bytes inside are still AV1-encoded AVIF data. Any application that inspects the file header — which every serious image tool does — will reject it or decode it incorrectly.

A few traps come up repeatedly when people try to convert AVIF on iPhone for the first time. Knowing them in advance saves the round trip of sending something that does not work and having to re-do it.

• Renaming .avif to .jpg. This only changes the filename. The file content is still AV1-encoded, and any application that reads file headers — which includes every image editor, most email clients, and all serious upload forms — will reject it or show a broken image. You need actual re-encoding, not a rename.
• Assuming "Save Image" produces a JPG. The "Save Image" action in iOS saves the image in its original format. If the source is AVIF, the saved file is AVIF. The only way to know what format ended up in Photos is to tap the image, open its info, and check. Do not assume JPEG because it looks fine on your screen.
• Confusing AVIF with HEIC. If you shot the photo on the iPhone camera, it is almost certainly HEIC, not AVIF. HEIC and AVIF have different conversion paths. Treating a HEIC file as AVIF runs you through the wrong set of steps. Check the extension first.
• Converting giant batches on a low-memory device. Mobile Safari caps canvas memory. Trying to convert twenty large AVIF files in one go on an older iPhone will fail partway through. Convert in smaller batches — five or ten files at a time — and close other tabs to free up memory between passes.
• Sending before checking what format was saved. Before attaching a file to an email or uploading to a form, tap it in Files and confirm the extension is .jpg, not .avif. The thumbnail looks the same either way.

The decision of whether to convert before sending comes down to one question: do you know for certain that the recipient's environment supports AVIF? If yes, skip the conversion. If there is any doubt, convert first. The cost of converting is a few seconds. The cost of "I can't open this" is a round trip, a re-send, and potentially a missed deadline.

Job applications and portfolio submissions. HR software and applicant-tracking systems are rarely on the cutting edge of image format support. Profile photos and portfolio images attached to applications should be JPG. A recruiter on Windows using an older version of Outlook may never see an AVIF attachment.

Forms that accept photo ID or documents. Government services, financial institutions, and schools usually specify JPG or PNG in the upload instructions. Even if the form does not validate the type, a processor reviewing the file on a legacy system may be unable to open it. JPG is the safe choice.

Sending to clients or colleagues. If you are sharing product shots, event photos, or any image a non-technical person will open, JPG is more reliable than AVIF across the full range of devices and email clients that might receive it. For a closer look at AVIF vs JPG and when each format is the right choice, the comparison page covers the trade-offs in detail.

Sending within a known ecosystem. If you are sharing with other iPhone users on iOS 16.1 or later, or with people who will open files in a modern browser, sending AVIF directly is fine. AirDrop between iPhones preserves the original format and the recipient's device can display it without conversion.

It helps to understand what is happening under the hood, because it explains both why the tool works and what its limits are on mobile. When you load the converter in Safari and drop an AVIF file into it, the browser hands the file to its native AV1 decoder — the same decoder it uses to render AVIF images on any webpage. That decoder produces a full RGBA raster in memory: four bytes for every pixel, with color and opacity for each one.

That raster is drawn onto an HTML canvas, and the canvas encoder re-encodes it as a JPEG data URL using the quality setting you choose. The JPEG file is assembled entirely in the browser's memory sandbox and handed to you as a download. Nothing is transmitted to any server. The whole process is functionally identical to what happens on a desktop browser — the difference is that mobile devices have stricter memory limits, which is why very large images can fail.

The batch queue works the same way: files are processed one at a time, each decoded and re-encoded in sequence, so peak memory usage is bounded by the largest single file in the batch rather than the total size of all files. If you are converting a mix of small and large files, the large ones are the constraint. For images from a high-resolution camera or a retina-display screenshot, consider splitting the batch into a handful of files at a time and giving the browser a moment between groups to free memory.

You can also use the same tool to convert AVIF to PNG if the destination requires a lossless format or needs to preserve a transparent background. PNG files will be larger than JPG, but the conversion mechanics on iPhone are the same.