Crop

Circle crop image Crop image

Optimize

Compress image Remove background Upscale image

Modify

Resize image

Convert

Other

Convert JPG to PDF

Loading your files…

Convert AVIF to JPG, Open It in Any App

Turn an AVIF photo into a universal JPG and open it anywhere.

or drop the image here

Quick answer

Convert AVIF to JPG and open the photo anywhere. A single AVIF converts right on your device with no upload needed, and you get a JPG back in under a second for most photos since AVIF input decodes natively and fast. Converting several at once sends them to our server, which packs the results into one download, and whatever is sent is deleted within about 2 hours. AVIF is not accepted everywhere yet. Instagram uploads are inconsistent, Windows without the AVIF codec extension cannot preview the file, older Photoshop versions reject it, and most print services still want JPEG. JPG works everywhere. Transparent areas in the AVIF get filled with white in the output, because JPEG cannot store transparency, which is a property of the JPEG format, not a tool choice. The output JPG is usually larger than the source AVIF, since AVIF compresses more efficiently. That size bump is the cost of universal compatibility.

How to convert AVIF to JPG

How to convert AVIF to JPG

Drag an AVIF onto the upload area, or click to pick one from your device. The conversion starts the instant the file lands, with no Convert button. A single AVIF is read by your browser's native decoder and written back out as JPEG right on your device, with nothing to upload. Drop several at once and they go to our server instead, which converts them together and hands back one download, with the files deleted within about 2 hours. When the JPG is ready, a stats line shows the input and output sizes, and the Download button drops it onto your device. For standard-size photos a single round trip usually takes under a second, since AVIF input rides the fast native decode path.

What happens to transparent areas

What happens to transparent areas

AVIF carries full transparency support, so its areas can be fully see-through or partly see-through. JPEG supports no transparency at all. Every transparent or part-transparent area in your AVIF has to be replaced with a solid colour before the JPEG is written, and the conversion fills those areas with white. If you need a different background colour. For example, if you want dark grey for a logo on a dark page, open the AVIF in an image editor, add a coloured background layer beneath the image, flatten the layers, and then convert the flattened file here. If you need the transparency itself to survive, convert to WebP or PNG instead of JPG. The white fill is a property of the JPEG format, not a setting this tool chose to hide from you.

Why AVIF does not work everywhere yet

Why AVIF does not work everywhere yet

AVIF is a newer format. Instagram and the wider Meta platforms have inconsistent upload support, with some workflows taking it while others silently reject it or re-compress it badly. Windows 10 and 11 need the AVIF Image Extension from the Microsoft Store to preview AVIF files in File Explorer and Photos, and without it the file shows up as a blank icon. Older Photoshop versions, before 2021, cannot open AVIF at all. Most stock agencies, print services, and e-commerce systems validate uploads against a MIME allowlist that predates AVIF. Email clients vary too, with Apple Mail showing it and Outlook on Windows not. Converting to JPG removes every one of these barriers in a single step, which is why compatibility, not quality, is usually the real reason to make this conversion.

Why the JPG is usually larger than the AVIF

Why the JPG is usually larger than the AVIF

AVIF and JPEG handle compression very differently. AVIF is a highly efficient modern format that shrinks photos dramatically. JPEG is the older, universally compatible format that trades compression efficiency for reach. So when you go from AVIF to JPEG, the output grows. In our measurements, AVIF files made from JPEG sources run 40 to 86 percent lighter than the original, and converting back brings the size close to what the original JPEG weighed. The JPEG writer runs at near-maximum quality, so the growth is entirely from format efficiency differences, not from re-compressing your photo at a lower setting. Think of it as paying bytes for compatibility: the trade is worth it when you need the file to open everywhere.

Where your file is processed

Where your file is processed

The answer depends on how many photos you bring. Drop one AVIF and the conversion happens entirely on your device: the browser's built-in image engine decodes the file and writes it as a JPEG, with nothing crossing the network. You can verify this yourself by checking the Network panel in your developer tools during a single conversion: the request log will show no outbound image traffic. Drop several AVIFs and they travel to our server instead, where they are converted together and returned as a single download. Whatever you send to our server is deleted within about 2 hours, and a clear-now button on the result screen lets you remove them immediately. Your photos are used only to produce your JPGs. Nothing is retained after the job is done.

