AVIF to JPG — Batch-Convert AVIF Images to Universal JPG Online for WeChat, Email, Print and Legacy Systems, Processed Locally
AVIF is a new-generation image format launched in 2019 alongside AV1 video coding, and its compression beats WebP by a wide margin — at the same perceived quality it can be roughly half the size again, so Chrome, Firefox and Safari gradually wrote it into their web standards, and many newer phones save photos and downloaded assets as .avif by default. The trouble starts with its youth: WeChat, mail clients, older Office builds, print layout software, content management systems and a great many upload forms still recognise only JPG or PNG, and when they meet a .avif file they either show a blank box or reject it outright. This page decodes the AVIF fully in your browser and re-encodes it as JPG with a quality slider you control: higher values keep more detail and produce larger files, and around zero point eight five is usually a good balance. JPG has no alpha channel, so for icons or cut-outs with transparent areas you can pick a fill colour — it starts out white — to avoid dark fringes. Drag in several files at once, watch each one’s status and size in the batch list, step through the preview with Previous and Next to compare side by side, then download one image or pack the whole batch into a ZIP. The target-format dropdown switches to PNG or WebP at any time, and already-decoded images re-export automatically without being imported again; the whole conversion runs locally in your browser and no image is ever uploaded.
Import images
Target format
All three formats reuse the same decoded pixels, so switching re-exports automatically — no need to import again.
JPG is the most compatible and usually the smallest. Ideal for messaging, email, printing and older systems; it cannot store transparency.
Higher values keep more detail and produce larger files. Around 0.85 suits photos; push it higher for screenshots.
JPG has no alpha channel, so transparent and semi-transparent areas are filled with this colour. It starts out white, and you can change it to any colour.
A few AVIF files carry an orientation flag and decode sideways. Correct them here.
Leave it empty to keep the original name; the extension is replaced with the output format.
Preview and export
Batch list
0 / 0 DoneNo images imported yet.
How to use
- Drag .avif images into the import area, or click Choose images to select several at once; Ctrl+V pastes a screenshot too. The tool identifies the real format from the file header, so a wrong extension does not matter.
- Keep the target format on JPG and start with quality around zero point eight five to see the file size, then nudge it either way: push a photo too hard and the sky bands; for text screenshots, watch whether strokes go soft.
- If the source has transparent areas, choose a background colour in Transparency fill; a few AVIF files carry an orientation flag and decode sideways, so correct those with Extra rotation.
- Use Previous and Next in the preview to check both panes image by image, then download the current one, download individual rows from the batch list, or pack everything into a ZIP. Changing the dropdown re-exports the already-decoded images automatically.
Frequently asked questions
Why will an AVIF image not open in some programs?
AVIF was only finalised in 2019, nearly three decades after JPG, and browsers took several generations to complete support, while plenty of desktop programs, older Office builds, print layout systems, content management back ends and upload forms still read only JPG and PNG. The file is not damaged; the program on the other side simply has no AVIF decoder. A JPG depends on nothing installed on the system, opens on any computer you copy it to, and is the least troublesome thing to hand to a print shop or upload to a form.
Does converting to JPG lose quality a second time?
It does, though usually invisibly. A lossy AVIF has already been compressed once, and decoding to pixels before re-encoding with a JPG quantisation table is a second lossy pass; sky gradients and high-contrast edges are the likeliest places to show faint banding or ringing. Above quality zero point eight five it is essentially imperceptible at normal viewing sizes, and if you want later edits to cause no further loss at all, use the PNG page, which stores the decoded pixels losslessly — while understanding that it cannot bring back what the first compression discarded.
What happens to a transparent background?
JPG has no alpha channel, so transparent and semi-transparent areas must be composited onto a solid colour — it starts out white, and you can change it to any colour in Transparency fill. For a cut-out product shot or a rounded logo, pick the colour of the page it will sit on, otherwise a white halo appears on a dark background. Switch to PNG or WebP if you need to keep transparency, since both support a full alpha channel.
My phone saved a photo as AVIF. How do I send it to someone?
Some phones and messaging apps store or transcode images to AVIF to save data, and the recipient may see a blank box if they use an older WeChat, mail client or image viewer. The most dependable move is to convert it to JPG here first, then send or upload it — the other person can open it on any device. The whole process runs locally in the browser, and no image ever touches a server.
Are my images uploaded to a server?
No. Decoding, orientation correction, quality adjustment and encoding all happen in the browser, AVIF pixels are unpacked by the browser itself, image data never leaves your device and the page has no upload endpoint. Once it has loaded you can even keep converting offline. The flip side is that the list is gone when you close the tab, so keep your own backup of important originals; the output is a brand-new file and no EXIF shooting data is carried over.
What is it
The difference between AVIF and JPG is not which looks sharper, but the gap in the years they were designed. AVIF is an image format Netflix released in 2019 with several partners, built on AV1 intra-frame video coding and packed into a High Efficiency Image File Format container; one specification offers lossy, lossless, an alpha channel and animation. Its lossy mode splits the picture into blocks, predicts each block’s pixels from its neighbours and records only the residual with adaptive quantisation, which is why it is often half the size of a JPG at the same quality and can beat WebP by another notch. JPG is an older standard settled in 1992: it splits the picture into eight-by-eight blocks, applies the discrete cosine transform and discards high-frequency coefficients through a quantisation table, and commonly halves colour resolution with four-two-zero chroma subsampling. Converting to JPG means the browser first unpacks the AVIF into full pixels and then runs blocking, transform and quantisation once more, an irreversible second round of loss: detail the source already discarded never returns, and sky gradients or high-contrast edges are the first to show banding or ringing. The quality slider controls that quantisation table, and setting it to one keeps the most detail but noticeably enlarges the file. An AVIF with alpha is composited onto the chosen background first, because JPG has no transparency dimension at all; EXIF, ICC and animation frames in the container do not come along either, and a multi-frame AVIF contributes only its first frame. The tool identifies the real format from the file header, so a wrong extension does not matter.
Origin & history
Lay the timeline out and two formats nearly thirty years apart meet on the same machine. JPG comes first: in 1992 the JPEG standard was published jointly by ISO and ITU, using the discrete cosine transform and quantisation tables to squeeze a photograph into a few tens of KB, and around 1994 JFIF spread until virtually every program could read it; the core barely changed over the next three decades, at the cost of eight-bit depth, no transparency and visible blocking at high compression. The other strand begins in February 2019: Netflix, together with Google, Amazon, Microsoft, Cisco and others, released AVIF, built on the open AV1 video codec and packed into a HEIF container, borrowing the high compression of video intra-coding for still images. The first version already offered lossy, lossless, alpha and animation, and libavif was adopted by Chromium, Firefox, Safari and a great many server-side toolchains. Then came the slow rollout: Chrome supported it by the end of that year, Firefox only caught up in 2021, and Safari completed the set in 2024, so picture elements and server-side content negotiation by request header were effectively mandatory, with several assets to maintain per page. The interesting twist is that once AVIF spread, the trouble moved from inside the web to outside it: design software, older Office builds, print workflows, content management systems and upload forms long recognised only JPG or PNG, and the growing pile of .avif files in site directories could barely take a step beyond the browser. The real solution needed no new algorithm: canvas toBlob had long accepted image/jpeg with a quality argument, so the encoding side was never the obstacle, and once browsers could unpack AVIF pixels natively, local decoding plus local re-encoding became the most dependable combination — one that does not even need an upload endpoint. Today a single click converts the file; what looks like merely skipping one upload is in fact handing a piece of computation that should have stayed local back to the local device.Today phones and messaging apps often store or transcode images to AVIF to save data, and cases where the recipient cannot open them keep rising, which makes local conversion the most practical fallback.
Related keywords
Feedback
Found a problem with a tool or have a suggestion? Email us — we read every message.
