AVIF has become the quiet workhorse of the modern web. Content delivery networks compress cached images into it, camera apps export it to save space, and a growing list of design tools ship it as a default. The problem arrives at the boundary: the moment the file meets software that predates the format. An email client renders it as a blank tile, an older portal lists JPEG and PNG in the accepted formats, and a print shop asks you to send something it can actually open. Converting to JPG is the universal handshake, and it should not require an account, a codec download, or uploading the file to a stranger’s server.
What AVIF is and why it keeps showing up
AVIF is an image codec built on the same video technology that powers modern streaming, which is why it squeezes substantially more detail into the same byte count than JPEG or WebP. That efficiency is exactly why pipelines adopted it: smaller files moving faster cost less to host. The cost is maturity. Browsers learned it first, servers second, and everything else still lags, so a file that is perfect on the web can be useless in a form, a document, or a print order. The format is not wrong; it is just ahead of the destinations.
Why JPG still travels everywhere
Twenty-five years of ubiquity did JPEG a favor no newer format can match: every operating system, email client, form builder, and print pipeline opens it without configuration. When a requirement simply says image and lists nothing else, JPEG is the safest read of it. When it lists formats explicitly, JPEG appears on the list. That is the entire argument for converting: you are not losing quality you can see, you are buying compatibility that the next system may not negotiate.
How the conversion works here
Your browser already carries an AVIF decoder, so the tool asks it to open the file, redraws the same pixels onto a canvas, and re-encodes the result as JPEG at the quality you set. The whole pass happens on your device; the file never crosses the network. Drop the AVIF in, check the size the tool reports beside the download, and save. When a batch of images needs the same treatment, run each one through in turn, which is faster than it sounds because there is no upload wait between files.
AVIF, WebP, and JPG: what to send where
A rule of thumb that covers most cases. To a website or a service that lists AVIF or WebP as accepted, send the modern format and keep the bandwidth savings. To an email attachment, a document insert, or a print service, send JPG. To a form with an explicit list, match the list. And when you are converting AVIF down to JPG, choose quality 90 or above for anything that will be viewed on a large screen, and 80 for thumbnails and form photos where a smaller file is the point. The converter here gives you that choice without forcing a default on you.
Frequently asked questions
Why convert to JPG when AVIF is smaller?
n
The destination decides. Upload forms, email clients, and print vendors that predate AVIF reject the file, and JPG opens anywhere. You pay for that universality in file size, which is the trade this page makes for you.
n
What quality setting should I use?
n
90 or above for anything viewed on a large screen, such as slides, banners, or a print draft, and 80 for thumbnails and form photos where a smaller file is the point. The gap between 80 and 90 shows up in fine detail under close inspection.
n
What happens to transparency?
n
JPG cannot store transparency, so if the AVIF carries an alpha channel the output is flattened. When you need the transparent areas to survive, use the PNG path instead.
n
Which browsers can decode the source AVIF?
n
The tool needs a browser that decodes AVIF: Chrome 85 or later, Edge 93 or later, Firefox 93 or later, or Safari 16 or later. On an older browser the tool says the file could not be opened, and updating the browser is the fix.
n
What is the maximum file size?
n
25 MB per file. A typical AVIF photo is well under that; if yours is near the ceiling, the JPG output at quality 90 will be a fraction of it.
n