Frequently Asked Questions

Yes, and here's why. There's no upload step. The file you drop in gets read and converted by JavaScript running in your own browser, so it never reaches us — we don't run a server that could store it or even look at it. You can confirm this yourself: open your browser's Network tab before you convert, and you'll see no image leaving the page.

Usually it means the original was already squeezed hard. Take a JPEG that was saved at 30% quality, re-encode it as WebP at 100%, and you're asking the encoder to faithfully keep every compression artifact — which can cost more bytes than it saves. Pull the quality slider down to around 75–80 and it'll almost always come out smaller. The savings figure under the tool flags this the moment it happens.

No — it's just the single converter on the home page, one file at a time. There's no API or batch mode, which is really a side effect of running everything in the browser. If you need to process a whole folder or wire conversion into a build step, you're better off scripting it on the server; our walkthrough on serving WebP with PHP does it in a few lines of GD code.

Yes — personal projects, client work, commercial sites, all fine, and there's no charge. If you're optimizing images for a store you run or a CMS you manage for someone else, go right ahead.

There's no fixed cap, because no server is sitting there enforcing one. The real ceiling is your device's memory, since the whole image gets loaded and redrawn locally. A modern laptop handles a 50 MB photo without blinking. An older phone might stall for a second or two on a huge print-resolution file — if that happens, shrink it first with the percentage field.

They do. WebP carries an alpha channel, the same thing that makes PNG transparency work. Drop in a logo with a see-through background and the WebP keeps it — usually at a fraction of the original file size.

For most web images — blog photos, product shots, banners — 80 is a sensible default, which is why it's set there to start. Go below about 75 and you'll start seeing mushiness in fine detail. Push above 90 and the file grows for quality most people won't spot on a screen. When an image really matters, convert it twice at different settings and compare them side by side before you commit.

For practical purposes, yes. Every current browser handles it — Chrome, Firefox, Edge, Opera, and Safari, which was the last holdout until it added support back in 2020. The only place you'd hit trouble is something ancient like Internet Explorer, and if you genuinely need to cover that, serve a JPEG fallback using the <picture> element.