tabplate.field guide
Website ↗

When a favicon is missing

A letter is a fallback, not a broken link. Here is how icons are found.

Where the icons come from

Tabplate can use built-in artwork, uploaded images and Chrome’s local favicon store. Optional direct website fetching can discover other favicons and site icons. It is off by default, including for older settings that predate the choice.

If you see an initial instead

  1. Check that the link is right

    A saved address can work perfectly even if its site has no usable icon.

  2. Check Site icons settings

    If you want automatic discovery, explicitly enable fetching from websites and accept Chrome’s optional site-access request.

  3. Refresh the icon

    Use the available icon refresh action for the link or refresh website icons from settings. A cached failure may otherwise remain for a while.

  4. Expect a few fallbacks

    A site can block requests, omit icons, return an incompatible file or require authentication. Tabplate keeps a letter fallback rather than blocking the page.

What does fetching share?

Icon requests go directly to the saved site and its discovered asset servers. Those services can see your IP and the requested asset address. Tabplate omits cookies, credentials and referrers. It does not send private paths from the saved page to discover the icon.

Tab rail vs saved linksThe right-side rail mirrors favicons supplied by Chrome for open tabs. It does not need direct website icon fetching. A good rail favicon and a letter on a saved link can therefore coexist.

Esc close · Searches only this guide, locally.