Built for the smallest asset on the web.
favicon.tools is a small, focused suite for one job: getting a correct, complete favicon set out of whatever you're starting from — an icon, an emoji, a couple of letters, or a logo you already have. It also checks what a live site is actually serving, since the gap between "I added a favicon" and "every platform can see it" is where most favicon problems live.
What it's built on
On-device by default
The Generator and Converter render every icon in your browser with the Canvas API. Your artwork is never uploaded, so there's nothing to leak, store or delete later — closing the tab clears everything.
Free, with no catch
No accounts, no paywall, no watermark, no usage limits. There's no premium tier hiding behind the free one.
Built for the real workflow
A favicon isn't one file anymore — it's an .ico, a set of PNGs, an Apple touch icon and a web manifest, each with its own size and rules. The tools handle all of it in one pass instead of leaving you to hand-assemble it.
Small, and staying that way
This is three focused tools, not a platform. Every addition has to earn its place rather than pad out a feature list.
How it actually works
The Generator and Converter run entirely client-side: Next.js and React render the UI, and the actual image work — resizing, padding, recoloring, encoding — happens in the browser's Canvas API, including a hand-built PNG-to-ICO packer and a ZIP writer, so no image library or server round-trip is involved. The Checker is the one part that talks to a server: it fetches a page's public HTML (the same way a browser would), reads its declared icons and manifest, and probes each one for reachability — nothing about that request is stored afterward.
The three tools
Questions or feedback?
Bug reports, feature requests and general feedback are all welcome at contact@favicon.tools, or see the contact page for more.