Help Centre

Iconfind checks the icons a website declares and reports which are present, missing, or misconfigured. Below are answers to the most common questions. This is a new tool — if something is not covered here, see the contact section at the bottom.

Getting started

Using Iconfind takes one step: paste a URL into the input field on the Check a site page and click Check. The tool will:

  • Fetch the page's <head> and read every icon declaration — favicon.ico, apple-touch-icon, <link rel="icon"> with its sizes and type attributes.
  • Probe the two convention paths that browsers request without being declared: /favicon.ico and /apple-touch-icon.png at the site root.
  • Request each icon file and report what came back — present with real pixel dimensions, present in the wrong format for what it claims, or missing entirely.
  • Show a verdict for each client: browser tab, search results, and iOS home-screen bookmark.

No account or payment is needed. The check is free and the results disappear when you leave the page.

Frequently asked questions

Why is my favicon not showing in Google search results?

Google uses the favicon that it last crawled and cached for your site, not necessarily the one currently being served. There are several reasons your icon may not appear:

  • Google has not recrawled your site. After changing your favicon, it can take days or weeks for Google to recrawl and display the new one. You can request recrawling through Google Search Console.
  • The icon is not declared in a way Google recognises. Google looks for a <link rel="icon"> declaration with a valid image at the specified URL. A file sitting at /favicon.ico without a declaration in the <head> is not guaranteed to be picked up. Use Iconfind to check whether your page declares the icon.
  • Wrong size or format. Google's favicon specifications recommend a 16x16 or 32x32 PNG or ICO file. Very large images or unusual formats may be ignored.

Iconfind can tell you whether the declaration and file are present — the rest is up to Google's crawl schedule.

Why is my favicon not updating after I changed it?

This is the most common icon issue. Three things can cause a stale favicon:

  • Your own browser cache. Your browser has cached the old icon. Try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or clear the browser cache. For aggressive testing, open a private/incognito window — those start with a clean cache.
  • The old file is still at the old path. If you renamed the icon file but kept the old declaration pointing at the old URL, the browser loads the old file. Update the <link> tag to point to the new file path.
  • CDN or proxy cache. If your site sits behind Cloudflare, Varnish, or another caching layer, the old icon may be served from cache. Purge or invalidate the icon URL through your CDN dashboard.

Run Iconfind to confirm that the new icon file is actually being served at the expected URL. If Iconfind shows the new icon correctly, the issue is browser or CDN caching, not the file itself.

What sizes should my favicon be?

There is no single standard, but the modern recommended set covers the main use cases:

  • 16x16 — Standard browser tab icon. Expected as favicon.ico or a <link rel="icon"> with sizes="16x16".
  • 32x32 — High-DPI (Retina) browser tab and browser taskbar. Recommended for <link rel="icon" sizes="32x32">.
  • 180x180 — Apple touch icon for iOS home-screen bookmarks. Declared as <link rel="apple-touch-icon" sizes="180x180">.
  • 192x192 — Android Chrome splash screen icon (part of the Web App Manifest).
  • 512x512 — Android Chrome splash screen (large variant, also in the Web App Manifest).

If you only have one icon, a properly declared 32x32 PNG covers most desktop browsers. For full coverage you need multiple declarations. Iconfind will show you which sizes your page actually declares and which files exist.

My site icon shows blank in the browser tab — what's wrong?

A blank or default icon in the browser tab usually means one of these:

  • No favicon is declared. Many browsers show a blank page icon when no <link rel="icon"> exists and the root /favicon.ico returns 404. Run Iconfind to check whether /favicon.ico is reachable.
  • The declared icon file returns 404 or an error. The <link> tag exists but points to a file that does not exist or cannot be loaded. Iconfind will flag this as missing or error.
  • The file is served but in an unsupported format. Some servers serve an SVG or JPEG where the browser expects a 32x32 ICO or PNG. Iconfind reports the actual format detected so you can see the mismatch.
  • The path is relative and resolved incorrectly. If your page is at a subdirectory like /blog/page.html and your favicon link is href="favicon.ico" (relative), the browser looks for /blog/favicon.ico, not /favicon.ico. Use an absolute path (/favicon.ico) to avoid confusion.

Paste your URL into Iconfind — the results will tell you exactly which file is missing.

Apple touch icon missing — how do I fix it?

When a user adds your site to their iPhone home screen, iOS looks for an apple-touch-icon. If it is missing, the bookmark shows a generic blank tile.

To fix it, add this declaration to your page's <head>:

<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">

Then place a 180x180 PNG file at /apple-touch-icon.png on your server. The file must be a PNG — iOS will not accept ICO or other formats for touch icons.

Iconfind checks both the declared Apple touch icon (if present) and the convention path /apple-touch-icon.png at the site root, because iOS also probes that path even when no declaration exists. If neither is found, the verdict will say No touch icon in the iOS bookmark column.

Why does Iconfind report my site as unreachable?

If your site is hosted on Cloudflare's network, Iconfind — which also runs on Cloudflare Workers — cannot open a connection back into the same Cloudflare network. This is a platform limitation, not a problem with your site's configuration.

The symptom: every icon for your site reports as error or unreachable. You can verify that your icons are actually working by checking them from outside Cloudflare (e.g. using curl from a non-Cloudflare server, or checking the icon URLs directly in a browser).

This limitation is specific to Cloudflare-to-Cloudflare connections. Sites on other providers (AWS, DigitalOcean, Netlify, standard hosting) do not have this issue.

Known limitations

  • Cloudflare-to-Cloudflare connections. As described above, if the target URL is behind Cloudflare, the platform cannot probe it. Those hosts are reported as unreachable even when the icons are actually present.
  • Single snapshot only. Each check is a one-time fetch. Iconfind does not monitor sites over time, send alerts, or re-check URLs automatically.
  • No icon generation or design. Iconfind only reports what the server serves. It does not create, resize, or suggest icon designs.
  • No authentication-supported checks. Iconfind cannot check URLs that require login, authentication headers, or cookies. It accesses only publicly accessible pages.
  • Paid tiers are not yet available. The Pro and Team pricing tiers listed on the Pricing page are planned. No payment system is connected yet. The Free tier works now and needs no payment details.
  • No accounts, no saved history. Iconfind does not store results. Each check is ephemeral. There is no way to return to a previous report.
  • JavaScript-rendered icons not detected. Iconfind reads the raw HTML from the initial server response. If a page injects icon declarations via JavaScript after page load, those may not be detected.

What Iconfind is not

Iconfind is a diagnostic tool. It is not a favicon generator, not a design service, not a monitoring solution, and not a substitute for testing your site across multiple browsers. It reports what is served, not what should be served.

How to contact us

Support is not yet reachable by email. No mailbox or contact form is set up for this service. The business has no registered legal entity and no support infrastructure beyond this Help Centre. If you need to reach the operator, use the channel through which you obtained access to this tool.

In the meantime, these resources may help:

  • Browse this Help Centre — the FAQ above covers the most common icon issues.
  • Run a fresh check on your URL — the results often make the problem obvious.
  • If you found a bug or have a feature request, please record it through the channel where you accessed this tool. The operator reviews all feedback.