Skip to content
Server-sideDeleted in 30 minutes

Convert AVIF to JPG

AVIF is the format you end up with after saving an image from a modern website, and then discover that Photoshop, Word or your photo viewer refuses it. This converts it to JPG. Your browser is very likely the only piece of software on your machine that reads AVIF at all, which is exactly why the file is stuck.

Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.

Add to Chrome — free
AVIFJPG

Drop your AVIF file here, or click to browse

Up to 50 MB. Deleted automatically after 30 minutes.

What it does

  • No account, deleted within 30 minutes
  • Batch conversion with a ZIP download
  • Transparency flattened onto a chosen background
  • Full resolution kept

How to use AVIF to JPG

  1. 1

    Add the AVIF files

    Images saved from a website, exported from a build pipeline, or handed over by a designer. Several at once is fine; they come back as a ZIP.

  2. 2

    Pick a background if the image has transparency

    JPEG has no alpha channel, so anything transparent has to become a solid color. White is the usual answer and the default. If the image will sit on a dark page, choose that color here rather than discovering the halo later.

  3. 3

    Convert and download

    The file is decoded and re-encoded on our server, then deleted — the upload as soon as the conversion finishes, the result within 30 minutes.

How it works

The browser decodes the AVIF using the same code path it uses to display one on a web page, draws the decoded pixels to a canvas, and asks the canvas to encode JPEG, on our server.

The reverse conversion is harder than this one for a specific reason. Browsers ship an AV1 decoder — they need one to display AVIF images and play AV1 video — but they do not expose an AV1 encoder to web pages. So reading AVIF in a browser is free, and writing it is impossible, which is why PNG to AVIF runs on a server and this page does not.

Why you have an AVIF in the first place

Almost always because you saved an image from a site that had already optimized it. AVIF's efficiency is genuinely large — the same picture at the same quality is routinely a third the size of a JPEG — so it has been adopted quickly by anyone serving a lot of images. Right-click, save, and you get whatever the site was serving, which increasingly is AVIF.

The awkwardness is that the format won the web before it won the desktop. A file that displayed perfectly a second ago in the browser is refused by the program you wanted to open it in, which reads as the file being broken when it is nothing of the kind.

What changes and what does not

Dimensions do not change. No resizing happens; the output has exactly the pixel dimensions of the input.

Color is preserved for ordinary images. AVIF supports wider color and higher bit depth than JPEG, so an image using either is narrowed to what JPEG holds. Files saved from typical websites are standard 8-bit sRGB and lose nothing here.

Transparency is flattened. Covered above, and the single most common surprise.

Animation is lost. AVIF can hold an animation sequence, and JPEG cannot. Only the first frame is converted. This is rare in practice, since animated AVIF is uncommon on the web, but it is worth knowing if a file that moved comes back still.

When to convert and when not to

Convert when a specific piece of software refuses the file and you need it now. That is a good reason and it is why most people arrive here.

Do not convert a whole library "to be safe". You will roughly triple the storage and give up a generation of quality for a compatibility problem that keeps shrinking as software catches up. Keep the AVIF as the original and convert the individual files you need, when you need them.

Examples

A photo saved from a website

hero.avif — 2400x1600, 210 KB
hero.jpg — 2400x1600, 680 KB

Three times larger for the same picture, which is the cost of leaving AVIF. The pixels are unchanged in dimension and near-identical in appearance; the file is bigger because JPEG's compression is thirty years older and simply less efficient.

A logo with a transparent background

brand.avif — 600x200, transparent
brand.jpg — 600x200, white behind the mark

The transparency is gone and cannot come back. On a white page nobody notices; on any other color there is now a white rectangle around the logo. If the image needs to sit on a colored background, convert it to PNG or WebP instead — both keep the alpha channel.

Frequently asked questions

Why does my computer refuse to open AVIF files?

Because support arrived in browsers years before it arrived anywhere else. Chrome, Firefox, Safari and Edge all decode AVIF, while a great deal of desktop software still does not: older Photoshop versions, most Office applications, many photo viewers, and almost anything that predates 2022. That gap is the entire reason this page exists.

Does converting lose quality?

A little. The AVIF was already lossy, and JPEG is lossy again, so this is a second generation of compression. At the quality level used here the difference is not visible at normal viewing size, but it is real, and it compounds if you convert the same image repeatedly. Convert from the AVIF each time rather than from a previous JPG.

Why is the JPG so much larger?

AVIF compresses far better — commonly two to three times better than JPEG at matched quality. Leaving it trades that efficiency for compatibility, so a bigger file is the expected outcome. Nothing has gone wrong, and no setting on this page will get the size back down without also visibly degrading the image.

I need transparency. What should I use instead?

PNG if the image is flat artwork or has hard edges, WebP if it is photographic and the destination is a browser. Both carry an alpha channel, and both are far more widely supported than AVIF. JPEG is the wrong target whenever transparency matters, regardless of what the source was.