Convert images to WebP in your browser
This webp converter turns PNG, JPG, GIF, AVIF and BMP files into WebP, several at a time, without sending anything to a server. Drop a batch, choose lossy or lossless, and each file is converted in turn with its own size comparison and download button. The work happens on your device, using the image encoder already built into the browser.
How to use it
- Drop your images on the box, or click it and select several files.
- Choose Lossy for photographs or Lossless for graphics and screenshots.
- In lossy mode, adjust the quality slider; every file is re-encoded with the new setting.
- Check each row: the percentage tells you whether WebP actually helped for that file.
- Download the files you want to keep. The output names keep the original stem.
Convert PNG to WebP, or JPG to WebP?
The two conversions behave differently, and it is worth knowing why. A PNG is lossless, so a PNG screenshot or logo converted to lossless WebP keeps every pixel and typically drops by around a quarter. Converting that same PNG with lossy WebP can shrink it much further, but text and sharp edges may show faint halos — check the result at full size.
A JPG to WebP conversion is lossy to lossy. The JPEG already threw detail away, and a second lossy encoder throws some more away, so aim for a quality close to the original's. For a typical camera JPEG, WebP at 80 lands noticeably smaller with no visible change. Running an existing WebP back through lossy compression is the one case the tool flags: every generation adds loss, so keep the original unless the saving is large.
How lossless works here
The canvas API has no explicit "lossless" switch. What it offers is a quality value between 0 and 1, and Chromium-based browsers — Chrome, Edge, Opera, Brave — treat a WebP request at quality 1.0 as a request for true lossless encoding. That is what the lossless option sends. Other engines may give you a maximum-quality lossy file instead, which is still visually identical but not bit-exact, so use a Chromium browser when exactness matters.
WebP vs AVIF
AVIF is newer and, on photographs, often 20% smaller than WebP at the same visual quality. It is also
slower to encode and, crucially for a browser-based tool, not every browser can produce it from a
canvas. WebP is universally supported, encodes quickly and has a mature lossless mode that AVIF lacks
in practice. For most sites the pragmatic choice is WebP everywhere, with AVIF added through a
<picture> element where the extra saving justifies the work. If you want to try AVIF on a single
image, the image compressor offers it and tells you when your browser cannot
encode it.
Metadata is stripped
Because each output is rebuilt from pixels, EXIF metadata does not carry over. Camera details, timestamps and GPS coordinates are all removed, which is usually what you want for images published on the web. After converting, run your pages through the image alt checker so the new files arrive with proper descriptions.