filetity

PNG or JPG -> WEBP · Local tool

PNG to WebP

Turn PNG and JPG images into WebP, which usually lands smaller at the same quality.

Last updated

  1. 01 / Your device

    the file stays here

  2. 02 / Browser memory

    the work runs locally

  3. 03 / Back to you

    saved on this device

When you would use this

Situations, not settings.

Images making a page slow
WebP usually lands 25 to 35 percent under PNG at the same quality, and keeps transparency.
A site that already serves WebP
Converting the assets once is simpler than adding a build step for it.
Storage filling up with screenshots
A folder of PNG captures shrinks noticeably with nothing visible lost.

How it works / no cloud

A conversion engine, not an upload form.

Your browser already encodes WebP, so filetity decodes the image with the browser's own codec, redraws it on a canvas and encodes the result as WebP. No conversion service, no upload and no extra engine to download.

  • 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?
PNG and JPG in. WebP out, one file per image, or a ZIP when you convert several.
What are the limits?
No image count limit. Very large images are bounded by the memory your browser will give a canvas. Animated GIFs are not accepted, and this does not produce animated WebP.
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.
How much smaller is WebP?
It depends on what the image is, and the range is wide. Measured in Chrome on 2026-08-26 at quality 85, a 3080 by 2052 photo went from 1,014,388 bytes as JPG to 782,002 as WebP, 23% smaller. A 1200 by 800 PNG graphic went from 134,635 bytes to 9,872, 93% smaller, because PNG was never compressing it well. A JPG that is already heavily compressed can shrink very little, or grow.
Does transparency survive?
Yes. WebP has a real alpha channel, so transparent areas of a PNG stay transparent. That is why WebP replaces PNG on the web as well as JPG.
What still cannot open WebP?
Every current browser reads WebP, and so do Windows, macOS, iOS and Android. Older desktop software still trips over it: some versions of Photoshop without a plugin, older Office, plenty of print shops, and the image libraries inside long-lived internal tools. If a file is going anywhere other than a web page, check first.
Should I archive my photos as WebP?
No. WebP is built for delivery. It is lossy by default, support outside browsers is thin, and print workflows expect JPG or TIFF. Keep the original and publish the WebP.
Why is the WebP bigger than my JPG?
Because the JPG was already squeezed hard, and a second lossy pass over it has little left to save. The result line shows the change and tells you to keep the original when the WebP grew. Converting from the PNG or the camera original avoids the double pass.

Keep working locally

7 available · more coming