filetity

ICO -> WEBP · Local tool

ICO to WebP

Turn a Windows ICO icon into a WebP for use on a web page.

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.

A site icon reused as a page image
The favicon already holds the mark you want in a header or a card, and WebP is what the rest of the page is served in.
An icon set being packaged for the web
A folder of ICO files converts in one pass, clear backgrounds kept, ready to be referenced from CSS or markup.
A desktop app icon going into a web dashboard
Windows software ships ICO files. A dashboard listing those apps needs something a browser will lay out normally.

How it works / no cloud

A conversion engine, not an upload form.

Your browser decodes ICO and encodes WebP, so filetity reads the icon and writes it out at the quality you choose, keeping the alpha channel. The browser hands back the largest size the icon holds, and that is what gets written.

  • 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?
ICO in. WebP out, one file per image, or a ZIP when you convert several.
What are the limits?
No image count limit. Only the largest size in the icon comes out; the smaller copies are dropped. WebP is lossy at the default quality, so raise it if the icon's edges start to look soft.
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.
Which size comes out?
The largest one the icon holds. Measured in Chrome on 2026-09-06 against a four size ICO, the browser returns the 256 pixel copy and ignores the rest, whichever order they appear in.
Is a lossy format right for an icon?
Not at the default setting. An icon is flat colour and hard edges, and lossy compression softens exactly those. Raise the quality, or use PNG, which stores the icon exactly and is often smaller than a high quality WebP for this kind of picture.
Does transparency survive?
Yes. WebP has a real alpha channel, so the clear area around the icon stays clear.
Why not just use the ICO on my site?
Browsers do read ICO, which is why favicons still work. But an ICO is a container of square sizes, so it is awkward as a page image, and its compression is decades behind WebP. For anything other than the favicon slot, a WebP or a PNG is the better file.
Can I get a smaller WebP than the icon's largest size?
Not here. The resize menu starts at 640 pixels, and an icon is never larger than 256, so those steps change nothing on this page. Convert first, then take the WebP to the Image Resizer, which goes down to any width you type, for a 64 or 32 pixel version.

Keep working locally

7 available · more coming