Favicon without favicon.ico: why tabs still show an icon

Contents
- Why an icon showing up with no favicon.ico feels strange
- How to check a site's icon declarations by hand
- How a browser picks one icon out of several: and why these differences happen technically
- Comparing quality, format, and use cases
- Common sticking points
- Copyright and legitimate use
- How It Differs from Similar Tools and Platforms
- Summary
- Frequently Asked Questions
Some sites show an icon in the tab even though nobody ever uploaded a favicon.ico file. Other sites clearly do have a favicon.ico, yet the tab shows a different image. Neither case is broken.
When a browser looks for a favicon, it doesn't start by hunting for a file name. It first reads the page's head to see what's declared there as "this is the icon." This post covers that lookup order, and how to track down every icon a site is actually hiding under one name or another.
Summary ① Browsers check the icon declarations in the head first (rel="icon", rel="apple-touch-icon", and so on), and only try the default path /favicon.ico when nothing is declared. ② That's why it's common for a site to show a tab icon with no favicon.ico at all — a different declared file is being used instead. ③ A single real site often declares several icons for different purposes at once, and this tool finds all of them and shows them as a list.
Why an icon showing up with no favicon.ico feels strange
A lot of people learn that "favicon = favicon.ico." And for a while that really was true — you dropped one favicon.ico in the site root and you were done. So even today, developer communities get "why doesn't my icon show up when I put favicon.ico in the root?" alongside the exact opposite question: "I deleted favicon.ico, so why is the icon still showing?"
Both questions start from the same misunderstanding: treating favicon.ico as the one right answer. In practice, site frameworks and CMSs plant an icon link tag directly in the head instead of — or in addition to — favicon.ico. When that tag is there, the browser has no reason to request /favicon.ico at all.
So a developer opens the Network tab in developer tools, sees no favicon.ico request, and concludes the favicon is broken. In reality, the browser simply never needed to request that path, because the declaration in the head had already delivered the image it wanted.
The same misunderstanding runs in the other direction too. Someone redesigns a site, swaps out the head tags, but leaves the old favicon.ico sitting on the server. Now the tab shows the new icon, yet if you type yourdomain.com/favicon.ico into the address bar, you get the old image. Both files exist, and neither is wrong. The browser just never looked at that path when picking what to draw in the tab.
This actually causes confusion on teams. A designer builds a new icon set from the new logo and hands it over, and the developer replaces the files while leaving the head tags alone and keeping the file names identical. If the browser or a CDN has the previous files cached, you keep seeing the old image for a while. And if the head tag's href still points at the old file name, then no matter how many times you upload new files, the old file at that path keeps getting loaded. The visible symptom (nothing changed) looks the same, but the thing you need to fix is completely different in each case. That's why confirming "what does the head point at right now?" is the starting point for fixing it.
All of this narrows down to one question: by what criteria, and in what order, does a browser decide which image to use as the icon? The next section covers how to check that for real.
When the icon in search results doesn't match the tab icon
There's another situation that adds to the confusion: the site icon that shows in a list of search results looks different from the icon that appears in the browser tab after you click through.
Those two icons were fetched at different times for different purposes. The search result icon is a cached value the search engine read the last time it crawled the site. The tab icon in front of you is a value the browser read just now. If the site swapped its icon in between, it's only natural that they look different. There can be a lag before the search engine refreshes its cache, so it's common to see "I definitely changed it, but search results still show the old image."
If you don't know this, you get stuck all over again at "I want to save the search result icon, but it's different from the tab icon, so which one do I download?" What you actually need isn't the cache the search engine read earlier — it's the original: what this site declares in its head right now. Once you've checked the source, you can predict how the results will change when the search engine catches up later.
How to check a site's icon declarations by hand
The most accurate method is to look at exactly what the browser sees: open the page's HTML source directly. Here's the order.
- Open the site you want to check.
- Right-click in the address bar and choose "View Page Source," or put
view-source:in front of the URL and load it again. - Press Ctrl+F (Cmd+F on a Mac) and search for "icon".
- Inside the head tag, look at each link tag whose rel attribute contains icon.
You'll often find more than one. rel="icon" may show up on several lines, mixed with tags that have entirely different names, like rel="apple-touch-icon" and rel="mask-icon". Each tag carries the actual file path in href, plus size and format hints in sizes or type when they exist.
When the href is a relative path
The part that trips people up is the href value. It's often written as a relative path with no domain in front, like href="/assets/icon-32.png". You have to add the domain of the site you're viewing to the front yourself to get an address you can actually open.
For example, if you're checking example.com and the href is /assets/icon-32.png, the real image address is example.com/assets/icon-32.png. If the href is just a filename with no slash, like icon-32.png, it's even more confusing, because you have to rebuild it relative to the path of the page you're currently on. With one tag, this takes a few seconds. Past five or six tags, combining each one and pasting it into a new tab becomes pure repetitive labor.
When you need to compare several sites at once
If you're only looking at one site by yourself, viewing the source is survivable. The trouble starts when the number of sites grows. To compare the icon setups of three or four competitors side by side, or to check that the icons across your own subdomains are consistent, you have to repeat the whole loop once per site: open the source, scan the head, and rebuild the relative paths.
The thing people most often lose track of in that loop is which file came from which site. With several tabs open and comparisons going one by one, it's easy to mix up which file belonged to which site. Filenames overlap constantly too — plenty of sites just call it icon.png — so files get jumbled in your downloads folder as well. Switching URLs to look each one up and saving the results in a labeled way as you go is ultimately the most reliable way to keep things straight.
Double-checking with the DevTools Network tab
Instead of viewing the source, you can open the Network tab in the developer tools (F12), reload the page, and filter for "icon". That shows you the files this browser actually requested and received.
This method only shows what was actually used by this browser, under these conditions. A declaration that's in the head but only used by another browser or under other conditions — Safari's mask-icon, for example — won't even be requested when you open the page in Chrome, so it won't appear in the list. To see every icon declaration a site has, you still have to read the source code from top to bottom.
Manually, this is where it gets tedious. Plenty of sites have more than ten tags in the head, and if the href is relative, you have to assemble the real file address yourself and paste it into a new tab one by one just to see what the image looks like. For SVG files like rel="mask-icon", opening one shows only a black silhouette with no color, which makes you wonder why it counts as an icon at all. And if a site has no declarations in the head, this method only confirms that there are none — figuring out what the browser actually uses means opening /favicon.ico separately.
The more declarations a site has, the more this becomes a manual, tag-by-tag cross-check. It's hard to tell just from the names which one is for tabs, which is for the iOS home screen, and which is for the Safari mask icon. Only after repeating three tasks — assembling relative paths, identifying file formats, and sorting out purposes — once per tag do you finally get the full picture: "so this is how this site sets up its icons."
Free — just enter a URL, no sign-up, and get every declared icon as single files or a ZIP

