How to convert WebP to PNG without uploading it
Every image you save from the web today arrives as a WebP. Google made the format the default for web images because it is smaller — but the tools people actually work in (older Photoshop, office suites, upload forms, print shops) never caught up. The usual "free" converter fixes that by uploading your image to its server, converting it there, and capping you at 10 or 25 files a day. The safer approach is converting the file where it already is: on your own device.
This tool does exactly that. When you drop a WebP here, your browser:
- Reads the file with its own built-in WebP decoder — every modern browser has one, so no decoder needs to download and the page stays light.
- Draws the image onto a canvas at its original dimensions, with transparency intact.
- Re-encodes it as PNG and hands you the result as a download. Your original file is never modified, and each file converts the moment you add it — no Convert button, no queue to wait for.
What is WebP, and why does it need converting?
WebP is Google's image format, released in 2010 to replace JPG and PNG on the web. It compresses better than both — typically 25–34% smaller than a JPG at similar quality and about 26% smaller than a PNG — and it supports transparency like PNG and animation like GIF, all in one format. That is why every browser and every major website now serves images as WebP. The problem is everything outside the browser: desktop editors, design tools, document software, and upload forms that were built before 2010 often have no WebP decoder at all. A WebP saved from a website will open fine in Chrome and then fail in Photoshop CS6, an old Word, or a form that only accepts JPG and PNG. Converting to PNG is the fix that works everywhere, because PNG has been universally supported since the late 1990s.
When PNG is the right choice
PNG is the right output when the image has a transparent background, contains text or sharp lines, or must survive editing without any further quality loss. Logos, icons, diagrams, screenshots of interfaces, and product cutouts all belong in PNG: its lossless compression keeps every edge crisp and every transparent pixel transparent. It is the wrong choice for photographs you plan to email or upload — a photo that was 800 KB as a WebP can come back as 3–4 MB of PNG, and nothing about the picture improves. If the image is a photo and the destination accepts JPG, convert to JPG instead; choose PNG when transparency, sharp edges, or pixel-perfect editing matter more than file size.
A worked example: a website logo
Say you saved a company logo from a website and it arrived as logo.webp,
240 KB, with a transparent background. You need it in a slide deck that rejects WebP.
Drop it here: the tool decodes it, keeps the transparency, and offers
logo.png for download — typically 400–600 KB, larger because PNG stores
every pixel exactly. The preview card shows the logo on a checkerboard, which is how
you confirm the transparency survived: a white box behind the logo would mean it was
flattened. Open the PNG in the deck and it sits cleanly on any slide background. If
instead the deck flattened transparent PNGs to black, you would re-run the same file
with "White" selected under Transparent areas and get an opaque logo on white.
Quality notes: what converting to PNG does and doesn't do
Converting WebP to PNG never improves quality and never loses any — it preserves exactly what the browser decoded. If the original WebP was lossy (most web images are), the compression artefacts baked into it are carried into the PNG unchanged; PNG cannot restore detail the WebP encoder already threw away. What PNG does guarantee is that no further loss happens: you can open, crop, and re-save the PNG as many times as you like without the gradual softening that re-saving a JPG causes. Dimensions are also preserved exactly — a 1920 × 1080 WebP becomes a 1920 × 1080 PNG — and orientation is read from the file, so a photo stored sideways comes back upright.
Mistakes that waste your time
The most common one is renaming the file: changing photo.webp to
photo.png does not convert anything — the bytes are still WebP, and most
programs refuse to open it. The second is converting photographs to PNG for email
or upload forms and then wondering why the attachment is enormous; PNG is the wrong
format for photos, and the size jump is the format working as designed. The third is
assuming an animated WebP will stay animated: PNG is a still format, so only the first
frame survives — if you need the motion, convert to GIF or APNG instead. And the
fourth is trusting an upload-based converter with screenshots that contain passwords,
financial data, or personal information; those images should never leave your device,
which is exactly the case this tool is built for.
Honest limitations
PNGs are larger than WebPs
WebP is 25–34% smaller than PNG at similar quality, and PNG is lossless on top of that. The before/after panel shows this honestly: a bigger output file is the price of universal compatibility, not a bug.
Animated WebP loses the motion
An animated WebP is several frames. Only the first frame is converted; the rest are dropped. Keep your original if you want the animation.
Lossy artefacts are carried over
If the WebP was lossy, its compression artefacts are baked in and survive into the PNG unchanged. PNG preserves what it is given — it cannot restore detail that was already discarded.
Metadata is stripped
Camera metadata (EXIF, including location) is not carried into the PNG on re-encode. Orientation is preserved — the output is stored upright — but the rest of the metadata is gone.