If your favicon is not showing, first inspect the icon URL declared by the page and confirm that it returns the intended image. Then check competing icon declarations, deployment paths, and caching.
A cache refresh cannot repair a missing file or a URL that returns your application’s HTML. Work through the checks below in order, stopping when you find the cause.
For a public website, start with the FaviconIcon checker to review the setup exposed by your page. Use browser developer tools for local cache state and requests blocked in your own browser.
Identify where the icon is missing
| Where you see the problem | What to inspect first |
|---|---|
| Browser tab | The page’s icon links and the image they reference |
| Only one page or nested route | The icon URL resolved from that page |
| Google Search results | The homepage declaration and Google’s favicon requirements |
| A saved home screen shortcut or installed app | The Apple touch icon or web app manifest |
Start with the browser tab checks below. If the tab already looks correct, go to the sections on Google Search or home screen icons.
1. Inspect the favicon declaration
Open the affected page and inspect its rendered <head> in developer tools. Find the <link> elements whose rel includes icon.
For a file served at the domain root, a basic declaration is:
<link rel="icon" href="/favicon.ico">For a PNG file, declare its actual format and dimensions:
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">Use the path where your file is actually served. These examples assume root-level files; an app deployed under a subfolder may need a prefix.
Inspect both the initial page source and the rendered head if your application manages metadata dynamically. A component, theme, plugin, or framework configuration may add a declaration after the initial HTML loads.
Write down the exact icon URLs you find. Those URLs determine the next check.
2. Confirm that the URL returns an image
Open the referenced icon URL directly. Then inspect its request in the browser’s Network panel.
Check the request URL, final URL after redirects, status, response headers, and image preview. In Chrome DevTools, the Headers, Preview, and Response tabs expose these details. developer.chrome.com
| Result | What it suggests | Next action |
|---|---|---|
404 | The resource is missing at that URL | Correct the path or deploy the file |
401 or 403 | Access is restricted | Review authentication and asset access rules |
| Redirect to a login page | The icon is behind a login flow | Serve the intended public icon without that redirect |
200 with the expected image | The file is reachable | Continue with declarations and cache checks |
200 with HTML | A page or fallback is being served | Correct the asset path or routing rule |
| Image that is visibly old | The response itself is outdated | Compare the deployed file and relevant caches |
A successful status code alone does not prove that the favicon was delivered. A single-page app fallback can return index.html for a missing asset path. Netlify’s rewrite documentation describes this behavior for its SPA fallback rules. Netlify Docs
Check the body as well as the Content-Type. That header identifies the response’s media type, so text/html at an icon URL deserves investigation. MDN
If the response is your app’s HTML, deploy the missing asset or make sure static assets are served correctly before the page fallback applies.
3. Correct the path for the page and deployment
A relative path and a root-relative path can request different files.
For a page at https://example.com/docs/setup/, with no custom HTML base element:
| Link href | Requested path |
|---|---|
favicon.ico | /docs/setup/favicon.ico |
/favicon.ico | /favicon.ico |
/app/favicon.ico | /app/favicon.ico |
A leading slash starts at the domain root. It does not automatically include your application’s deployment subfolder. MDN
If the icon exists at /app/favicon.ico, changing the link to /favicon.ico still points to the wrong location.
Compare the filename character by character, including capitalization and extension. Also check whether your HTML has a <base> element that changes URL resolution.
For a built application, inspect the production HTML and the actual production request. Source code alone may not show the final URL after the build tool’s transformations.
Use the framework guide that matches your project:
4. Remove unintended competing declarations
Multiple favicon links can be correct. You may deliberately offer an ICO file, PNG sizes, or different icons for different color schemes.
Browsers select among icon links using attributes including type, sizes, and media. When candidates are equally suitable, the later one is selected. MDN
Look for declarations that point to:
- A starter template icon.
- A previous brand’s icon.
- A file that no longer exists.
- Another icon added by a theme or component.
Fix the source that creates the unwanted link. Editing the DOM in developer tools is useful for diagnosis, but the change disappears when the page reloads.
Keep intentional size and format variants. Confirm that each one contains the current artwork.
5. Find which cache is serving the old version
Investigate caching after the URL and declarations are correct.
Compare a fresh browser session
Open the page in another browser or a fresh browser profile. If it shows the new icon while your original profile does not, continue investigating local browser state.
In Chrome, enable Disable cache in the Network panel while debugging and reload. This helps diagnose HTTP caching; it is not a guarantee that every piece of browser favicon state has been reset. developer.chrome.com
Check the page and image separately
| Observation | Next check |
|---|---|
| The page still declares the old icon URL | Confirm the deployed HTML version |
| The image URL itself serves old artwork | Compare the deployed asset and CDN response |
| A fresh profile works but the original does not | Investigate browser cache and profile state |
| The app uses a service worker | Inspect the HTML, manifest, and other responses it may serve |
A CDN cache is separate from your browser cache. If the CDN serves an outdated icon or HTML document, use the hosting provider’s cache controls for the affected resources. Review cache headers when deciding how future updates should propagate. MDN
Check service workers when your app uses them
A service worker can keep serving an older page or manifest that references an old icon. In Chrome’s Application panel, inspect Service Workers and Cache Storage. Bypass for network provides a diagnostic comparison without relying on the worker’s responses.
Correct the app’s update or cache strategy if that comparison identifies the problem. Do not assume every browser routes every favicon request through a service worker. developer.chrome.com
Keep a stable URL after debugging
For a controlled diagnostic test, you can temporarily publish the new image under a different filename and update its link. Compare that result with the original URL to investigate stale responses.
Avoid generating a different favicon URL on every page load. Once the issue is resolved, use a stable URL and a deliberate cache policy.
6. Check the image and security policy
If the expected URL opens but the icon is still unusable, inspect the file itself.
Check that the file is an actual image in the declared format. Renaming a PNG file to .ico does not convert its contents. Match any declared PNG dimensions to the image’s real dimensions.
Preview the artwork at a small size on light and dark backgrounds. A transparent image with very low contrast can appear blank even when it loads correctly. If needed, generate a simpler version with the favicon generator or image converter.
Also inspect the browser Console for a Content Security Policy error. The img-src directive controls allowed image and favicon sources; default-src is the fallback when img-src is absent. An icon that opens directly may still be blocked when requested by a page with that policy. MDN
Adjust the policy to allow the specific source your icon needs, while keeping the rest of the site’s policy intact.
7. Check the deployed environment
If the icon works locally, compare the local and production responses directly.
Confirm that:
- The deployment contains the new icon files.
- The published HTML references those files.
- The asset URL includes the correct deployment prefix.
- Asset requests are not redirected to authentication or rewritten to the app shell.
- The production filename matches the reference exactly.
- Both the homepage and a direct visit to a nested route use the intended icon.
- The live domain is serving the deployment you meant to publish.
For Vite projects, preview the production build before deploying, then repeat the URL checks on the public site. The React and Vite guide includes the base-path and manifest examples.
8. Handle Google Search separately
If the browser tab is correct but Google Search still shows a missing or old favicon, check the homepage and crawler access.
Google’s requirements include a homepage icon declaration, a square representative image in a supported format, and crawl access to the homepage and favicon. Googlebot needs access to the homepage; Googlebot-Image needs access to the icon.
Keep the favicon URL stable. Google treats the hostname as the site boundary, so separate subfolders on the same hostname do not receive independent search-result favicons.
After fixing the setup, you can request indexing of the homepage in Search Console. Recrawling and processing may take days to weeks, and meeting the requirements does not guarantee display. developers.google.com
Refreshing your own browser does not trigger that processing.
For a detailed search-specific investigation, follow the Google Search favicon troubleshooting guide.
9. Check home screen icons separately
For an Apple home screen shortcut, inspect the Apple touch icon declaration:
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">Use your real deployment path. Apple Web Clip icons use apple-touch-icon, so checking only rel="icon" can miss the relevant asset. MDN
For a web app that uses manifest icons, inspect the linked manifest and every relevant icons[].src. Relative icon paths resolve against the manifest URL. In Chrome, the Application panel’s Manifest section helps inspect those icons and loading errors. MDN
Test a newly created shortcut or fresh installation as part of diagnosis. Treat an existing installed icon as a separate test from the current browser tab.
Frequently asked questions
Does my favicon have to be named favicon.ico?
No. An explicit icon link can point to another filename or path. Use a valid image and a URL the browser can reach.
Why is my favicon missing only on some pages?
Compare the final icon URL on a working page and a failing page. Document-relative paths, route-specific metadata, or different templates are useful places to start.
Does an HTTP 200 response mean the favicon works?
No. Verify that the response body contains the intended image. An application fallback or login page can also return a successful status.
Can an online favicon checker clear my browser cache?
No. An online checker can review publicly accessible declarations and files. Use your browser’s developer tools to investigate local state.
How long should a favicon update take?
There is no universal delay. The response served by your host, browser state, installed shortcuts, and Google Search processing are separate factors. First identify which one still contains the old icon.
Check your favicon again after the fix
Run your public page through the favicon checker, open the declared image URL, and confirm the result in a fresh browser session.
If you need replacement icon files, create a favicon package and install it using the guide for your framework.