How it works
- Drop your JPG files here, or select a whole folder.
- Each JPG is decoded and re-encoded as AVIF — right in your browser.
- Adjust the quality slider; expect encoding to take a little longer than JPG or WebP.
- Download the AVIF files individually, or as one ZIP.
AVIF typically beats JPG (JPEG) by a wide margin on file size at the same visual quality, which makes it worth the switch for photos headed to a website. Worth knowing honestly: this is a lossy-to-lossy re-encode — the JPG's compression already happened once, and AVIF encoding adds a second generation on top of it. If a higher-quality original (RAW, HEIC, or an uncompressed export) still exists, encoding to AVIF from that source instead will always look better than going through JPG first. This tool converts entirely in your browser, no upload, and AVIF encoding does take a bit longer than JPG.
Why use convert.pics?
- Typically much smaller than the JPG at a visually comparable quality.
- No upload: the whole re-encode happens locally, however many photos you have.
- Batch conversion for a whole folder of website images at once.
- Quality slider gives full control over the size-versus-fidelity tradeoff.
Frequently asked questions
How much smaller is AVIF than JPG at the same quality?
Often 40-50% smaller for photographic content, based on independent codec comparisons — though the exact figure varies a lot by image content and the quality setting used on both sides.
Is AVIF better than WebP?
For file size at equivalent quality, AVIF usually edges out WebP, sometimes significantly. WebP has the advantage of slightly wider software support and much faster encoding, which matters for very large batches.
Does re-encoding a JPG to AVIF lose quality twice?
Yes — this is a second lossy generation on top of whatever the JPG already lost. If a better-quality original still exists (RAW, HEIC, or an uncompressed export), encoding to AVIF directly from that will look better than going through JPG.
What quality setting should I use for AVIF?
The default (82) is a reasonable starting point and usually looks visually identical to the source. For a second-generation JPG-to-AVIF conversion specifically, nudging the quality up slightly helps offset the earlier compression.