Skip to content

Why your favicon isn't showing and how to fix it

A checklist for a favicon that's missing or stuck on the old picture, covering the file, the link tag, formats, stored copies and Google's rules.

Reviewed 15 November 2026

Work down this list in order. The earlier items are quick, and they cause the most trouble. Each has a short note on how to check it.

Working through a missing faviconOpen the icon's address directlyCheck the link tag in the headCheck file type and sizeAllow for stored copies and waiting
Start with the file, then the tag, then stored copies.

1. The file isn't where the tag says

  • Check: copy the href from your link tag and paste it into a browser's address bar. You should see the picture.
  • Why it fails: a typo, a wrong folder, or a file that was never uploaded.
  • Note: when no icon is listed and no file exists at the usual root spot, browsers can end up logging unnecessary 404 entries on the server1. A 404 is the "page not found" reply.

2. The tag is missing, or in the wrong place

  • Check: view the page source and find the link line inside head.
  • Why it fails: the line sits in the body, or a template leaves it off some pages.
  • Note: an old file at the root won't win. Wikipedia says a listed icon beats the root file in modern browsers1.

3. The browser can't use the file type

  • Check: which format did you link?
  • Why it fails: old Internet Explorer versions (5 to 10) read only ICO files1, and the browser has no SVG favicon support1.
  • Note: if the best match can't be used, a browser proceeds to the next-most appropriate icon2. So list a fallback.

4. Two icons are fighting

  • Check: count your rel="icon" lines.
  • Why it fails: when icons tie, MDN says the last one listed is used2. The one you wanted may be listed first.

5. The browser kept an old copy

A stored copy is one possible reason a favicon "won't update".

  • Check: open the site in a private window, or a different browser. If the new icon appears there, a stored copy is one possible explanation. It isn't proof.
  • Why it happens: HTTP is designed to cache as much as possible. Even with no Cache-Control header, responses will get stored and reused if certain conditions are met3. A cache is a saved copy kept to avoid downloading a file again.
  • Whose copy: a private cache is tied to a specific client, typically a browser3. Yours and a visitor's can differ.
  • How long: a stored copy is fresh while it can be reused, and stale once it has expired3. Until then the browser may not ask for the new file.
  • Trade-off: you could give the new icon a new file name, so the browser sees a new address. But Google says the favicon URL must be stable and shouldn't change frequently4. Don't rename it over and over.

6. The address bar isn't where the icon lives

  • Check: look at the tab, not the address bar.
  • Why: in most modern browsers, MDN says, the address bar now shows an HTTPS status image where the favicon used to be5.

7. Google still shows the old one, or none

Search results run on a different clock. The full rules are in Google's icon requirements. The common causes:

  • Waiting. A recrawl may take from several days up to several weeks4.
  • Blocked. A robots.txt rule, or any other block, can stop Google fetching the home page or the icon file4.
  • Wrong kind of address. A subdirectory-level home page isn't supported4. Only domain and subdomain home pages are.
  • Bad shape or size. The icon must be square and at least 8x8 pixels4.
  • No promise. Even if every guideline is met, Google says that doesn't mean a favicon will appear in Google Search results4.
  • Replaced. If Google finds inappropriate imagery in a favicon, it replaces it with a default icon4.

8. Phone home screens ignore your tab icon

  • Why: Apple's iOS does not use the standard icon link type to pick a home screen icon2. With no custom icon supplied, the phone shows a page thumbnail instead1.
  • Fix: add an Apple touch icon. The home screen icon guide shows how.

Still stuck?

Go back to how to add a favicon and compare your tags line by line. Check sizes and formats too.

References

  1. Favicon, Wikipedia
  2. rel attribute values (HTML attributes), MDN Web Docs, Mozilla
  3. HTTP caching, MDN Web Docs, Mozilla
  4. Define a favicon to show in search results, Google Search Central
  5. Favicon (Glossary), MDN Web Docs, Mozilla