Convert WebP to PNG on Mac, free and lossless.
WebP is Google's image format and it's everywhere on the web. The problem: half the apps you'd want to drop one into still don't open it cleanly, and the ones that do often re-encode it to something worse. Convertible turns WebP into PNG locally, with transparency intact and zero quality loss, on the free tier.
Drop the WebP into Convertible, choose PNG, click Convert. The PNG appears next to the original. Transparency is preserved, color is preserved, and the conversion is on the free tier so there's no upgrade prompt and no daily limit.
How it works, step by step
- Drag the WebP into Convertible. Straight from a Chrome download, a Slack message, a design handoff folder, anywhere. Single file or batch, both work.
- Pick PNG as the output format. If you'd rather have JPG (smaller, no transparency) or HEIC (smaller still, Apple-only), those are also one click away.
- Click Convert. The PNG lands next to the WebP. The image is decoded once and re-encoded to PNG with no intermediate compression step, so what you get back is bit-identical to what the WebP decoded to.
Why WebP support is still patchy
WebP is Google's image format, designed for the web, and it does its job well. Browsers love it. Most CDNs serve it by default. The problem starts the moment you try to use a WebP outside the browser. Figma will let you import one, but a lot of older Sketch and Illustrator workflows won't. Photoshop only added native support relatively recently. Slack previews them but the desktop app still occasionally chokes. And the macOS Finder shows a thumbnail but Quick Look on older versions of macOS doesn't always render it correctly.
Add to that the fact that designers and developers regularly need PNG specifically (for design assets, icons, app store screenshots, anywhere transparency matters), and the WebP-to-PNG round trip becomes a daily annoyance. Online converters work, but you're uploading your client's branding asset to a stranger's server, which is a worse trade than just doing it locally.
What you actually get back
PNG is a lossless format. WebP can be either lossy or lossless (most are lossless when used for design assets, lossy when used for photos on the web). Convertible decodes the WebP fully, then re-encodes the decoded pixels into PNG, so the output is pixel-identical to the WebP's decoded contents. No second compression pass, no quality drop. If the WebP had transparency, the PNG has transparency in the same alpha channel. If the WebP was an animated image, Convertible converts only the first frame to PNG (PNG isn't an animation format; APNG is, but it's rarely what you want).
PNG files are larger than WebP, sometimes a lot larger. A 200 KB lossy WebP photo can become a 2 MB PNG. That's the cost of lossless. If the file size matters more than absolute fidelity, JPG is a better target than PNG; you can pick that from the same dropdown.
Frequently asked questions
Why do websites use WebP instead of PNG or JPG?
WebP gives you roughly 25 to 35 percent smaller files than JPG at the same quality, and roughly 25 percent smaller than PNG for lossless images. For a website serving millions of images, that adds up to real bandwidth savings and faster page loads. Browsers all support it now, so for the web specifically it's the right call. The friction only shows up when you try to take a WebP back out of the browser into design tools, document workflows, or apps that don't expect it.
Does PNG keep the transparency from the WebP?
Yes. WebP supports an 8-bit alpha channel, and so does PNG. Convertible carries the alpha through bit-for-bit, so a WebP icon with a transparent background becomes a PNG icon with the same transparent background. No fringing, no white halo, no manual cleanup.
How does PNG quality compare to WebP?
PNG is lossless, so the quality is whatever quality the WebP was when it was decoded. If the original WebP was lossless, the PNG is identical. If the WebP was a lossy compression of some original (say a JPG that was re-encoded to WebP for the web), then the PNG preserves whatever quality that lossy WebP had, but it can't recover what the original WebP throw away. Converting WebP to PNG never makes the image worse, but it also can't make it better than the WebP already is.
Will the PNG be much larger than the WebP?
Often, yes. Lossless PNG can be several times the size of a lossy WebP, especially for photos. For design assets, screenshots, and icons the difference is smaller (PNG and lossless WebP are in the same ballpark). If file size matters more than format, target JPG instead, you'll get a much smaller file with quality that's visually indistinguishable for most photos.
Can I convert a folder of WebPs all at once?
Yes. Drop the entire folder onto Convertible (or open the folder and select all the WebPs), choose PNG, click Convert. The whole batch runs in parallel using all available cores. There's no per-batch fee or daily limit; image conversions are on the free tier.