Favicon Troubleshooting Guides
A systematic way to fix missing, stale, blurry, or rejected favicons.
Use this favicon guide cluster in production order
Fix the earliest failing layer instead of changing every icon file. Begin with discovery in the rendered HTML, resolve each URL, inspect the public response and decoded image, validate the manifest, and only then investigate browser, service-worker, CDN, home-screen, or search-engine caches.
The symptom identifies the likely layer. A failure on nested routes suggests relative paths; a 200 response containing HTML suggests a rewrite; a correct fresh profile with a stale existing profile suggests client cache; and a working browser tab with a missing search favicon requires a separate Google eligibility check.
Prove the public bytes
Record status, final URL, Content-Type, format, dimensions, and ICO frames. A filename and a successful HTML response are not proof of a valid image.
Separate surfaces
Browser tabs, bookmarks, Apple shortcuts, installed PWAs, and search results select and cache different assets. Test the surface that is actually failing.
Change one layer at a time
Correct the first failed check, deploy it, and retest before clearing caches or rotating filenames. This keeps the diagnosis reproducible.
Start with: Favicon Not Showing? Diagnose It in Seven Checks
Follow the request chain from HTML discovery to file response, image validity, caching, and platform-specific rules.
Use this foundational guide first, then choose the route below that matches your file format, platform, failure symptom, design constraint, or implementation layer.
Begin with this guide →Favicon Not Showing? Diagnose It in Seven Checks
Follow the request chain from HTML discovery to file response, image validity, caching, and platform-specific rules.
Favicon Not Showing in Google Search Results
Meet Google’s crawl, shape, size, stability, and homepage-discovery requirements—then allow time for recrawling.
How to Clear a Stubborn Favicon Cache
First prove the server is correct; then target the cache layer actually serving the stale icon.
Why Browsers Request /favicon.ico—and How to Stop the 404
Some clients still probe the site root even when explicit modern icons exist.
Favicon Cache Headers, Versioning and Rebrands
Control favicon caching with stable URLs, accurate Cache-Control and ETag responses, deliberate revalidation, and a safe release plan for brand changes.
Why Is My Favicon Not Showing on iPhone?
Separate Safari tab behavior from an iPhone home-screen Web Clip, then verify the Apple touch icon, public response, saved shortcut, and retained device state.
Why Is My Favicon Showing a Blank White Square?
A white square usually comes from lost transparency, white artwork on transparent pixels, an adaptive mask mismatch, or a fallback asset you never inspected.
Favicon Troubleshooting Guides questions
Use these answers to choose the correct guide or tool before changing production files.
What should I check before clearing a favicon cache?+
Verify the rendered link tags and request the final public image URL. Confirm the current bytes, format, dimensions, and cache headers first.
Why does /favicon.ico return HTML with status 200?+
A catch-all application route or rewrite is probably serving the page shell. Exempt the static asset or add an explicit root-file route.
Can a checker force Google to refresh a favicon?+
No. It can prove technical eligibility and public access, but Google controls recrawling, selection, and display timing.
From favicon idea to verified deployment
Follow one clear path through creation, inspection, installation, and troubleshooting.