Chrome Default Favicon Globe Icon: What It Means

You open a new tab in Chrome, and instead of your logo you see a small gray globe. It looks like a placeholder, and that is exactly what it is. The Chrome default favicon globe icon is the browser's fallback when it cannot find or load a valid icon for a page.

This article explains what that globe means, why Chrome picks it, and how to replace it with your own favicon. We will keep the focus on the globe itself, not on general cache troubleshooting.

What the Chrome default favicon globe icon actually is

Chrome does not ship a single hard-coded globe for every site. The globe is a generic placeholder that appears when no usable icon is available. It is the visual equivalent of an empty slot in the tab bar.

The HTML standard defines how a page declares an icon: a <link rel='icon'> element in the document head. You can read the specification at WHATWG HTML: rel=icon. When that declaration is missing, broken, or points to a file Chrome cannot decode, the browser falls back to the globe.

Why the globe appears instead of your icon

Most cases fall into a few predictable buckets. Here are the common ones:

• No icon declared and no /favicon.ico. Chrome may request /favicon.ico at the site root. If that file is missing, the globe stays.
• The link tag points to a 404. A typo in the path or a file that was never deployed produces the same result.
• The format is unsupported or corrupt. A truncated ICO or an SVG with invalid markup can fail to render.
• The page is a local file or a restricted context. Some internal Chrome pages and local files have no icon, so the globe is expected.

Notice that none of these require a deep cache investigation. The globe is usually a signal that the icon was never successfully resolved in the first place.

How Chrome chooses between your icon and the globe

Chrome reads the icon links in the document head and picks a candidate it can decode. If you provide an SVG and a PNG, the browser uses the format it supports best. If every candidate fails, the globe is shown.

A minimal, reliable declaration looks like this:

<link rel='icon' type='image/svg+xml' href='/favicon.svg'>
<link rel='icon' type='image/png' sizes='32x32' href='/favicon-32.png'>

This gives Chrome two chances to succeed. For a deeper look at how the link element is structured, see our guide to the favicon link tag.

Best practices to avoid the globe

You do not need a dozen files to get rid of the globe, but you do need at least one valid, reachable icon. A few practical rules:

1. Declare an icon explicitly in the head instead of relying on the implicit root request.
2. Verify the file actually returns HTTP 200, not a redirect to an HTML error page.
3. Keep a PNG fallback alongside SVG for older or stricter parsers.
4. Test in a fresh Chrome profile or incognito window so a previously cached globe does not confuse you.

If your icon is declared correctly but Chrome still shows the globe, the cause is often a stale cached entry rather than a missing file. Our article on favicon not showing in Chrome covers that specific cache behavior.

Conclusion

The globe is not a bug. It is Chrome telling you that no usable icon was found. Declare a valid rel='icon' link, confirm the file is served correctly, and the globe disappears. Start with one working SVG or PNG, then expand to the full icon set once the basics are solid.