Convert WebP to AVIF to squeeze web images down further. AVIF usually produces the smallest file at a similar quality. Transparency and animation both carry over, so you rarely give anything up on the move.
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · max 30 MB
Auto tunes each image.
A hard cap for “under 50 KB” portals.
Empty side keeps the ratio. Never enlarges.
WebP · 229 KB
AVIF · 67 KBBecause AVIF is the same idea, one codec generation later: typically 15–40% smaller at equal visual quality. If WebP was your site's big win in 2020, AVIF is the same win again in 2026. Same images, same one-line fallback pattern. The pages that repay it first are the ones in your Largest Contentful Paint path: heroes, galleries, product photography.
| Encode | Size | vs source WebP |
|---|---|---|
| AVIF (Auto) | 68.7 KB | −71% |
| AVIF (quality 45) | 48.2 KB | −79% |
Source: photo.webp, 234.9 KB. The equivalence row explains the trap of re-encoding at too-high quality.
One quality-scale warning that explains most "AVIF made my file bigger" complaints: the scales are not aligned across formats. On the same photograph, AVIF at quality 60 measured 114.7 KB while AVIF at quality 80 measured 164.1 KB. That is near-double the bytes for near-identical appearance. Encode AVIF in the 50–65 band (Auto does), not at the 80–90 numbers you learned from JPEG.
How these numbers are measured: every byte count on this page is the size of the actual encoded file our engine produced from the named source image. Those are the same bytes you would download, not an estimate or a best case. Rerun any of them yourself: drop your own file into the tool above and the meter reports your real result.
It compounds two generations of loss. That is real, and nobody ranking for this query says so. In practice, one careful re-encode at Auto quality is visually clean. What degrades images is repeated cycling through formats and qualities. Two honest rules: if the original PNG or camera file still exists, encode the AVIF from that (one generation instead of two), and verify the result in the compare slider at 100% before replacing anything. Fine texture and skin gradients show compounding first.
<picture> <source srcset="hero.avif" type="image/avif" /> <source srcset="hero.webp" type="image/webp" /> <img src="hero.jpg" alt="…" /> </picture>
About 95% of visitors receive the AVIF. The rest fall through to WebP (~97% support) or the JPG. WordPress 6.5+ and Shopify's CDN both handle AVIF natively. No plugin gymnastics required anymore.
Coming the other way? AVIF to WebP exists for exactly those platforms.
Short answers specific to this page. The tool above settles most of them in a second.
Every route in and out runs on the same engine and the same rules. Each card is its own page.
Roughly half the bytes of WebP on most photos. Slower to encode, worth it at scale.
Transparency survives and size collapses. Check thin type and 1px strokes in the preview first.
The universal handoff. Anything that opens an image opens this: print, email, old software.
Keeps transparency for editors and pipelines that won't read WebP. Bigger file, no further loss.
When something rejects the upload, this is the format it wants. Photos only, no transparency.
Keeps alpha and gives every editor something to open. Expect a large file. That's the trade.
Drop it in above. The meter reports the exact saving before you download anything.