Questions about AVIF and WebP
Isn't AVIF the better format? Why convert backwards?
For raw compression, yes. For getting an image to display everywhere it needs to, not yet. If something in your stack refuses AVIF — an image editor, a theme, a mail client, an older Safari — the better format is the one that renders.
Will the WebP file be bigger than the AVIF?
Usually somewhat, since AVIF squeezes harder. Set a target size here and the difference stops mattering — you get the file weight you asked for, at whatever quality fits inside it.
So which should I actually publish?
AVIF where you control the whole chain and can verify it renders. WebP where the image will travel — a feed, a newsletter, a marketplace listing, a client's site running a theme you have never seen.
Are my images really not uploaded?
Correct. The conversion uses your browser's own image engine, so the file is read from your disk into the tab and never sent over the network. Open your browser's network panel and convert something — no request is made.
How does the target size work?
The converter encodes your image, checks the result against your target, and adjusts quality until it fits. If quality alone cannot get there, it reduces the dimensions in steps rather than destroying the picture. You always see what happened.
Is there a limit on how many files I can convert?
None from us — your computer does the work, not our server. The practical ceiling is around 40 megapixels per image, where browsers stop being reliable.