Does this tool handle animated AVIF?

Does this tool handle animated AVIF?

The converter keeps only the first frame of an animated AVIF. Every later animation frame is dropped, and the output is a still JPEG of that opening frame. JPEG itself has no animation support to fall back on. Animated AVIF sequences are usually short loops used in place of GIF for better quality and smaller files on the web. If you need to pull multiple frames out of an animated AVIF, a dedicated video or animation tool is the right choice. This converter's scope is single-image still conversion, and for a normal still photo none of this applies and the conversion behaves exactly as you expect.

How it works

  1. Drop or pick your AVIF

    Click the upload area or drag an AVIF onto it. The conversion starts the moment the file lands, with no Convert button. A single file is handled on your device, while several at once go to our server.

  2. Let the conversion run

    For a single AVIF, the browser's native decoder and JPEG writer run on your device, and a standard-size photo usually finishes in under a second. Converting several at once runs on our server and returns one download.

  3. Read the output sizes

    A stats line shows the AVIF input size and the JPG output size side by side. Expect the JPG to be larger, since AVIF compresses more efficiently than JPEG.

  4. Download the JPG

    Click Download to save the result. The file keeps its original name and switches to the .jpg extension for you, so nothing needs renaming.

Related tools

Reverse the conversion, or explore other AVIF and JPG workflows.

JPG to AVIF AVIF to PNG All format converters

Frequently asked questions

Why convert AVIF to JPG?

AVIF is not universally supported. Instagram uploads are inconsistent, Windows without the AVIF codec extension cannot preview the file in File Explorer, and older Photoshop versions and most print services reject it. JPG works on every device, every operating system, every social platform, and every editor. Converting trades AVIF's slimmer file size for guaranteed compatibility wherever you actually need to open or share the picture, which is usually the whole reason for the conversion.

What happens to transparent areas when I convert to JPG?

AVIF carries full transparency support, so areas can be see-through or partly see-through. JPEG cannot store transparency at all. The conversion fills every transparent area with white. If you need a specific background colour, paint it onto the AVIF in an editor before converting. If you need to keep the transparency itself, convert to WebP or PNG instead. Any tool that claims to preserve transparency when converting to JPG is incorrect, since the JPEG format makes that impossible.

What happens to my files? Are they uploaded anywhere?

It depends on how many you convert. A single AVIF is handled entirely on your device using the browser's own image engine, with nothing uploaded. You can confirm this by opening the Network panel in your developer tools during a single conversion: you will see no outbound image requests. Converting several at once sends them to our server, which converts them together and returns one download, and those files are deleted within about 2 hours, with a clear-now button on the result screen. We keep nothing once the job is finished.

What is the AVIF image format?

AVIF is a modern still-image format built on advanced video compression technology. It produces much smaller files than JPEG and WebP at the same visual quality, typically 40 to 86 percent lighter than JPEG. It was designed as an open, without licensing fees format. Browser support reached 94 percent globally in 2026, but many desktop apps, upload forms, and social platforms still do not accept it, which is why converting to JPG for compatibility is such a common task.

Is there a cost to use this converter?

Yes. Converting is available at no cost. You do not need to create an account or register. Your output arrives without any watermark. The only practical limit is your device's memory, which may restrict very large images on older hardware. A single image converts right on your device. Batches of several at once run on our server and results are deleted within about 2 hours.

Can I convert several AVIF files to JPG at once?

Yes. Drop several AVIF files and they are converted together on our server, then handed back as a single download. The files you send are deleted within about 2 hours, and you can clear them sooner from the result screen. A single file is instead handled right on your device with nothing uploaded. AVIF input decodes fast, so even a large batch finishes quickly.

The details

Notes from the team on craft, formats, and the small decisions behind a good result.

