Why We Built a Private Online JPG to AVIF Converter
JPGtoAVIF.com exists to make a modern image format available through a straightforward browser workflow. Many image conversion sites begin with an upload, which is unnecessary for a task that current browsers and WebAssembly can perform locally. Our converter keeps source images on the device while still supporting useful production controls.
The first screen is the actual tool, not a marketing gate. You can add files, select a folder, adjust AVIF quality, choose maximum dimensions, follow per-file progress, and download either individual results or one ZIP without creating an account.
How Browser-Based JPG, PNG, and WebP to AVIF Conversion Works
The browser decodes supported source files into an RGBA pixel buffer. A dedicated worker runs the jSquash AVIF WebAssembly encoder so the page remains responsive, then exposes the resulting AVIF blob through a local download URL. ZIP creation also happens inside the browser.
The converter intentionally processes one image at a time. Sequential encoding reduces peak memory use and allows a failed file to be reported without ending the rest of the batch. Source files are never modified.
- JPG, JPEG, PNG, WebP, and BMP still-image input
- AVIF lossy and lossless output
- Quality, speed, and resize controls
- Folder-aware ZIP downloads
- No account and no image upload
Open-Source AVIF Encoder for Local Image Conversion
The interface and workflow were informed by gitcobra's MIT-licensed avif2jpeg project, especially its file, folder, drag-and-drop, settings, progress, and ZIP concepts. The target direction is different: this project uses a real AVIF encoder rather than relying on browser Canvas output support.
AVIF encoding is powered by the Apache-2.0-licensed @jsquash/avif package, derived from the Squoosh project and libavif. Links to both projects remain in the footer so the technical foundation is inspectable.
How to Report a JPG to AVIF Converter Problem
Useful reports include the page URL, browser and version, device type, source format, image dimensions, selected settings, and the exact visible error. Do not attach a sensitive source image unless you are comfortable sharing it by email; the website itself does not receive converter files.
Compatibility and encoder behavior can change as browsers and codecs evolve. Reproducible reports help distinguish a damaged source file, browser decoding limitation, memory constraint, and application defect.