When this tool is useful
Opening AVIF assets in older editors, upload forms, print services, or devices that require JPEG.
How local processing works
A local AVIF decoder reconstructs the pixels, which are then encoded into a new JPEG at the chosen quality.
How to use it
- Choose the source files.
- Review the available settings and page order.
- Process locally, inspect the result, and download it.
Important limitations
HDR range, alpha transparency, animation, and AVIF-specific efficiency may be lost in the JPEG output.
Verify the downloaded result
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
Does this tool upload my files?
No. Processing happens in your browser; closing the page clears the working session.
Will the output always match the source exactly?
HDR range, alpha transparency, animation, and AVIF-specific efficiency may be lost in the JPEG output.
What should I check before using the result?
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Which browsers and devices are supported?
Use a current browser with JavaScript, workers, canvas, WebAssembly where the format requires it, Blob downloads, and enough memory. Reopen important downloads in the destination application.
Concrete input and output example
Input a 1600×1200 AVIF at 280KB and export JPG quality 90. The 760KB output favors compatibility; HDR range, alpha, animation, and AVIF-specific metadata may not transfer.
Browser compatibility notes
Reviewed against the implementation and required web APIs on 2026-08-12. Use a current browser where these APIs are available and verify important output on your device.
- Chrome / Edge (current desktop)
- Requires local decode, canvas, encoding, Blob download, and enough memory; verify the downloaded image.
- Firefox (current desktop)
- Uses the same standard local APIs; color rendering can differ slightly from Chromium.
- Safari (current desktop)
- Uses canvas and Blob downloads; available memory and codec behavior remain WebKit-controlled.
A tool-specific question
Why can the JPG be larger than AVIF?
AVIF is often more efficient. The conversion prioritizes compatibility, and a high-quality JPEG may require more bytes for similar appearance.