Written by Alex Chen — Frontend Engineer. I optimize images for the web and deal with format compatibility daily. More about me →
I migrated a client's WordPress site to WebP last month — 2,400 product images, average file size dropped 62%. The site went from a 4.3-second Largest Contentful Paint to 1.4 seconds. The client was thrilled. Then three days later their print vendor rejected every single image. "We don't accept WebP," the email said. "PNG or TIFF only."
WebP is incredible for the web. Google's own data shows WebP lossless images are 26% smaller than PNGs at equivalent quality. But the format hits a wall whenever an image leaves the browser: print shops, email clients, legacy CMS platforms, and presentation software all expect PNG or JPEG. So I've learned exactly when and how to convert WebP back to PNG without losing what matters.
I separate this into three situations where converting WebP to PNG is actually necessary:
Print and production. Most print-on-demand services (Printful, Printify, Gelato) require PNG or TIFF. WebP isn't in their pipeline. I learned this when a client's 300-dpi product photos — carefully edited and exported as WebP — got rejected by three different print vendors in one week.
Transparency edge cases. WebP supports alpha channels, but older image editors and some browser-based design tools don't render WebP transparency correctly. I've had WebP files with transparency show up with black backgrounds in older versions of Photoshop. Converting back to PNG with a proper alpha channel fixes it.
Batch processing for clients. When you're a developer handing off assets to non-technical stakeholders, they need formats that open everywhere. PNG opens in Preview, Paint, PowerPoint, and every email client. WebP doesn't.
Here's what I actually tested. I took a 2400×1600 photo, saved it as a lossless WebP (1.8MB), and converted it to PNG using four different methods:
macOS Preview export: works but one file at a time. Good quality, terrible throughput.
ImageMagick CLI: convert image.webp image.png — fast, scriptable, but the transparency handling in version 7.1.0-62 produced artifacts on partial-opacity pixels.
GIMP: full control but 11 clicks per conversion. Not viable for more than a few files.
Browser-based WebP to PNG converter: instant, batch up to 50 files, ZIP download. Transparency preserved. No artifacts on the partial-opacity test.
For bulk WebP to PNG conversion, I now use the browser tool for anything under 50 files and write a quick ImageMagick script for larger batches. The browser tool wins on convenience every time since there's nothing to install and no command to remember.
Three things every time. First, open a random sample in Preview and toggle between the WebP original and PNG output — look for color shifts. Second, check the file size: PNG should be larger than lossy WebP (it has more data), but if it's 10x larger, something went wrong. Third, if there's transparency, open the PNG against both white and dark backgrounds. I missed a transparency bug once because I only tested on white.
Written by Alex Chen — Frontend Engineer. I optimize images for the web and deal with format compatibility daily. More about me →