What people mean by “convert WebP”
WebP is Google’s image format, and by now it is everywhere: it is what most content management systems emit, what image CDNs serve, and what your browser hands you when you save a picture from a modern site. That ubiquity is exactly why so many people need to convert WebP, and they arrive wanting one of two opposite things.
Some already have a WebP file and need something that will open it. They want to convert WebP to PNG, or convert WebP into JPG, because the software in front of them refuses the format outright — an older Photoshop release, a print shop’s upload form, a government portal, a photo kiosk, a CMS with a strict allow-list. Others are going the other direction, turning photographs and graphics into WebP to make a website load faster.
This page does both. Drop your files in, choose the output format, and the work happens inside your own browser tab. Nothing is uploaded, there is no account, and there is no cap on how many files you convert or how large they are.
How to convert WebP to JPG
There are four steps, and none of them involve an upload.
-
Drag your
.webpfiles onto the box at the top of this page, or click it to browse. You can also paste an image straight from the clipboard, or drop a whole folder at once. - Set the output format to JPG. Every file in the queue follows that setting, so a batch of two hundred images needs it set once.
- Adjust quality if you want to. The default of 82 is a good balance; push it to 90 or above when you want the re-encode to be effectively invisible.
- Press Convert, then download the results individually or take the whole batch as a single ZIP.
That is the entire process to convert a WebP file to JPG. It is the same four steps whether you have one image or a thousand, the same steps to convert WebP to JPEG — JPG and JPEG are one format with two spellings — and the same steps if you want PNG instead. Only the format button changes. Because the encoder runs on your own machine, converting online here costs nothing, works offline once the page has loaded, and never puts your photographs on someone else’s server.
Convert WebP to PNG, or convert WebP into JPEG?
The two destinations solve different problems, and picking the wrong one is the most common mistake people make here.
Choose PNG when the image has transparency, or when it contains text, screenshots, logos, diagrams or any large areas of flat colour. PNG is lossless, so it stores every pixel exactly and keeps hard edges crisp. The catch is size: converting a lossy WebP into PNG routinely produces a file five to ten times larger, because PNG has to faithfully record the compression artifacts the WebP introduced, and noise is precisely what lossless compression handles worst.
Choose JPG — or JPEG, which is the same format under a shorter, MS-DOS-era spelling — when the image is a photograph and you want a small file that opens absolutely anywhere. JPEG has been universally supported for three decades. It has no alpha channel, though, so any transparency is composited onto a solid background.
One expectation worth setting plainly: converting back from WebP cannot restore quality that lossy compression already discarded. Whichever format you pick, you are preserving the image as it stands now, not recovering the original.
Converting the other way — PNG, JPG and HEIC to WebP
Most people who convert to WebP are doing it for page speed. The savings are real: a typical photograph converted from JPEG comes out 25–50% smaller at a quality most viewers cannot distinguish, and a PNG logo or screenshot converted in lossless mode is usually around 26% smaller with every pixel identical.
The converter reads JPG, JPEG, PNG, GIF, BMP, TIFF, AVIF, SVG and HEIC. That last one matters more than it sounds: iPhones have shot HEIC by default since iOS 11, and no browser can open it natively, so a photo that looks fine on your phone is unopenable nearly everywhere else. It is decoded here in the page, with no app to install.
Why convert WebP here rather than anywhere else
Nearly every browser-based converter is a thin wrapper around one
canvas.toBlob() call. That gives you a single quality slider,
no lossless mode, and — the part people discover the hard way — no WebP
encoding at all in Safari, which has never supported it. Converters built
that way quietly fail on every iPhone and Mac.
This one ships libwebp itself, compiled to WebAssembly: the same encoder Google publishes and Squoosh uses. That is what makes true lossless mode, alpha quality, a 0–6 effort dial and byte-exact file size targeting possible, and it is why the tool behaves identically on an iPhone and on a desktop.
It also means no server is involved. Your images are decoded, resized and encoded inside the tab, so there is no upload endpoint to send them to even in principle. Open your browser’s Network tab while converting and you will see the encoder load once and then nothing. Turn your Wi-Fi off after the page loads and it still works. EXIF metadata, including the GPS coordinates phones write into photographs, is stripped by default.
Free, with nothing held back
Free here means free: no account, no watermark, no daily quota, no file that is too big and no batch that is too long, and no paid tier where the useful settings live. Conversion runs on your hardware rather than ours, so it genuinely costs nothing per image — which is the only reason a promise like that is possible to keep.