Convert JPG images to AVIF for much smaller files
Drag and drop your files here
or browse your device
Files are deleted automatically. Downloads expire after 10 minutes.
If you are optimising a website or just tired of photos eating storage, AVIF is the format worth knowing about. It uses the same compression family as modern video codecs, and in practice that means a picture saved as AVIF is frequently around half the size of the equivalent JPG at a visually similar quality, sometimes better than that. For anyone watching page-load times, that is a large saving spread across every image on a page.
This tool re-encodes each JPG as AVIF at the quality you choose. AVIF's quality scale is not the same as JPEG's, so the default sits at 55, a setting that looks clean for photographs while still delivering most of the size reduction. Nudge it higher if you want to be conservative with detail, or lower if shaving every last kilobyte is the priority. Because your source is already a JPG that has been compressed once, there is no benefit to pushing the quality to the maximum.
On a real website the saving compounds. A gallery or product page might carry twenty or thirty images, and trimming each one to around half its weight can shave a second or more off the time the page needs to become usable, which search engines and visitors both notice. The common pattern is to serve AVIF to browsers that accept it while keeping a JPG fallback in the markup for the rest, so nobody is left looking at a blank space. The one practical cost is that AVIF takes longer to encode than a JPG, a few extra moments per image, which is why it is a job you do once at publish time rather than on the fly.
Every current major browser now displays AVIF, so for the web it is a safe modern choice, ideally offered alongside a JPG fallback for the small number of older clients still in use. Outside the browser, support is thinner, so if a file is destined for an old desktop viewer or a print workflow, JPG or PNG remains the more dependable pick. The JPG to WebP route is a useful middle ground, trading a little of AVIF's efficiency for even broader compatibility.
If you ever need to go back, AVIF to JPG converts straight back, and PNG to AVIF does the same job for PNG sources.
Add a single photo or a whole folder's worth.
55 is a sound default for AVIF. Raise it to guard fine detail, lower it to squeeze the file harder.
One photo returns on its own; a batch is zipped with the original filenames.
For most photographs you can expect roughly half the size at a comparable quality, and often more. The exact figure depends on the picture, but the saving is large enough that it is the main reason people switch image-heavy pages to AVIF.
AVIF measures quality on a different scale than JPEG, so its numbers aren't directly comparable. A setting of 55 already looks clean for photos while keeping files small. Pushing it toward 100 mostly inflates the file for detail your already-compressed JPG no longer holds.
Every current major browser supports it, so on the modern web it is reliable, especially with a JPG fallback for older visitors. Support is patchier in desktop apps and print tools, so keep a JPG or PNG for those uses.
It still reduces the file size meaningfully, but converting cannot recover detail the JPG already lost. You are repackaging the existing picture into a more efficient format, not improving it.
No. The JPGs you upload and the AVIFs that come out are purged automatically within minutes of the job finishing, so nothing lingers on the server and nobody reviews your images.