JPG to AVIF
Turn a JPG into a smaller AVIF.
AVIF is among the most efficient picture formats. Drop JPG files, choose the quality, and save AVIF files made on your device.
AVIF is made by a converter built into this page, so it works the same in every browser.
Drop a photo here.
Drop a photo here.Choose a photo.
HEICJPGPNGWEBPNothing leaves this device.
Several files of one kind convert together.
How it works
Drop, set the quality, save.
1
Drop the JPG files
PNG, WebP and HEIC are read too, where your browser opens them.
2
AVIF is selected
Custom opens on AVIF at full size and Great quality, 82 percent, scaled internally so the picture quality matches JPG at the same setting. Good and Best are one move away.
3
Save
AVIF files, or one ZIP. Large pictures take a few seconds each.
Measured examples
Smaller, but slow to make.
AVIF is the slowest format here to write. We timed three generated pictures at the page's setting, Great quality.
| Test file | Size | Change | Time | Result |
|---|---|---|---|---|
| Detailed photo, 12 MPChrome | 2.5 MB → 1.4 MB | 44 percent smaller | 3.9 s | 31.4 dB likeness · 4000 × 3000 · Location removed |
| Detailed photo, 12 MPWebKit | 2.5 MB → 1.4 MB | 44 percent smaller | 5.4 s | 31.4 dB likeness · 4000 × 3000 · Location removed |
| Smooth gradients, 12 MPChrome | 243 kB → 21 kB | 92 percent smaller | 1.2 s | 51.5 dB likeness · 4000 × 3000 · Location removed |
| App screenshot, 2400 by 1600Chrome | 162 kB → 41 kB | 75 percent smaller | 560 ms | 47.5 dB likeness · 2400 × 1600 |
Measured on November 7, 2026 in Google Chrome 157, WebKit (Playwright build, not Safari) 26, on Apple M1 Pro. Times run from pressing Convert to the result being ready, with the page already loaded. Likeness is PSNR against the original: higher is closer, and above 40 dB the difference is hard to see. WebKit here is Playwright's build, which is not Safari. Every test file was generated for these measurements, none is anyone else's work, and each is described on the About page.
The detailed 12-megapixel photo went from 2.5 MB to 1.4 MB in 3.9 seconds in Chrome and 5.4 in WebKit. The smooth picture went from 243 kB to 21 kB, a saving of 92 percent, and the screenshot saved 75 percent. Smooth areas are where AVIF wins most.
Facts
What AVIF changes.
Quality number
The number is scaled for AVIF: 82 is written at about 74, tuned to match the look of a JPG at 82.
Tags and location
Not written. The test photos carried GPS, make, model and capture date; none is in the AVIF.
Largest picture
About 35 bytes of memory per pixel while encoding. Pictures over 48 megapixels are scaled down first and the name gets a size suffix.
Who can open it
Current browsers show AVIF. Many upload forms, social networks and email clients do not accept it yet.
Good to know
What AVIF is good for.
AVIF compresses harder than JPG and WebP, at the price of time and compatibility.
How much smaller
AVIF is often much smaller than JPG at a similar look, with the largest wins on smooth skies and gradients, as the table shows. Textured photographs save less. The catch is that a JPG was already compressed once, so for the best result start from the original file.
Time it takes
AVIF is slow to encode. A 12-megapixel photo took 3.9 seconds in Chrome and 5.4 in WebKit, the engine behind Safari. We use a fast setting that costs a little size for a lot of time.
Very large pictures
Memory is about 35 bytes per pixel during encoding. A 100-megapixel picture ran out of memory in our tests, so anything above 48 megapixels is scaled down first, and the file name gets a size suffix such as -7000px.
Where AVIF is not welcome
Current browsers show AVIF, but many upload forms, social networks, email clients and older programs do not accept it. Check where the picture is going. If it is refused, JPG or WebP are the fallbacks. Metadata, including location, is not written.
The quality number is adjusted
A quality number does not mean the same thing in every format. AVIF at the same raw number as JPG would give a much larger file, so the quality is scaled down for AVIF: 82 is written at about 74, which we tuned to match the look of the JPG at 82. If a result is bigger than you want, choose Good rather than switching format.
If something goes wrong
When it does not work.
AVIF fails at the edges of a workflow, not in the encoder.
The site rejects the AVIF
Why: The destination only takes JPG, PNG or WebP.
What to do: Keep the JPG, or convert to WebP on the PNG to WebP page.
The tab is slow while it converts
Why: AVIF needs far more computation than JPG: 3.9 seconds for one 12-megapixel photo here. The work runs in the background, so the page stays usable.
What to do: Convert large batches one folder at a time and leave the tab open.
The AVIF looks worse than the JPG
Why: The JPG was compressed once already and AVIF compresses it again.
What to do: Start from the original file, or the best JPG you have, and keep quality at 82 or higher.