JPG to AVIF Details
This page is a single-purpose converter: it rewrites JPG files as AVIF. Drop a file in, run the conversion, take the download.
JPG is the long-standing photo format: lossy compression, no transparency, and support in every viewer worth mentioning. AVIF is the still-image half of the AV1 codec and holds detail well even at low bitrates.
The workflow
If this is your first visit, here is how it behaves.
- Drag your JPG files onto the upload area, or click it and pick them from the file dialog.
- Each queued file shows its name and size. Remove what you do not need; one round handles 20 files at most.
- Use the convert button on a single row, or the batch button to run the whole queue at once.
- Rename the output in the queue field before downloading; the extension is set to AVIF for you.
- Click the download link on the finished row and the AVIF file lands on your device.
Technical details
A few details that make the decision easier:
- Accepted input: JPG (jpg, jpeg), up to 24 MB per file.
- The result is written as AVIF and encoded at quality 60, which is why the file shrinks so much.
- The queue carries 20 files at a time, and each file travels in its own request.
- JPG files have no transparency to begin with, so the AVIF result is opaque; an alpha channel is never invented.
- Both sides are lossy, which means the image is encoded once more. Avoid converting the same file back and forth.
- Do not count on metadata surviving: whether EXIF and ICC data travel depends on the engine handling the file, so keep anything critical elsewhere.
Picking the right tool
This conversion earns its place when an existing JPG file has to land somewhere that asks for AVIF. Hero images, high-resolution photography and pages that pay attention to mobile data cost benefit most. It usually lands smaller than WebP at matching quality, but encoding is slower and old software support is thin. JPG is the long-standing photo format: lossy compression, no transparency, and support in every viewer worth mentioning.
AVIF gives you the smallest file when page speed is the priority. If the file has to open in older software, WebP or JPG output is the safer call.
Small things that help
- Filling the queue with 20 files and hitting convert all is faster than working through them one by one.
- Renaming outputs in the queue keeps your downloads folder readable once several AVIF files land there.
- AVIF is encoded with loss, so converting the same file repeatedly costs quality. Keep the original.
- Open the AVIF file afterwards and check edges and colour gradients, and keep the JPG source where it is.
Where your data is processed
Your file travels over HTTPS, is processed during that single request and comes back as the download itself. It is never written to a public directory, nothing is kept once the response is sent, and the download is marked as non-cacheable.