Convert AVIF to JPG for Any Device
Convert AVIF to JPG in your browser. Both formats are lossy, so this is a re-encode rather than a copy — the quality you pick decides how much of the original survives the second pass.
Your images never leave your device
Nothing to delete later
Location data stays yours
Works in every modern browser
How it works
- 1
Add your AVIFs
Drop the files onto the page or click to browse and select them.
- 2
Set quality and background
Choose how hard to compress, and what colour any transparency flattens onto.
- 3
Download
Save the JPEGs individually or all at once as a zip.
Why use this tool
Quality is yours to set
A second lossy pass always costs something, so the slider is exposed rather than hidden behind a default.
Transparency handled explicitly
JPEG has no alpha channel, so you choose the colour it flattens onto instead of getting white by surprise.
Genuinely smaller files
Unlike a PNG, the output is comparable in size to the AVIF, which is the point of choosing JPEG.
Accepted almost anywhere
Upload forms, email clients and legacy systems that reject AVIF have taken JPEG for thirty years.
Location data under your control
A photo AVIF may carry GPS coordinates, and you decide whether they survive into the JPEG.
Nothing is uploaded
The re-encode runs on your device, so a personal photograph never becomes a file on someone else’s server.
Two lossy formats in a row: what generation loss actually does
This conversion is the classic case of generation loss, and understanding it changes how you use the quality setting. The AVIF you start with has already been through one lossy encoder: AV1 analysed the picture, decided which detail the eye would not miss, and threw it away. Converting to JPEG runs a second, completely different lossy encoder over the result. The trouble is that the JPEG encoder cannot tell the difference between real detail and the artefacts AVIF left behind. It faithfully spends bits preserving AVIF’s smoothed patches and blocking, then adds its own quantisation error on top. The damage compounds rather than cancels. In practice a single conversion at a sensible quality is close to invisible, and that is why this is a normal thing to do. What is not normal is doing it repeatedly — convert to JPEG, edit, save, convert again, and the picture visibly softens. Always go back to the AVIF original for each new export rather than re-exporting an export.
Quality 100 is not lossless, and it is usually the wrong choice
The most common mistake here is dragging the quality slider to maximum on the assumption that it disables compression. It does not. JPEG has no lossless mode: at quality 100 the encoder still transforms the image in 8×8 blocks and still quantises the coefficients, just with a very fine quantisation table. It also, in most encoders, still discards colour resolution unless you explicitly disable subsampling. What you get is a file several times larger than quality 90 for a difference almost nobody can see, which is a strange result when the entire reason to choose JPEG was file size. The band that actually matters is roughly 80 to 92. Below 75 the 8×8 block structure starts to show in flat areas and around edges; above 92 you are mostly paying for artefacts the eye cannot resolve. If you truly need every pixel intact, JPEG is the wrong destination and PNG is the answer.
JPEG has no transparency, so you are picking a background whether you decide or not
This is the part that produces the ugliest surprises, because it happens silently. A JPEG file cannot store an alpha channel at all — the format predates the idea. So if the AVIF has transparency, something must fill it, and if you do not choose, the encoder picks for you, usually white and occasionally black. A logo that was designed to sit on any background arrives with a white rectangle behind it, which looks fine on a white page and terrible on a dark one. Worse, semi-transparent pixels are not simply made opaque; they are blended with the fill colour, so the soft anti-aliased edge of a cut-out is permanently mixed with white and can never be separated again. There is no undo for this in the JPEG. If the image has any transparency at all and the destination might not be white, either flatten deliberately onto the colour you will actually use, or convert to PNG instead.
Why fine coloured detail smears and brightness detail does not
If red text or a thin coloured line looks muddier after conversion while the rest of the picture looks fine, you have met chroma subsampling, and it is worth knowing because it explains a whole class of complaints. JPEG separates the image into brightness and colour, then stores colour at half resolution in each direction — the mode usually written as 4:2:0. This works because human vision resolves brightness far more sharply than hue, so for photographs the saving is enormous and the loss is invisible. It stops working the moment the image contains fine detail carried by colour rather than by brightness: red text on a grey background, saturated thin lines in a chart, the boundary between two colours of similar lightness. Those get visibly fuzzy while everything else stays crisp. Screenshots, diagrams and anything with coloured text belong in PNG for exactly this reason, and no quality setting fixes it because subsampling happens before quantisation.
When JPEG is the right destination, and when it is not
It helps to name the conditions, because all three have to hold. JPEG is right when the destination genuinely cannot read AVIF, when the file needs to stay small, and when the image has no transparency. Attaching a photograph to an email, filling in an upload form with a size cap, feeding an older content management system, sending something to a print shop that wants a familiar format — all of these are exactly right. It is the wrong choice when any one of those conditions fails. If the destination reads AVIF, converting only makes the file bigger or worse. If the image is a screenshot, a diagram or a logo, JPEG will blur its edges and PNG is the answer. And if you need an editable master to work on, neither JPEG nor a re-encode of any kind belongs in that role — keep the AVIF.
Photographs are the most personal file you own, and this runs locally
AVIF turns up most often as a photograph, either saved from a modern website or produced by a recent phone, and a photograph carries more than the picture. A camera file records when it was taken, on what device, and very often exactly where — latitude and longitude to a few metres, which is to say the address of a home, a school or a workplace. Uploading that to a hosted converter hands the coordinates to a third party alongside the image itself, in exchange for a transformation your browser can perform natively. Here the decode and the re-encode both happen in the page: the browser reads the AV1 frame, composites any transparency onto the colour you chose, and writes the JPEG, with metadata kept or stripped according to your setting. No request is made at any point, which the network panel of your developer tools will confirm while the batch runs.
Common mistakes to avoid
- Setting quality to 100 to avoid loss. JPEG has no lossless mode — you get a file several times larger for a difference nobody can see, which defeats the reason you chose JPEG.
- Converting a transparent AVIF without choosing a background. JPEG cannot store alpha, so the encoder fills it for you and blends the soft edges permanently into that colour.
- Using JPEG for screenshots or diagrams. Chroma subsampling stores colour at half resolution, so coloured text and thin lines smear no matter what quality you set.
- Re-exporting a JPEG instead of returning to the AVIF. Each lossy pass compounds the previous one, so always convert from the original rather than from a previous conversion.
- Forgetting the photo carries GPS coordinates. A camera file records where it was taken to within a few metres — decide deliberately whether that travels with the JPEG.
How it compares
| Feature | This tool | Typical online converters |
|---|---|---|
| Images uploaded to a server | Never — converted in your browser | Usually uploaded |
| Quality setting exposed | Yes | Sometimes |
| Choose the flatten colour | Yes | Rarely — usually white |
| Strip GPS and EXIF | Your choice | Varies |
| Image-count limit | Unlimited | Often capped on free tier |
| Price | Free | Free / paid tiers |
Features
Adjustable quality
A visible slider with a sensible default, since the right setting depends on the picture rather than the format.
Chosen flatten colour
Transparent areas are composited onto a colour you pick, not onto whatever the encoder defaults to.
Metadata control
EXIF, including capture time and GPS position, is kept or dropped according to what you choose.
Batch conversion
Add a folder of AVIFs and convert them in one pass without an upload queue.
Dimensions unchanged
Width and height stay exactly as they were — only the encoding changes.
No installation
Nothing to download or install — it runs on the web page.
Arabic and RTL friendly
Full interface in eight languages, including right-to-left Arabic.
Secure by default
Served over HTTPS, with no file tracking and no third-party upload.
Who uses it
Anyone filling an upload form
Producing a file a form will accept when it validates by extension and rejects AVIF.
Email and messaging
Sending a photograph to a recipient whose client cannot display an AVIF attachment.
Content and marketing teams
Getting an image into an older content management system that only understands JPEG.
Print shops and photo services
Handing over the familiar format that almost every print workflow still expects.
Frequently Asked Questions
AVIF (AV1 Image File Format) is a next-generation image format offering significantly better compression than JPG or PNG. It was developed by the Alliance for Open Media and is increasingly used by web browsers and CDNs.
While AVIF offers superior compression, it is not yet supported by all devices, email clients, and applications. Converting to JPG ensures your images work everywhere — on any device and in any app.
AVIF is supported in Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 85+. If your browser does not support AVIF, our tool will display a notification with upgrade options.
AVIF uses advanced compression that may not translate perfectly to JPG. Using a quality setting of 90–95 will produce JPG output visually close to the original AVIF.