Convert WebP to AVIF.
WebP re-encoded to smaller AVIF — right in your browser.
Drop WebP files here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Convert WebP images to AVIF right in your browser — re-encoded locally, never uploaded. WebP was the web’s efficiency upgrade of the 2010s; AVIF is the same step taken again. Stills typically come out 20–40% smaller at matching visual quality, transparency included.
How it works
- Drop files anywhere on the page, click to browse, or paste with ⌘V.
- Pick a quality or preset — or set an exact target size and let the tool find it.
- Compress, compare before/after, and download — individually or as a ZIP.
One generation newer
AVIF’s AV1-based compression outperforms WebP’s VP8 roots on nearly every image type — smoother gradients, cleaner detail at low quality, tighter files. The gap is biggest on photographic content and high-quality sources. Both formats enjoy universal current-browser support, so for the web this conversion is almost pure savings; Compress WebP is the tool when the file must stay WebP.
Animated WebP: first frame only
AVIF output here is still-image only — an animated WebP converts to a single AVIF of its first frame, and the tool warns when that happens. To shrink an animation while keeping it moving, run it through Compress WebP instead, which re-encodes animated WebP natively.
Frequently asked questions
How much smaller is AVIF than WebP?
Typically 20–40% at the same visual quality for stills — a smaller jump than from JPG, but real. High-quality sources gain the most.
What happens to animated WebP?
Only the first frame is kept — AVIF output is still-image only, and a warning tells you when an animation was flattened. Keep animations in WebP instead.
Is transparency preserved?
Yes — both formats carry a full alpha channel, so see-through regions survive the conversion exactly.
Do my files leave my device?
No — the pixels never leave your machine. Decoding and re-encoding both happen in your browser; there is no upload to wait for and no server-side copy to worry about afterwards. Want proof? Run one file through, switch your connection off, and run another — it still works.