GIF -> WEBP · Local tool
GIF to WebP
Turn a GIF into a still WebP. The animation is not carried across.
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 still GIF slowing down a page
- Most GIFs on the web never move. As a WebP the same picture is a fraction of the download.
- Old site assets being modernised
- A folder of GIF buttons and dividers converts in one pass, clear backgrounds and all, ready for the new templates.
- A GIF for a tool that only reads WebP
- Some newer frameworks and image pipelines take WebP and nothing older. This is the one step that gets there.
How it works / no cloud
A conversion engine, not an upload form.
Your browser decodes the GIF and encodes WebP, so filetity draws the first frame on a canvas and writes it out at the quality you choose. That canvas encoder writes exactly one frame, which is why an animated WebP is not on offer here. Nothing is uploaded.
- 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?
- GIF in. WebP out, one file per image, or a ZIP when you convert several.
- What are the limits?
- No image count limit. WebP can hold an animation and this tool cannot write one, so you get a still of the first frame. A GIF holds at most 256 colours, and transparency is kept.
- 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, once the page has loaded. The tool keeps working with no network connection.
- Will I get an animated WebP?
- No. WebP as a format is perfectly capable of holding an animation. The encoder built into your browser, which is what this page uses, writes a single frame and has no way to write more. So an animated GIF comes back as a still of its first frame. If you want the motion in a smaller file, keep it a GIF and compress that instead.
- Then what is this page for?
- A GIF that was never animated, which is most GIFs on the web: a logo, a diagram, a button, a screenshot somebody saved in the wrong format. WebP carries those at a fraction of the size with the clear background intact.
- Is transparency kept?
- Yes. A GIF's clear colour comes across as a real alpha channel in the WebP, and WebP can hold the soft edges a GIF had to make jagged.
- Will it actually be smaller?
- For a single frame, usually yes and often by a lot, because 256 colour GIF compression is decades behind WebP. Against a long animation the comparison is not meaningful, since you would be weighing a whole animation against one picture.
Keep working locally
4 available · more coming