PNG to WEBP Converter
Re-save PNGs as WEBP for a much smaller file, with transparency intact. The images stay on your device.
Drop PNG files here
or click to browse (multiple selection works)
Accepts: .png
Why PNG to WEBP makes sense
PNG is lossless and big. WEBP is lossy at the quality you pick, and roughly half the size of an equivalent PNG. The trade is small visual loss for a much smaller file. For websites, app assets, and anywhere a designer is yelling about page weight, WEBP is the upgrade.
And transparency still works
Unlike JPG, WEBP supports alpha channels. So a PNG with a transparent background converts cleanly. No white fill, no halos.
What this does
- Decodes each PNG.
- Re-saves it as WEBP at your chosen quality.
- One file in, one out. Several in, you get a zip.
Nothing leaves your browser
All the work happens in this tab. Want to confirm? Disconnect from the internet after the page loads. Conversions still complete.
About the PNG format
PNG (Portable Network Graphics) was finalized by the W3C in 1996 as the open replacement for GIF, which at the time was encumbered by Unisys's LZW compression patent. It's a lossless raster format: every pixel that goes in comes out exactly the same. PNG handles full 8-bit alpha transparency, palette images, and grayscale, and is the default screenshot format on macOS, Windows, and most Linux desktops. Because the compression is lossless and tuned for flat colors and sharp edges, PNG produces small files for UI mockups, logos, and pixel art, but balloons for photographs.
About the WEBP format
WEBP is Google's image format, released in 2010 and built on top of the same VP8 video codec that powered early WebRTC. It supports both lossy and lossless modes, plus alpha transparency, animation, and ICC color profiles. The selling point is size: at visually similar quality, WEBP files are typically 25-35% smaller than JPEG and 50-80% smaller than PNG. Every modern browser supports it, and the format is the default for Google's own image-heavy properties. The catch is older desktop apps and Windows Photo Viewer (pre-Win11) still refuse to open it.
When to use PNG to WEBP (and when not to)
Pick this conversion when:
- You're shipping image assets for a website and need the page to load faster.
- The PNG has transparency you can't lose by going through JPG.
- You have a folder of screenshots eating up disk space.
- You're packaging app or game art and every megabyte counts.
Skip it when:
- The PNG is going to a print shop, government portal, or older desktop tool that still rejects WEBP.
- You need lossless fidelity for an archive or for further editing.
Common problems and how to fix them
- The WEBP looks blurry compared to the PNG. The quality slider is set too low. Bump it from Compact to Standard or High and the visible loss disappears.
- Transparency turned into a black or white halo. Some older PNGs use 1-bit transparency masks instead of an alpha channel. Re-export the source with full alpha and convert again.
- The output is bigger than the source. Rare, but happens with pixel art or tiny PNGs already heavily optimized. WEBP's overhead doesn't pay off below a few KB. Keep the PNG.
- Colors shifted slightly. WEBP encoders sometimes drop or rewrite the ICC color profile. For brand or print work, keep a PNG master.
- Browser can't preview the WEBP. If you're on Windows 10 with no Photo Viewer update, open it in any current browser instead. The file is fine.
Frequently asked questions
Does the conversion happen on your servers?
No. The PNG is decoded and re-encoded inside this browser tab using the Canvas API. You can disconnect from the network after the page loads to verify — conversions still complete.
Can I convert hundreds of PNGs at once?
Yes. Drag them all in and the results come back as a single ZIP. The practical ceiling is your device's RAM; a laptop handles thousands of small PNGs without issue.
Is the transparency really preserved?
Yes. WEBP supports an 8-bit alpha channel like PNG. You get smooth, anti-aliased edges, not just a 1-bit mask.
What quality setting should I use?
Standard (0.85) is right for almost everything. Drop to Compact only for thumbnails or when you specifically need the smallest possible file. High (0.95) is for source-quality assets.
Does this support animated PNGs?
No. Animated PNG (APNG) doesn't round-trip cleanly to animated WEBP in a browser. For animation, keep the APNG or convert with a desktop tool like ffmpeg.
What about lossless WEBP?
This converter uses lossy WEBP for the size win. If you need pixel-perfect output, keep the source PNG — there's no point converting losslessly.