Skip to content
SnapTools

Favicon Generator

Runs in your browser

Turn one logo into a complete favicon set — favicon.ico, apple-touch-icon and PNGs from 16 to 512 pixels. Generated in your browser.

HTML for your <head>
<link rel="icon" href="/favicon.ico" sizes="32x32">
<link rel="icon" href="/favicon-192x192.png" type="image/png" sizes="192x192">
<link rel="apple-touch-icon" href="/apple-touch-icon.png">

About this tool

A favicon is not one file any more. Browsers want a small .ico, iOS wants a 180-pixel apple-touch-icon for the home screen, Android and PWA manifests want 192 and 512 pixel PNGs, and each is requested in different circumstances. Generating them by hand means six exports at exact sizes; getting one wrong usually shows up as a blurry icon on someone else's phone months later. This produces the whole set from a single source image, including a real multi-resolution .ico.

How to use

  1. Drop in a square logo — 512 pixels or larger gives the best results.
  2. Run it and download the ZIP.
  3. Put the files in your site's root and paste the HTML snippet into your <head>.

When to use this tool

  • Adding a proper icon set to a new website.
  • Replacing a favicon that looks blurry on high-density screens.
  • Producing the icons a PWA manifest requires.
  • Refreshing every icon after a rebrand.

Tips

  • Start from a square source. A rectangular image is fitted into each square, which usually is not what you want — crop it first.
  • Simple, high-contrast marks survive being shrunk to 16 pixels; detailed logos turn to mush. Consider a simplified mark for the small sizes.
  • Keep the file names as generated — the HTML snippet and most manifest examples assume them.

Limitations

  • Square sources work best. A rectangular image is scaled to fit each square, so crop it first if the framing matters.
  • The .ico contains 16, 32 and 48 pixel versions, which is what browsers actually request.

FAQ

Is my logo uploaded?
No. Every size is rendered in your browser and the .ico is assembled locally. Nothing is transmitted or stored.
What is inside the .ico file?
The 16, 32 and 48 pixel versions, which is what browsers actually request from favicon.ico. The larger sizes ship as separate PNGs, which is how modern sites reference them.
Do I still need favicon.ico at all?
Yes, practically speaking. Browsers request /favicon.ico by default even when PNG links are present, and some feed readers and crawlers only look for that path.

Common jobs this solves

Related tools