WebP is what a web page wants: a quarter to a third smaller than a JPEG at the same visible quality, with the transparency a PNG has. This writes one with your browser's own encoder and tells you the saving in bytes, because a conversion that does not measure itself cannot say whether it was worth doing.
What it does
Decodes the picture with your browser's own codec and asks the same browser to encode it as WebP at the quality you chose. Transparency is kept: WebP has an alpha channel, so a PNG logo on nothing stays on nothing.
Where it does not work
Safari's canvas cannot write WebP as of this writing; asked to, it quietly writes a PNG instead. This tool checks the bytes that came back and refuses rather than naming a PNG .webp — the file would be rejected by whatever wanted a WebP, later, with no explanation. Chrome, Edge and Firefox on any system, including a Mac, write it.
The quality choices are named, not numbered
Best for pictures people will look at closely, Balanced for a page, Small for a thumbnail. The size each produced is shown next to the result, which is the feedback a slider never gives.
What is left in the file
Nothing but the pixels. Metadata the source carried is stripped.
Page weight. A WebP is typically 25–35% smaller than a JPEG of the same visible quality and far smaller than a PNG, and every current browser displays it. For a picture on a web page that is the whole argument; for a picture going to a printer, an email or a form, it is not, and the PNG or JPG is the better file to send.
Is the transparency kept?
Yes. WebP has an alpha channel like PNG, so nothing has to be painted underneath and there is no background colour to choose on this page.
Why does it refuse in Safari?
Because Safari's canvas cannot encode WebP; asked to, it hands back a PNG. Rather than name that file .webp and let you find out when a site rejects it, the tool checks the format of the bytes it received and stops. The same picture converts in Chrome, Edge or Firefox on the same machine.
Is my picture uploaded?
No. Decoding and encoding both happen in this browser tab, and the site has no endpoint that could receive a file.
We count page views with our own analytics, which sets no cookie and stores no analytics identifier in this browser. Your choice below is about advertising: if it is switched on here, our partners may store and read information on your device. How we use it