How to Convert WebP to PNG (Without an Account or Upload)
You right-clicked an image in Chrome, picked Save image as…, and ended up with a .webp file. Then you tried to drop it into Word, an old version of Photoshop, an Etsy listing, or some upload form, and it bounced. WebP is now Google's default for the open web, but the rest of your software stack hasn't always caught up.
The fix is a one-step conversion. WebP and PNG are both lossless on the way in (or near-lossless), so converting from WebP to PNG doesn't degrade quality — it just gives you a file the rest of your software actually likes.
What WebP is, briefly
WebP is Google's image format. The lossy variant uses VP8 video compression (about 25–35% smaller than JPG at the same quality); the lossless variant beats PNG by roughly 25%. Browsers ship with native WebP decoders, so the saved file works fine inside any browser — but the moment you take it out of that environment, you hit the same wall HEIC users hit on iPhones.
Convert in your browser
Buncha's Bulk Image Converter reads WebP and writes PNG (or JPG, or back the other way) entirely client-side. Drop one file or fifty; pick PNG as the output; download the converted set.
The conversion uses your browser's built-in <canvas>. The browser decodes the WebP, paints it onto a canvas, and the canvas exports a PNG. No external library, no upload, no account. The only limit is your computer's memory if you drop a hundred huge images at once.
Lossless vs. lossy WebP — does it matter for the conversion?
Slightly. If the source is a lossless WebP (typical for screenshots and graphics), the PNG you get is pixel-perfect. If the source is a lossy WebP (typical for photos saved from web pages), the PNG preserves whatever the WebP already contains — but the quality loss happened upstream when the WebP was made, not in the conversion. Don't expect the PNG to "fix" a low-quality WebP.
File size — expect bigger
PNG is bigger than WebP at the same quality. A WebP photo that's 200 KB might become a 600 KB PNG, sometimes more. That's the cost of compatibility. If size matters for your destination (email, web upload), consider converting to JPG instead, or compressing the image afterwards.
Why we don't upload your file
Most "WebP to PNG" sites you'll find on the first page of Google are server-side. You upload, they convert, you download. That model has a few issues:
- Your image sits on a stranger's server for some retention window
- Conversion is rate-limited or paywalled past a few files
- Privacy depends entirely on whoever runs the site
Browser-side conversion has none of those problems. The image never leaves your device. There's no account, no daily limit, no upload meter. The trade-off is your laptop does the work — but <canvas> is a single-millisecond operation per file, so this isn't a real cost.
Animated WebP
WebP supports animation (similar to GIF). The PNG format doesn't, so converting an animated WebP gives you only the first frame. If you need to preserve motion, convert to GIF instead — most browsers can do that via <canvas> plus a small encoder library, or use a dedicated GIF tool.
Keeping transparency
PNG handles transparency, so any alpha channel in the source WebP carries over. This matters if you're working with logos, product cutouts, or anything with a transparent background — JPG would flatten the transparency to white, but PNG keeps it.
The shortest path
If you just want one file converted right now: open the converter, drop the WebP in, pick PNG as the output, download. That's it. No installs, no account, no upload.