How to Use This Tool
WebP reaches the same visual quality as PNG or JPEG at roughly a third of the size, and every browser released in the last six years supports it. For a page carrying a dozen images that is often the single largest performance win available, and it takes about ten seconds.
Converting
Drop one file or fifty. Each is decoded, redrawn to a canvas and re-encoded as WebP entirely inside your browser — there is no upload, no queue and no size limit beyond your own memory. Move the quality slider and every file re-encodes live, so you can watch the size fall and stop when it starts to look wrong.
Transparency is preserved. A PNG with an alpha channel becomes a WebP with an alpha channel, which is one of the main reasons to choose WebP over JPEG for logos, icons and cut-out product shots.
Choosing a quality setting
Between 75 and 85 is where almost every image should sit. Below about 70 the artefacts become visible on photographs; above 85 the file grows quickly for a difference nobody can see without pixel-peeping. The default of 80 is a good starting point for photographs. For screenshots and flat-colour graphics you can often go lower than you expect, because there is less detail for the encoder to lose.
Lossless mode
Ticking lossless produces a file with pixel-for-pixel identical output, and it still beats PNG by roughly 25 to 35% because WebP's compression is simply better. Use it for line art, diagrams, screenshots containing text, and anything that will be edited again later. For photographs it is rarely worth the size; quality 80 will be four times smaller and indistinguishable.
The skip option
Skip files WebP would make bigger is ticked by default and worth leaving on. Very small images — icons under a couple of kilobytes, simple two-colour PNGs — sometimes come out larger as WebP because the format's header overhead exceeds what it saves. Rather than silently handing you a worse file, the tool flags those and keeps the original.
Where you can safely use the output
WebP works in every version of Chrome, Firefox, Edge and Safari since 2020, which is effectively all real traffic. The remaining gaps are older desktop software rather than browsers: some email clients, some CMS uploaders and a few print workflows still reject it. If a system refuses your file, that is why, and the fix is to keep a JPEG fallback rather than to avoid WebP everywhere.