Why AVIF input is fast but AVIF output is slow
One of the most common misreadings of AVIF is that it is always slow. Decoding AVIF is fast. The browser's native AVIF decoder, present in Chrome since version 85, Firefox since 93, and Safari since 16.4, runs in compiled native code with no JavaScript overhead. For a typical web-sized AVIF, native decode takes tens of milliseconds. Encoding AVIF is a completely different job. The codec's compression tests many prediction modes per block and runs expensive rate-distortion passes. When this site outputs AVIF, on the JPG to AVIF page, it uses a heavy software encoder. When it inputs AVIF, on this page, it uses the fast native decoder, with no module to download, no warm-up, and no several-hundred-millisecond init. That is exactly why AVIF to JPG conversion feels fast even though JPG to AVIF takes seconds.
The transparency problem in detail: alpha, compositing, and white fill
AVIF's transparency layer stores per-area opacity from 0, fully see-through, to 255, fully opaque. When the browser draws the AVIF onto a drawing surface and then encodes that surface as JPEG, the compositing step has to resolve each area's final colour. The surface starts as transparent black by default. The JPEG output path then fills the surface background with white before encoding, because JPEG must produce a fully opaque result. So every transparent region in your AVIF becomes white in the JPG. Partly transparent areas are composited onto white, so a region at 50 percent opacity lands halfway between its own colour and white. There is no setting to change this fill without drawing the compositing yourself onto a surface with a custom background, which is a job for an editor, not a converter.
Quality measured: what 43.66 dB PSNR means in practice
PSNR, Peak Signal-to-Noise Ratio, is measured in decibels and shows how closely a re-encoded image matches its source. Higher is better. In our end-to-end test run, the JPEG writer used here produced 43.66 dB PSNR on a standard photographic test image at the default quality. For reference, 36 dB is usually described as the threshold below which differences become clearly visible to most viewers under normal conditions, and 40 dB is generally rated perceptually transparent for photographic content. At 43.66 dB the output is visually identical to the source for photos viewed on screens at typical sizes. For graphics with sharp edges, fine text, or areas of extreme contrast, faint JPEG artifacts may show, since JPEG's block-based compression treats those regions differently from smooth photographic gradients.
AVIF compatibility: where it works and where it still fails
As of mid-2026, AVIF decodes in all major browsers, but compatibility with non-browser software is still patchy. On Windows, the AVIF Image Extension from the Microsoft Store adds support to Photos and File Explorer on Windows 10 and 11, and without it AVIF files appear as blank icons. Adobe added AVIF support in Lightroom 13.3 in 2024 and Photoshop 23.2 in 2022, so earlier versions cannot open it. Affinity Photo 2.3 from 2023 supports AVIF import and export. Paint.net needs the AVIF plugin at no cost. On macOS, Preview has read AVIF since Monterey. On phones, the system photo viewer supports AVIF on iOS 16 and Android 12 and later. The gaps are real and concentrated in enterprise tools, upload forms, and print workflows, which are exactly the situations where converting to JPG is the practical answer.
AVIF versus HEIF: the difference and why it matters
Both AVIF and HEIF, the High Efficiency Image File Format, store images using modern video codec compression. HEIF typically uses its own engine, while AVIF uses a newer, without licensing fees codec. The key distinction for web use is licensing. The codec behind HEIF carries per-device royalties that browser makers are reluctant to pay, which is why Safari supports HEIF but Chrome does not. The codec behind AVIF is without licensing fees by design, built by an industry alliance that includes Google, Mozilla, and Apple. That is why AVIF enjoys broader browser support than HEIF despite HEIF being the older format. iPhones have captured photos as HEIF since the iPhone 7, and those files carry a .heic extension. HEIC to JPG conversion is a different tool category from AVIF to JPG. This converter handles AVIF input only, so if you have a .heic file from an iPhone, you need the HEIC to JPG converter instead.
When to keep AVIF and when to convert to JPG
A useful rule: keep AVIF when you control both ends of the workflow, and convert to JPG when the file has to pass through a system you do not control. If you are delivering images on a site you built, with a CDN that supports format negotiation, AVIF is the better choice, being lighter, visually equal, and now covering 94 percent of browser traffic. If the image is heading into an email newsletter, a social upload, a form submission, a client-supplied print template, a shared folder others open on older software, or any legacy content system that validates file types, JPG is the safer choice. The practical pattern for most web projects is to store AVIF originals and produce JPG exports on demand for any situation that needs universal compatibility.