How a browser picks one icon out of several: and why these differences happen technically
The process a browser follows to find a favicon isn't random. It follows a fixed order. Here's the core of it: the browser first checks whether the head of the page you're viewing has any icon-related link tags. Declarations like rel="icon", rel="apple-touch-icon", and rel="mask-icon" count. If even one of these declarations exists, the browser picks whichever one fits the situation and uses it. Only when there are no declarations at all does the browser try /favicon.ico, the site's default path, as a last resort.
Once you know this order, the two questions from the previous section answer themselves. The reason an icon shows up in the tab even though you never uploaded a favicon.ico file is that a rel="icon" declaration pointing to a file with a different name was already in the head. From the browser's point of view, the moment it finds that declaration, it has no reason to keep looking. The /favicon.ico path never even gets tried. So whether a file exists at that path makes no difference to the result.
Conversely, if a site has no icon declarations in its head at all, then the browser really does request /favicon.ico. If a file actually exists at that path, it becomes the tab icon. If not, the tab shows no image or the browser's default icon. In other words, /favicon.ico isn't a "default that always gets checked" — it's the last resort that only gets checked when there are no declarations. Get the order backwards and you'll keep looking in the wrong place every time you diagnose a site.
There's one more important point here. When the head holds more than one declaration, those declarations usually aren't competing with each other — they serve different purposes. If you actually open github.com's head and look, you'll find six icon declarations at once, all with different names and formats: fluid-icon (PNG), mask-icon (SVG), alternate icon (PNG), icon (SVG), favicon.ico (ICO), and og:image (PNG). These six aren't candidates where one substitutes for another. They're separate images that get used in different places to begin with.
The fluid-icon is used not in browser tabs but in some macOS browser shells that wrap a page like a desktop app. The mask-icon is the SVG Safari references when it renders a pinned tab or Dock icon as a single-color silhouette. It carries only shape, with no color information, so it's normal for it to look like a black silhouette when you open it. The alternate icon and icon (SVG) are often prepared together as vector icon candidates that modern browsers can display sharply at any scale. favicon.ico is the backward-compatibility file for older environments that don't support these newer formats. og:image isn't a favicon at all — it's the representative image that appears as a preview when a link is shared on social media or a messenger app such as KakaoTalk or WhatsApp, and its purpose is different from a tab icon's from the start.
The reason the roles split this way is that screens and display environments each have their own requirements. A browser tab has to render fast in a tiny space. Safari's mask icon has to be built on the assumption that it will be recolored with the system theme color, with no colors of its own. An Apple touch icon added to the iOS home screen only looks natural when it's filled edge to edge as a square with no padding, like an app icon. Since it's practically impossible to make a single image file that satisfies all of these conditions, sites prepare separate files optimized for each spot from the start and declare them side by side in the head.
Website Favicon Downloader: Every Declared Size puts this principle to work directly. Enter a URL and it finds every icon-related tag declared in the head and lists them all. If a site has no declarations at all, it also tries the default path, /favicon.ico. Instead of opening view-source yourself, hunting down each rel attribute one by one, resolving the relative path in href against the real address, and opening it in a new tab to check, you get all of that in a single lookup. From the results, you can grab just the ones you need one at a time, or download everything as a ZIP at once.
Why not just standardize on a single favicon.ico
By this point you're probably wondering, "Wouldn't it be much simpler to just standardize on one favicon.ico?" There really was a time when things worked that way. The reason so many sites now line up multiple declarations is that the number of places a favicon gets used has grown far beyond what it used to be.
In the past, the only place a favicon showed up was the browser tab. Now, on top of tabs, there are iOS and Android home screen icons, Safari pinned tabs and Dock silhouettes, browser bookmark lists, search result listings, and social media share previews. Each spot has different requirements — a square image with no padding, a silhouette with no color, a vector that stays sharp even at small resolutions — so no single file can satisfy every spot anymore. The growing number of declarations isn't an attempt to be complicated. It simply reflects the fact that the places where icons get displayed have diversified.
Put another way, the number of icon declarations in the head is roughly proportional to the number of display environments a site cares about. A site with only one declaration has really only covered the tab. A site with more than six has prepared separately for tabs, mobile home screens, Safari, and social sharing. That number alone gives you a sense of how many channels the site was built with in mind.
Why file extensions and file formats don't line up neatly
Another confusing point is file format. The file a rel="icon" tag points to isn't always ICO. It can point to a PNG, or to an SVG. The rel value itself only means "this thing acts as an icon." It doesn't force a file format. The actual format has to be determined from the extension of the file the href points to and from the type attribute written on the tag.
That's why, when you're scanning by eye, it's easy to assume "it's rel="icon", so it must be a .ico file," then see that it's actually .png or .svg and have to double-check — over and over. This is also why the tool shows the format next to each entry in the list.
Why this structure is useful when you're investigating a site
Once you know this lookup order, the way you investigate a site changes. Instead of just counting "how many icons are there," you can read "which display environments this site cared enough to prepare for."
For example, on a site with no apple-touch-icon declaration, adding it to the iOS home screen may fall back to a default icon the browser generates itself, or to a screenshot of the page. On a site with no mask-icon, Safari fills that spot with a different icon when you open it as a pinned tab. These differences are clues to how carefully the site's operator manages each channel. You can read them the same way whether you're auditing your own site or looking at a competitor's site for reference.
Comparing quality, format, and use cases
Everything that goes by the name "icon" is actually a different format built for a different job. Here's a table of what each file is for.
| Declaration | Format | Where it's mostly used | Color info |
|---|---|---|---|
| icon (classic) | ICO/PNG | Browser tabs, bookmarks, the default in older environments | Yes |
| icon (SVG declaration) | SVG | Modern browser tabs, crisp at any scale | Yes |
| apple-touch-icon | PNG | iOS/iPadOS home screen icon | Yes |
| mask-icon | SVG | Safari pinned tab and Dock icon (recolored with the system color) | None (silhouette) |
| alternate icon | PNG | Fallback for environments that don't support icon (SVG) | Yes |
| og:image | PNG/JPG | Link preview when shared on social media or messenger apps (not a favicon) | Yes |
| Default path (favicon.ico) | ICO | Last resort, only tried when there's no declaration at all | Yes |
As the table shows, if you use a file with no color information, like mask-icon, in place of another icon, all you get is a silhouette that looks wrong. And og:image isn't a file meant to sit in a favicon slot, so even if Website Favicon Downloader: Every Declared Size lists it alongside the others, it isn't the right file to grab for a tab icon. Picking the file that fits the slot is the whole game.
Read that table backward and you also get a natural answer to "which file should I download right now?" If you're building a mockup of a browser tab, take an icon-family file. If you're showing how the site looks added to an iOS home screen, take apple-touch-icon. If you're recreating Safari's pinned tab UI, take mask-icon. On the other hand, if you start without a purpose and just grab everything, you'll be confused again later about which file was for what. It helps to put the slot in the file name when you save each one.
Format differences matter in practice too. An ICO file is a container format that can hold several resolutions in a single file, so it covers a wide range of older environments, but different editing programs open it in different ways. PNG opens directly in most image editors and is easy to edit. SVG is vector, so it doesn't pixelate when enlarged, but keep in mind that when it has no color, like mask-icon, a regular viewer may show it differently from what was intended.
Common sticking points
| Symptom | Cause | Fix |
|---|---|---|
| No icons appear in the list at all | The site has no icon declarations in head whatsoever | The default /favicon.ico path is tried too, so if that's missing as well, the site really doesn't have an icon |
| The mask-icon file I downloaded is just a black silhouette | That's normal: the SVG has shapes only, with no color info | Safari recolors it with the system theme color, so add a background color yourself if you want to view it as an image |
| I downloaded favicon.ico, but it's not the image shown in the tab | Because head has declarations, the browser never looks at /favicon.ico in the first place | The file actually used in the tab is the one from the rel="icon" declaration in head, so check that entry |
| og:image shows up in the list too and it's confusing | og:image is for social share previews, and its tag structure resembles a favicon's, so it gets listed together | It's a share preview image, not a tab icon, so download it with that purpose in mind |
| I downloaded the ZIP, but some files have different sizes | The site prepared separate files at different actual sizes for each slot (tab / home screen / mask) | That's normal, so just pick the file that fits the slot you need |
| The icon in search results looks different from the file I just downloaded | The search engine cached a value it read earlier and it differs from what's in head now (the site swapped icons in the meantime) | For the accurate value right now, go with the list this tool shows, since it re-reads head |
| Same site, but the www and non-www addresses give different results | Depending on the server setup, the two addresses are treated as different pages (or redirect paths), so the head contents can differ | Enter the exact form of the address you actually visit most |
If you hit a symptom that isn't in this table, you can usually narrow the cause down by more than half just by deciding whether the problem is the file itself or whether the browser was looking at a different file all along. Rechecking the head declarations is the first thing to do.
Copyright and legitimate use
The icons you find with this tool are simply files that are declared in the head of public pages, viewed and saved as they are. But that doesn't change the fact that the copyright in those files belongs to the original creator who runs the site.
There's no problem at all with using the tool to audit the icons on a site you manage, or to check that brand assets you created display correctly across environments. On the other hand, taking another brand's logo or icon and reusing it in your own product or service, or redistributing it so it looks like your own, can lead to trademark and copyright problems.
Researching or referencing how a competitor's branding is put together is widely accepted, but that's a different matter from copying the result outright. To actually use a downloaded file, it's safest to limit yourself to your own assets or cases where the original creator has explicitly given you permission.
This tool deals only with files publicly declared on public pages, right from the start. It isn't a feature for bypassing login walls or restricted areas to pull resources you don't have access to. It just looks up, organizes, and displays files that anyone could download by opening the site in their browser — which is exactly where the principle of "public content only" comes from.
For the same reason, it's a natural fit for checking whether your own site's or product's icons are actually showing up the way you intended across environments. Verifying that old icon files aren't still sitting on the server after a redesign, or that declarations for a new channel haven't gone missing, raises no copyright issue at all.
And when you collect icons from multiple sites for design research, keep the internal reference material separate from anything you publish or redistribute. Even material you gathered for reference can turn into a copyright problem if you distribute it as if it were your own without crediting the original creator, so it's safer to think of the research stage and the actual use stage as two different things.
How It Differs from Similar Tools and Platforms
Favicon tools fall into two broad groups. One is a generator: you upload a single image, and it creates favicon files at several sizes. The other is an extractor: it finds icons that a site has already declared. They start with different inputs, too. A generator takes "the original image you have" as input, while an extractor takes "the address of the site you want to check."
You can do something similar with the Network tab in your browser's developer tools. Reload the page and filter for the word icon, and you'll see the files that were actually requested. But this method only shows what the browser requested at that moment under those conditions. It won't show, at a glance, other declarations in the head that weren't requested by that browser or environment—for example, a mask-icon meant for another browser. To see the full picture, you have to read the source and go through every rel declaration yourself.
This tool parses the head source and lists every declared item, and it also handles the fallback attempt to the default path when there are no declarations. That compresses into a single lookup what a person would otherwise have to check repeatedly across browsers and environments. It also goes beyond scanning the results: you can pick only the files you need and save them, which sets it apart from a simple lookup tool.
There are also browser extensions for favicons. They're useful for quickly seeing which file the tab you have open is actually using as its icon, but they usually focus on "the one file used by this tab." They often don't show all the other files the site has declared separately for other places (home screen, mask icon) at once. This tool instead starts with a single URL as the target, scans the entire head at that URL, and gathers every declared icon candidate in one place.
Compared with add-ons like "Import Icon from Website" that come with image editors, this tool is different in that you don't need to install anything or sign up. Just enter the URL in your browser and see the results right away. After reviewing the results, you can download only what you need individually or grab everything as a ZIP, so research and saving happen on the same screen.
This article asks a different question from the earlier post explaining "where each favicon size is used." That post covers what sizes mean—"why 16px and 180px are different." This post covers the search order—"when the browser has several declarations, which one does it look for and use first?" If you're creating new favicons, the post about sizes is the better fit. If you need to find every icon on a site that already exists, this tool and this post point you in the right direction.
Summary
- Browsers check the head for icon declarations first, and only try the default path /favicon.ico when there are none.
- That's why many sites show a tab icon even without favicon.ico—and why many sites have a favicon.ico that never gets used.
- A single real site can declare icons for tabs, Safari pinned tabs, iOS home screens, and social sharing at the same time, each in a different format.
- This tool finds every declared item and lists them, so you can save only what you need, individually or as a ZIP.
- When you actually use downloaded files, it's safest to limit them to your own material or cases where you have permission.
Free — just enter a URL, no sign-up, and get every declared icon as single files or a ZIP
Frequently Asked Questions
Is it normal for a tab icon to show up even when there's no favicon.ico?
Yes. If the page head has an icon declaration such as rel="icon", the browser uses that first. It only tries /favicon.ico as a last resort when there are no declarations at all. In other words, on a site with a head declaration, whether a favicon.ico file exists has no effect on whether a tab icon appears. If you don't see a favicon.ico request in developer tools, that doesn't mean the icon is broken—it more likely means the head declaration already took care of it. Likewise, if a favicon.ico file is sitting on the server but the browser never requests it, that's normal for the same reason.
The list shows several icons. Which one is the real favicon?
All of them are real. They're just used in different places. The icon declaration is used for tabs, apple-touch-icon for iOS home screens, and mask-icon for Safari pinned tabs. It's not that one is the main file and the rest are extras; each display context has different requirements, so they were prepared separately from the start. Pick the item that fits where you need it. If you haven't decided where you'll use it yet, it's reasonable to start with the icon family, which is the most common choice for tabs.
I downloaded a mask-icon, but it has no color—just a black silhouette. Is it broken?
No. A mask-icon is an SVG designed for Safari to recolor with the system theme color when it displays a pinned tab or Dock icon, so it's normal for the file itself to contain only shape information and no color. If you open it in an image viewer, seeing a black silhouette is by design. If you need a colored image, download a different format (icon, apple-touch-icon). If you specifically need the mask-icon, Safari will apply a color that contrasts with the background on its own, so you can use it as is.
og:image showed up in the list too. Is that a favicon?
No. og:image is the main image that appears as a preview when a link is shared on social media or in a messaging app, so its purpose is different from a tab icon. It's often written in the head near the icon declarations, which is why it can show up in the list, but it's a separate image that isn't used for browser tabs. It's usually prepared at a much higher resolution than a favicon because it's displayed large in a social card. It's best to distinguish the purpose and download only the items you need.
What do the sizes (16, 32, 180px, etc.) mean?
Small sizes are for narrow spaces like browser tabs, and larger sizes around 180px are for wider spaces like the iOS home screen. If several files are declared with the same rel="icon" but different sizes values, the browser picks the value that fits the space it needs to draw right now. For exactly what each size is used for and why multiple sizes are needed, see the separate post that covers that in detail. This post focuses less on the sizes themselves and more on which declaration the browser looks for and uses first.
Can I use an icon I found on another site for my own site?
We don't recommend it. The fact that something is public in the head and anyone can view it is a different matter from whether you can reuse the file. Copyright in the icon file belongs to the original creator, so if it isn't your own work or you don't have explicit permission, using it as is can lead to trademark or copyright problems. It's safer to limit your use to research, such as looking at a competitor's branding for reference. If you actually need an icon for a product or service, making one yourself or using material with clear usage rights will save you trouble later.
What should I do if the site shows no icon declarations at all?
That means the site truly has no icons, or there's no file at the default /favicon.ico path either. If you manage the site, it's a good idea to add at least one icon declaration to the head. With no declaration, the browser default icon may appear or the tab may stay blank, making it easy to miss among other tabs. If you want to create new favicon files at the sizes you need from a single image, use a separate tool that generates them rather than extracting them.
This article was adapted from our Korean original. Read the Korean original