A favicon generator solves the hard part: turning a logo, a letter, an emoji or an SVG into the set of files browsers and home screens actually ask for. The part that still goes wrong is installation. You download a neat zip, drop it somewhere on the site, and then the tab icon doesn't update, Google still shows a generic mark, or the PWA icon looks cropped on a phone.
This is a practical how-to for installing that package: where the files go, what the HTML should look like, and how to check the result before you declare it done.
What's usually in the package
A complete set is more than favicon.ico. Depending on the generator, you should expect some combination of:
- favicon.ico, often with more than one size inside, for older browsers and bookmarks.
- PNG icons at several sizes (16, 32, 180 and others) for tabs, shortcuts and Apple touch icons.
- An SVG favicon, if you started from a vector and want a crisp icon at any size.
-
Maskable icons and a web app manifest (
manifest.webmanifestormanifest.json) if you have a PWA, or want Add to Home Screen to look right. - An HTML snippet that points at those files.
If the zip is missing a manifest and you need one, or you're unsure whether the icons are declared correctly, that's a separate step from "put the ICO in the root" — and it's the step most often skipped.
Put the files where the HTML says they are
Pick a public, stable location and stick to it. Two patterns both work:
-
Site root.
/favicon.ico,/favicon-32x32.png,/apple-touch-icon.png,/manifest.webmanifest. Simple, and some browsers still request/favicon.icoautomatically. -
A dedicated folder, such as
/icons/or/favicon/. Tidier on a large site, but every path in the HTML and the manifest must match, and you may still want afavicon.icoat the root as a fallback.
What doesn't work is leaving the files in a private folder, behind authentication, or on a temporary CDN path that will change on the next deploy. Favicons are requested by browsers, crawlers and home screens, often without cookies and sometimes without the rest of your front-end router.
If you already have old favicon files in the root, replace them rather than adding a second set with new names and leaving the old ones in place. Otherwise you'll spend a morning wondering why a cache, a crawler or a bookmark still shows the previous icon.
Add the HTML, then check the manifest
Paste the generator's snippet into the <head> of your document — or into the shared layout template, if you have one. A typical set includes a root ICO or SVG, one or more PNG icons, an Apple touch icon, and a link to the manifest.
Then open the manifest itself. Icon paths inside it are often relative to the manifest file, not to the page. If you moved the manifest but not the icons, or the other way around, the tab may look fine while "Add to Home Screen" still pulls a missing or unexpected image.
If you started from a logo that doesn't fill the canvas, this is also the moment to confirm you really generated a maskable icon. Android will apply a mask (circle, squircle, and so on). A logo that sits too close to the edge will be cropped. The safe-area padding has to be in the image, not in your memory of the original artwork.
Install is not the same as "I see it on my machine"
Browsers cache favicons aggressively. A correct install can still show the old icon for a long time if you only check the tab you've had open since yesterday.
Work through a short verification list:
- Open the files directly. Visit each URL in the snippet and the manifest. You want a 200 response and the image you expect, not a 404 or an HTML error page.
- View source on a published page, not only on localhost, and confirm the final HTML has the tags you added. A build step, a CMS theme or a tag manager can drop or rewrite them.
- Hard-refresh or use a private window. If it still looks wrong, try a different browser, or temporarily add a query string to the icon URL while you're testing (and remove it once you're done — cache-busting query strings in production have their own problems).
- Check a phone home screen only after a fresh add. iOS in particular is stubborn about Apple touch icons it has already saved. Remove the shortcut and add it again.
- Don't trust your own computer alone. A favicon checker that fetches the live site from the outside will tell you whether the ICO, PNGs, SVG, Apple icon and manifest are actually reachable, which is the question that matters.
On Favicon.now the download includes the ICO, PNG, SVG, Apple and maskable PWA files plus a manifest and the HTML snippet. After you deploy, the site checker is the fastest way to see whether those public files resolve, and the HTML and manifest tools are there if you need to regenerate just that part of the package.
Common failures, quickly
- The tab icon updated, search results didn't. Search engines recrawl on their own schedule. Make sure a link to a real, square icon exists in the published HTML, then wait. You can't force it from the generator.
- The icon is blurry at 16×16. That's a design problem, not an install problem. A detailed logo often needs a simpler 16-pixel version. Re-export that size rather than hoping the browser will scale the large PNG kindly.
- Dark-mode tabs swallow a dark glyph. If you ship an SVG favicon, test it on a light and a dark browser chrome. A single-colour mark may need a background, or a media-query in the SVG, to stay visible.
- Only the ICO was deployed. Modern browsers may still show an icon, but Apple devices, PWAs and some search surfaces won't get what they need. Install the whole package.
Once the files are at stable URLs, the HTML and manifest agree, and an external check returns the icons you generated, you're done. The next time you change the mark, replace the same files at the same paths and plan for a cache delay — the install process itself shouldn't need to be invented again.
Top comments (0)