WEBP -> PNG · Local tool
WebP to PNG
Turn WebP images into PNG files that older editors and programs will open.
Last updated
01 / Your device
the file stays here
02 / Browser memory
the work runs locally
03 / Back to you
saved on this device
When you would use this
Situations, not settings.
- A WebP your editor will not open
- Older Photoshop, Illustrator and plenty of desktop tools still stop at WebP. PNG is what they were built to read.
- An image saved from a site for a document
- Right click and save on most sites now hands you a WebP. Word and PowerPoint take a PNG without argument.
- A picture you are about to edit repeatedly
- Every save of a lossy file costs a little more detail. Moving to PNG first stops the bleed for the rest of the work.
How it works / no cloud
A conversion engine, not an upload form.
Your browser already decodes WebP, so filetity reads the image with the browser's own codec and writes it back out as PNG, which stores every pixel exactly. Nothing is uploaded and no extra engine is downloaded.
- Offline ready
- Installable app
- No file limit queue
Straight answers
No accordion. Nothing hidden.
- Is it free?
- Yes, with no watermark and no page limit.
- Does it need an account?
- No. There is no account system.
- Is my file processed on my device?
- Yes. The file is read by your browser and never uploaded. There is no server to send it to.
- What formats are supported?
- WebP in. PNG out, one file per image, or a ZIP when you convert several.
- What are the limits?
- No image count limit. An animated WebP comes back as a still of its first frame, because PNG holds one image. Expect the PNG to be several times larger than the WebP was.
- Does it work on mobile?
- Yes, on any modern mobile browser. Large files are limited by the memory the phone gives the browser.
- Does it work offline?
- Yes, after you have used it once. Your browser keeps what the tool needs, so it then works with no network connection.
- What happens to an animated WebP?
- Only the first frame survives. PNG holds a single image, so the animation stops at frame one and everything after it is dropped. The PNG will not tell you that afterwards, so if the motion matters, keep the WebP as well.
- Why is the PNG so much bigger?
- Because it is lossless. WebP throws away detail to get small, and PNG stores every pixel exactly, so a photograph often grows several times over. That is the trade for a file anything will open and that survives repeated editing.
- Does this make the image sharper?
- No, and nothing can. PNG records exactly what the WebP contained, including the detail the WebP threw away. It stops further loss from this point on, which is why it is the right format to edit in, but it cannot recover what was never stored.
- Is transparency kept?
- Yes. Both formats have a real alpha channel, so see-through areas come across unchanged, with no white background painted underneath.
- Can I resize on the way?
- Yes. The menu fits the longest edge to 2048, 1600, 1024 or 640 pixels, keeping proportions, and never enlarges. A WebP served for the web is often already small, so most of these steps will leave it alone, and the result says the size it produced.
Keep working locally
7 available · more coming
- PNG to WebPTurn PNG and JPG images into WebP, which usually lands smaller at the same quality.
- WebP to JPGConvert WebP to JPG free, so the image opens on any app or device.
- AVIF to PNGTurn AVIF images into PNG files that anything can open.
- TIFF to PNGTurn a TIFF or TIF into a PNG, losing nothing and keeping transparency.
- JPG to PNGTurn JPG photos into PNG files that will not lose any more detail.
- GIF to PNGTurn a GIF into a lossless PNG still, with its transparent areas intact.