filetity

AVIF -> WEBP · Local tool

AVIF to WebP

Turn AVIF images into WebP, which more tools and older browsers accept.

Last updated

  1. 01 / Your device

    the file stays here

  2. 02 / Browser memory

    the work runs locally

  3. 03 / Back to you

    saved on this device

When you would use this

Situations, not settings.

A content system that rejects AVIF
WordPress, Shopify and most image hosts accepted WebP years ago and are still catching up on AVIF.
A site that has not moved to AVIF yet
If the templates already serve WebP, matching that is less work than adding a second format to the pipeline.
An image library standardising on one format
Carrying both means every consumer has to handle both. Picking the more widely read one removes the problem.

How it works / no cloud

A conversion engine, not an upload form.

Your browser decodes AVIF and encodes WebP, so filetity reads the image and re-encodes it at the quality you choose, carrying the alpha channel across. No engine download and no upload.

  • Offline ready
  • Installable app
  • No file limit queue

Straight answers

No accordion. Nothing hidden.

Is it free?
Yes, with no watermark and no page limit.
Does it need an account?
No. There is no account system.
Is my file processed on my device?
Yes. The file is read by your browser and never uploaded. There is no server to send it to.
What formats are supported?
AVIF in. WebP out, one file per image, or a ZIP when you convert several.
What are the limits?
No image count limit. Both formats can hold an image sequence and the browser's encoder writes a single frame, so an animated AVIF comes back as a still of its first frame. Transparency is kept.
Does it work on mobile?
Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
Does it work offline?
Yes, once the page has loaded. The tool keeps working with no network connection.
Why convert between two modern formats?
Because support for them is not the same. WebP has been in every browser since 2020 and is accepted by most content systems, image hosts and upload forms. AVIF arrived later, and plenty of those still turn it away. The picture does not get better on the way across; it just gets somewhere it is allowed in.
What does this cost in quality?
A little. Two lossy formats in a row means a second approximation, and AVIF is the better compressor, so matching what it stored takes more bytes in WebP. Raising the setting reduces the loss and increases the size.
What about an animated AVIF?
You get a still of its first frame. Both formats can carry a sequence, but the encoder built into your browser writes one frame and cannot be asked for more. Keep the AVIF if the motion matters.
Is transparency carried over?
Yes. Both formats have a real alpha channel, so see-through areas stay see-through, with no white painted underneath.

Keep working locally

4 available · more coming