JPG to AVIF Converter
Where AVIF wins over JPG
AVIF is AV1 used for stills. At comparable visual quality it runs 30-50% smaller than JPG, and unlike JPG it supports alpha, 10-bit color, and wide-gamut content. For photos served on the web, that's a meaningful bandwidth win on every single request.
- JPG (delivery)
- baseline
- AVIF (similar look)
- 30-50% smaller
- Second pass
- Stacks loss
Browser support is broad in 2026: Chrome, Firefox, Edge, Safari 16.4+, iOS 16+, and Android Chrome all render AVIF natively. For modern web delivery, it's a safe default ahead of JPG.
Transcoding JPG → AVIF without fooling yourself
The JPG already threw away frequency detail. AVIF will throw away a little more unless you crank quality high enough that bytes stop shrinking. I treat 75-85 as the practical web band when the source JPG was saved at normal camera or export quality; I go higher only when the asset is a hero or when I know another edit comes next.
- High-quality JPG in: AVIF 75-85 usually lands invisible at normal zoom.
- Low-quality JPG in: expect smaller gains — there is less signal left to compress.
- Hero or print path: bias toward 85+ or re-export from a lossless master.
When the swap isn't worth it
Older Safari below 16.4, pre-iOS-16 devices, corporate email clients, Office apps, and most Slack and Teams inline previews still don't render AVIF. Encode time is also 5-10x slower than JPG, which matters at scale if you're processing thousands of images.
For production sites, serve AVIF via a `<picture>` tag with a JPG fallback source — modern browsers take the small file, older clients get the compatible one. For one-off shares where you don't know the recipient's device, stick with JPG.
When to keep JPG
- Compatibility-first: attachments, LMS uploads, unknown viewers.
- Encode throughput: batch jobs where AVIF time dominates the pipeline.
- Already minimal: small thumbs where another codec buys almost nothing.
JPG to AVIF questions, answered
Is AVIF smaller than JPG?
At similar visual quality on photos, AVIF is often 30-50% smaller than JPG. The gain depends on content and encoder settings; a tiny or heavily compressed JPG has less room left to optimize.
Does JPG to AVIF lose quality?
Yes — it is another lossy encode on top of JPEG. At quality 75-85 the second pass is usually invisible on typical photos, but you cannot recover detail the original JPG already discarded.
What AVIF quality should I use for a JPG source?
Start around 75-85 for web delivery; AVIF quality does not match JPEG numerically. Use higher values for hero or print-adjacent output. When the JPG is already mangled, raising AVIF quality mostly spends bytes on artifacts.
Which browsers support AVIF?
Chrome, Firefox, Edge, and Safari 16.4+ decode AVIF. Email, many enterprise viewers, and older Safari do not — ship with a JPG fallback inside a picture element when you control the HTML.
When should I keep JPG instead of AVIF?
Keep JPG for maximum compatibility, faster encodes at huge scale, or destinations that reject AVIF. For one-off shares to unknown clients, JPG is still the safe default.