Convert WebP to PNG
Output is typically roughly 6.7× larger.
- Files stay on your device
- Free, no sign-up
Related tools
All image toolsQuestions
Why is my PNG so much larger than the WebP was?
Because PNG stores every pixel exactly, while WebP threw away the detail your eye is least likely to miss. A 400 KB WebP photograph commonly becomes a 4 MB PNG. Nothing has gone wrong — you are paying in file size for a format that will never lose anything again.
Will converting WebP to PNG make the file smaller?
Usually, yes. A 12-megapixel photo is around 2.1 MB as WebP and around 14 MB as PNG — roughly 6.7× larger. Because PNG is lossless the result depends entirely on the image content — flat colour and text compress far better than photographic detail.
Does converting WebP to PNG lose quality?
No. PNG is lossless, so every pixel decoded from your WebP file is stored exactly. Both formats are lossless, so the conversion is pixel-for-pixel identical.
Is transparency preserved when converting WebP to PNG?
Yes. Both WebP and PNG support an alpha channel, so transparent and semi-transparent pixels carry across unchanged — a logo with a cut-out background stays cut out, and soft drop shadows keep their gradient rather than picking up a white halo. Because PNG is lossless, the alpha channel is stored exactly as it was.
What happens to an animated WebP?
Only the first frame is converted. Every conversion here decodes one frame onto a canvas and re-encodes it, so the result is always a still image — that applies to PNG as much as to any other target. To shrink an animation while keeping the motion, a video file (MP4 or WebM) is usually around a tenth of the size of the equivalent WebP, and needs an encoder we do not ship yet.
When should I use PNG instead of a smaller format?
Use PNG when exactness matters more than size: screenshots, logos, diagrams, UI assets, anything with sharp text, and any image you will re-edit repeatedly. Lossless means no artefacts and no cumulative degradation. For photographs on the web, WebP or AVIF will be several times smaller at quality nobody can distinguish.
How it works, and more about webp to png
How it works
- Add your WebP file. Drag a WebP file onto the drop zone, or click to browse. You can select several at once.
- Choose your settings. PNG is lossless, so there is nothing to configure — the output matches the input pixel for pixel.
- Download the PNG. Conversion runs on your device as soon as each file is added — no upload, no queue. Download each result when it is ready.
Why people convert WebP to PNG
You saved an image from a website and now nothing local will open it. WebP is excellent on the web and still patchily supported in desktop software — older Photoshop versions, some print tools and plenty of corporate document workflows simply refuse it.
PNG is the safest target: readable everywhere, lossless from this point forward, and it keeps any transparency the WebP had. If the image is a photograph and file size matters more than exactness, JPEG is the smaller choice.
Worth knowing: PNG is lossless going forward but it cannot undo compression already applied. If the WebP was saved lossily, those artefacts come along — and the PNG will still be several times larger.
WebP and PNG side by side
| WebP | PNG | |
|---|---|---|
| Full name | WebP | Portable Network Graphics |
| Compression | Lossy or lossless | Lossless |
| Transparency | Yes — alpha channel | Yes — alpha channel |
| Animation | Yes | No |
| Browser support | All modern browsers — Chrome 32+, Firefox 65+, Safari 14+ (2020), Edge 18+ | Universal — every browser since 1996 |
| Typical 12 MP photo | ~2.1 MB | ~14 MB |
| Usually used for | Web images where page weight matters and modern browsers are the audience | Screenshots, logos, icons, diagrams and anything needing transparency |
On a typical 12-megapixel phone photo, the PNG output comes out roughly 6.7× larger than the WebP original. These are order-of-magnitude figures for one kind of image — your own results will vary a great deal, because flat colour, text and line art behave nothing like photographic detail.
What this tool actually produces
Not estimates. Each row below was produced by running the file through this page in a real browser and measuring the result, at the default quality of 82.
| Test image | WebP in | PNG out | Change |
|---|---|---|---|
| Smooth gradient 1600 × 1200, broad tonal transitions — where banding and blocking show | 175 KB | 3.1 MB | +1714% |
| UI screenshot 1440 × 900, dense text on flat panels — the hardest case for JPEG | 44 KB | 350 KB | +696% |
| Line-art diagram 1200 × 800, hard edges and large flat areas | 12 KB | 70 KB | +457% |
| Logo with transparency 512 × 512, flat colour on a transparent background | 7 KB | 69 KB | +899% |
Every test image got larger. That is expected for this pair rather than a fault: PNG is not the efficient choice for content that already suits WebP, and you are converting for compatibility or for editing headroom, not to save space. Measured in Chrome 150.0.7871.46; other browsers encode slightly differently.
What to watch out for
- Very large files for photographic content
- No animation (APNG is a separate, less-supported extension)
- Slower to decode than JPEG at the same pixel count
- Animation is lost. Only the first frame is converted — every conversion here decodes a single frame onto a canvas and re-encodes it, so the result is a still image whatever the target format. To shrink an animation and keep the motion, a video file is typically around a tenth of the size of the equivalent WebP.
About the two formats
WebP is the pragmatic modern choice for the web: roughly 25–35% smaller than JPEG at comparable quality, with transparency and animation that JPEG lacks, and — since Safari 14 in 2020 — support in every browser that matters. It is the format to reach for when you want smaller pages without worrying about fallbacks.
PNG stores every pixel exactly as it was, with no generation loss no matter how many times you re-save it. That fidelity is why it dominates screenshots, logos and UI assets, and also why it is the wrong choice for photographs — lossless compression simply cannot get a 12-megapixel photo down to a reasonable size.
Other conversions
Everything runs on your device — nothing is uploaded, so there is no size limit, no queue and no copy left on a server afterwards. There is more on how browser-based conversion works if you want the detail. Otherwise, browse every image tool, or convert PNG back to WebP.