WebP to PNG Converter — Make Web-Saved Images Pasteable Again
You right-clicked, hit Save As, got a .webp — and now Word, PowerPoint, your old Photoshop, or your team's upload form just stares back. Drop the .webp here to get a PNG that opens everywhere, with transparency preserved.
Drop images here or click to browse
Supports HEIC, WEBP, AVIF, BMP, TIFF, SVG, GIF, ICO, PDF, JPG, PNG
100% Private — Your files never leave your device
All conversion happens directly in your browser using JavaScript. Nothing is uploaded to any server. Your images stay on your computer the entire time.
The two flavors of WebP (and why both convert to a single PNG)
WebP isn't one format — it's two stuffed into one container, chosen by the site that encoded the image:
- Lossy WebPuses Google's VP8 video codec. This is the default for photos and is what you almost always get when saving an image from a CDN or e-commerce site. It throws away high-frequency detail to shrink the file.
- Lossless WebPuses a custom entropy coder more like PNG's. It's common for icons, logos, and sprite sheets. Pixel-perfect, but only about 25% smaller than the same image in PNG.
The browser decoder doesn't care which mode was used — both come out as raw RGBA pixels that get handed straight to the PNG encoder. The resulting PNG is always lossless from that point on: future copy-paste, recropping, or re-saving won't degrade it further the way repeated JPG saves would.
Transparency, alpha, and the checkerboard
One of the main reasons people choose PNG over JPG for a WebP conversion is the alpha channel. WebP supports 8-bit alpha (256 levels of transparency per pixel) and so does PNG, so logos cut from a background, glassy UI elements, and product shots on checkerboard backgrounds come through cleanly. If you convert to JPG instead, every transparent pixel gets composited against a solid color — usually white — which is why logos suddenly grow a white halo when saved as JPG.
File size: what to expect after conversion
PNG will be larger — sometimes much larger — because it can't throw anything away. Concrete examples from typical web saves:
- 1200×800 product photo: 80 KB WebP → 1.4 MB PNG (~18×)
- 512×512 logo with transparency: 12 KB WebP → 24 KB PNG (~2×)
- Screenshot of a UI: 200 KB WebP → 600 KB PNG (~3×)
- Vector-style illustration: 60 KB WebP → 90 KB PNG (~1.5×)
If file size matters and you don't need transparency or pixel-perfect quality, consider WebP to JPG instead — you'll land closer to the original WebP size.
Who reaches for WebP → PNG
- Anyone pasting a saved web image into Microsoft Office — PowerPoint and Word still refuse WebP in many versions.
- Marketers grabbing competitor assets to drop into a deck or Figma board.
- Developers extracting an SVG-style logo from a site to drop into a README, where GitHub renders PNG but not always WebP attachments.
- Print-on-demand sellers whose Etsy / Printful / Redbubble uploaders explicitly require PNG or JPG.
- Anyone using a CMS or photo workflow built before 2020 (older WordPress, Lightroom Classic, vintage Photoshop).
Frequently asked questions
Does converting WebP to PNG lose quality?
Not in the conversion itself — PNG is lossless, so every pixel the WebP decoder produces is preserved exactly. But if the source WebP was created with lossy compression (the default for photos on most websites), those compression artifacts are baked into the pixels and will be carried into the PNG. Converting can't un-compress what's already been compressed; it just stops further degradation.
Why did the image I saved from a website come out as .webp instead of .jpg?
Most modern sites — including Google Images, Pinterest, Shopify storefronts, and anything behind Cloudflare's Polish — serve WebP because it's typically 25–35% smaller than the equivalent JPG. Your browser fetches whatever the server offers, so right-clicking "Save As" gives you the .webp the page actually loaded, not a JPG version of it.
Will transparency be preserved?
Yes. Both WebP and PNG support a full 8-bit alpha channel — every pixel can range from fully transparent to fully opaque. Logos cut out of a background, UI elements, and product shots with checkerboard transparency come across cleanly. JPG, by contrast, would flatten the alpha against a solid color.
Why is my PNG so much bigger than the original WebP?
Because they compress on fundamentally different principles. WebP photos use VP8 — a video codec — to throw away detail your eyes won't miss. PNG uses DEFLATE, the same algorithm in ZIP files, which only finds repeating patterns and never discards anything. For a photograph that ratio is often 4–6×. For a flat logo with few colors, the gap shrinks to almost nothing.