WebP to PNG Converter — For Tools That Refuse WebP
Lossless conversion. Universal PNG compatibility. Animation caveats covered.
Chrome saves images as WebP by default. So does Firefox. Then you try to open the file in Photoshop, paste it into a Word document, or attach it to an Outlook email — and something refuses. Most professional editing tools, office suites, and email clients added WebP support late or partially, and many still trip on it depending on version. PNG is the universal fallback: lossless, supported by every image-aware piece of software since 1996, and a perfect copy of your WebP source. Drop WebP files below, click Convert, and download PNG.
Real-World Benchmark — Our Own Tests
Below are file sizes (rounded to the nearest readable KB; byte-exact values in src/assets/benchmarks/webp-to-png/results.json) from running this exact converter (tooldev.app v1.5) on five representative WebP inputs synthesised from our reference PNG set. No theoretical estimates — these numbers reflect the actual Canvas-API output produced by the same engine you are using on this page.
| Sample | Source WebP | PNG output | Size change |
|---|---|---|---|
| icon (256×256, transparent) | 4.7 KB | 21 KB | 4.5× larger |
| photo (1920×1280) | 86 KB | 945 KB | 11.0× larger |
| screenshot (1440×900) | 20 KB | 143 KB | 7.1× larger |
| gradient (1280×720) | 7.7 KB | 145 KB | 19.0× larger |
| composite (1280×853) | 16 KB | 203 KB | 12.8× larger |
Methodology & honest caveats
Test images are all self-generated by tooldev.app (see src/assets/benchmarks/samples/SOURCES.md). Reference PNGs were first re-encoded to WebP at quality 85 via the same engine to produce realistic WebP inputs, then converted to PNG. Conversions executed via tooldev.app v1.5 on 2026-05-20 in Chromium 148 on macOS. PNG output is lossless by design — there is no quality slider, so the table shows one output column. Reported file sizes are rounded to the nearest KB from the actual Canvas-API toBlob output. In our tests WebP → PNG did not reduce file size, and for normal content it usually grows substantially. PNG is a lossless container that faithfully preserves the decoded pixels of a typically-lossy WebP source — in this benchmark that means 4–19× the original size. The growth ratio is steeper than JPG → PNG because lossy WebP usually compresses better than JPG, so the WebP source files are smaller to begin with, and PNG's DEFLATE compression still has to encode all the same decoded pixels. Animation is not preserved. If the input is an animated WebP, our converter only encodes the first frame — PNG is a single-frame format and animation requires APNG, which we do not output. Use WebP → PNG when a downstream workflow explicitly requires a PNG container, not for storage savings. Sample files: icon.png, photo.png, screenshot.png, gradient.png, composite.png — all in our repository under src/assets/benchmarks/samples/.
Your Files Never Leave Your Browser
Conversions run locally in your browser using the Canvas API, with Web Workers used when supported. Your image data stays on your device and is never uploaded to any server.
We use Google Analytics and Google AdSense for aggregated traffic stats and contextual ads when consent allows it. Theme and language preferences stay in your browser. We never see, read, or store the images you convert.
Browser-based conversion has trade-offs: large files (>50 MB) may hit memory limits; animated GIF output flattens to a single frame; EXIF metadata is stripped; ICC color profiles may differ across browsers.
> webp_to_png_technical_notes
The reason WebP-to-PNG conversion exists at all is a software compatibility gap, not a quality problem. Understanding which tools accept WebP and which still refuse it is the difference between converting unnecessarily and converting only when you need to.
Software compatibility map (as of 2026)
Tools that accept WebP natively (no plugin needed): Adobe Photoshop 23.2+ (March 2022), Adobe Lightroom Classic 11.3+, Affinity Photo 2.0+, Figma (web), Pixelmator Pro 2.4+, GIMP 2.10+, modern macOS Preview (12+), Windows 10 1809+, Windows 11.
Tools that need a plugin or refuse WebP: Photoshop CS6 and earlier, Adobe Acrobat (PDF embedding), older versions of Microsoft Office, many enterprise document management systems, IrfanView (without the WebP plugin), legacy Windows Photo Viewer, ImageMagick versions before 6.6.5.
The painful gap is corporate environments. Many companies are still running Office 2016 or Office 2019 on Windows 10 LTSC, with locked-down software updates. WebP support in those Office versions ranges from "partial" to "nonexistent". When you need to embed an image in a presentation that will be opened on those machines, PNG is the safe choice.
Email client compatibility (where WebP still fails)
Email is the most common place where a WebP attachment causes problems. Inline images in HTML emails are read by the recipient's mail client, not by their browser, and email-client WebP support lags far behind browser support:
- Apple Mail (macOS, iOS): Works — uses the system image rendering pipeline, supports WebP since the OS does.
- Gmail (web interface): Works — handles WebP fine in the browser-based reader.
- Outlook for Windows (desktop, including 2016/2019/365): Inconsistent. Some versions render inline WebP, others show a broken-image icon. PNG always works.
- Outlook for Mac: Generally works in recent versions, but not in older builds still in use at many enterprises.
- Thunderbird: Works in modern releases; fails silently in versions older than 91 (2021).
- Mobile mail apps (third-party): Hit-or-miss. Some render WebP, some show a placeholder.
If you are sending an image in an email and you cannot guarantee the recipient's client, send PNG. The bandwidth cost is negligible for a single attachment.
The "PNG is bigger than my WebP" paradox
If your source WebP was lossy, the output PNG will typically be 2–4× larger than the WebP. This is not a bug. WebP achieves its size advantage by discarding data that PNG cannot discard — that's the entire definition of lossy compression.
The PNG that comes out is a perfect copy of the decoded WebP, including all the smoothing and quantization the lossy encoder performed. You are not getting more quality back, but you are also not losing any quality compared to what was already in the WebP. The trade-off is file size for software compatibility, not file size for quality.
Animated WebP — only the first frame survives
WebP supports animation, similar to GIF or APNG. Browser-based Canvas conversion does not preserve animation: drawImage on an animated WebP renders only the first frame, producing a static PNG with the rest of the animation discarded. This is a hard limitation of the Canvas API, not a bug in this converter.
If you need to preserve animation when converting from WebP, you have two options: convert to APNG using a desktop tool like ffmpeg or img2webp in reverse, or convert to animated GIF (with quality loss). Standard PNG is single-frame only.
> how_to_convert
- Upload your WebP fileDrag and drop your WebP image into the converter, or click "browse files". Multiple files are supported for batch conversion.
- PNG is pre-selectedThe output format is already set to PNG. No quality adjustment is needed — PNG output is always lossless.
- Download your PNGClick "Convert All", then download files individually or as a ZIP archive.
> webp_vs_png
| Feature | WebP | PNG |
|---|---|---|
| Browser support | Chrome, Firefox, Safari 14+ | All browsers & software |
| File size | Smaller | Larger |
| Compression | Lossless + Lossy | Lossless only |
| Editing software | Limited | Universal |
| Transparency | ✓ Yes | ✓ Yes |
| Best use case | Web delivery | Editing, archiving, sharing |
> when_not_to_convert_webp_to_png
Most "I need to convert WebP to PNG" requests are driven by a software-compatibility frustration that has a different solution. Five cases where the conversion is the wrong response:
1. The image is going back on a website
If your goal is to publish the image on the web — your blog, a CMS, an e-commerce product page — converting WebP to PNG is the wrong direction. WebP was designed for web delivery and is supported by 97%+ of browsers. PNG will be 2–4× larger with no benefit to the visitor's browser. Keep the WebP, or if you need an even smaller file, consider AVIF.
2. Your editor supports WebP and you just didn't know
Photoshop has supported WebP natively since version 23.2 (March 2022). Affinity Photo 2 supports it. GIMP supports it. macOS Preview opens it. Before converting, check your tool's actual current capabilities — you may discover the WebP opens fine if you update or use a different file menu. The conversion-tax-for-no-reason cycle is more common than you might expect.
3. The image is animated and you want the animation
If your WebP is animated (a short looping clip downloaded from a website), browser-based PNG conversion will discard the animation and keep only the first frame. PNG itself does support animation via the APNG extension, but Canvas API conversion cannot produce APNG. To preserve the animation, use a desktop tool like FFmpeg or convert to GIF instead. If the animation matters, do not use this converter.
4. You need maximum compression for storage or transfer
If you are archiving a large photo library, transferring images over a slow connection, or paying per gigabyte for storage, WebP is the wrong source format to abandon. The PNG output will be 2–4× larger. Keep the WebP. Tooling that handles WebP is more available every year, and storage compression efficiency only matters if your downstream tools can read the format.
5. You expected PNG to give back quality the WebP discarded
If your source was lossy WebP, the PNG output is a faithful copy of the already-compressed pixels. PNG is lossless going forward, but it cannot recover detail that lossy WebP threw away — same principle as JPG-to-PNG. If the WebP looks soft or shows compression artifacts, the PNG will too. PNG is a container, not a quality-restoration tool.
> when_webp_to_png_is_the_right_move
WebP is excellent for web delivery, but it wasn't designed for workflows that happen outside the browser. Most professional image editing tools — Photoshop, GIMP, Affinity Photo, older versions of Figma — either don't support WebP natively or support it with limitations. The moment an image leaves the web and enters a design or editing workflow, PNG is almost always the better format.
Situations where converting WebP to PNG solves a real problem:
- Editing in Photoshop or other design software — if you downloaded an image from a website and it saved as WebP, you'll need PNG to open it properly in most professional tools without installing plugins.
- Preparing images for further editing — PNG is lossless, meaning you can edit, save, and re-export repeatedly without any cumulative quality loss. Lossy WebP doesn't give you this guarantee.
- Sharing with clients or colleagues using non-web tools — designers and non-technical users commonly work with PNG, JPEG, or TIFF. WebP can be confusing or simply unopenable without a modern browser.
- Long-term archiving — if saving images for future re-editing, lossless PNG is more reliable than WebP from a software compatibility standpoint. PNG support is universal; WebP is not.
- Presentations and documents — Microsoft PowerPoint and Google Slides support PNG universally. WebP support in office tools varies significantly by version and platform.
One thing to expect: the PNG output will be noticeably larger than the WebP source — typically 2–4x. This is normal. PNG is storing all pixel data without compression shortcuts, which is precisely why it's better for editing.