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.
Who builds and writes this
Abdessamad Bettal
I'm a web developer, and favicon.tools is a one-person project — I write the code, the guides and this sentence. It started the way most tools do: I needed a favicon set for a side project, worked through the usual pile of half-correct blog posts and generators that hand you a 2013-era file list, and decided the whole thing deserved to be done once, properly.
Everything published here comes out of building the tools themselves — the ICO packer, the manifest writer and the checker were all written from the file-format specs and tested against real browsers, which is where most of the detail in the guides comes from. If something here is wrong, I'd genuinely like to know: contact@favicon.tools.
Editorial standards
The guides exist to answer a question completely enough that you don't need a second tab open. That means a few rules:
Every claim is verified against a real browser
Size tables, tag syntax and framework instructions are checked against the actual behaviour of current Chrome, Safari, Firefox and Edge before they're published — not copied from another blog post that copied it from a third.
Guides say when something is out of date
Favicon advice rots quickly: sizes get deprecated, Safari drops a tag, a framework changes its conventions. Where a widely-repeated recommendation is no longer true, the guide says so explicitly rather than repeating it for safety.
No sponsored posts, ever
Nothing on this site is paid placement. Ads are served by Google AdSense and are clearly ad-shaped; they never appear as recommendations inside a guide, and no third party has any say in what gets written.
Corrections are made in place
If a guide is wrong, it gets fixed rather than quietly deleted. Write in and the correction usually ships the same week.
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, and honest about why
No accounts, no paywall, no watermark, no usage limits, and no premium tier hiding behind the free one. Hosting and the domain are paid for by the ads on the page — that's the whole business model, and it's why your files still don't need to touch a server.
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.