How to Add a Website Tab Icon in HTML (Favicon Guide)

To put an image beside your page title in a browser tab, add a <link rel="icon"> element inside the document’s <head>. Point its href to an icon file that is actually deployed with your site:

<head>
  <meta charset="utf-8">
  <title>My website</title>
  <link rel="icon" href="/favicon.ico">
</head>

Replace /favicon.ico with the real URL and filename of your image. The small tab image is called a favicon.

#	Preview	Product	Price
1		Hobbspring 200Pcs Make a Face Self-Adhesive Stickers Cartoon 10 Designs	$9.49	Buy on Amazon

What the favicon link does

HTML treats a favicon as a separate image resource associated with the current document. The rel="icon" value tells the browser that the linked resource is an icon, while href supplies its location. The browser cannot display an icon that exists only on your computer; the file must be uploaded to the same site (or to a deliberately permitted image host) and the URL must resolve when the page is deployed.

A root-relative URL starts at the site’s domain root. Thus /favicon.ico means https://your-domain.example/favicon.ico. A path such as images/site-icon.png is resolved relative to the page URL, so it is appropriate only when your directory layout makes that path correct. Use a leading slash when you want the same root-level asset reference from pages in different folders.

#1 Best Overall

Hobbspring 200Pcs Make a Face Self-Adhesive Stickers Cartoon 10 Designs

• Unique Design: Features various cartoon facial features including eyes, noses, mouths, and beards in multiple expressions. Perfect for creating funny faces and encouraging creative character design during playtime and learning activities.
• High Quality Material: Made from , - paper with inks. The self-adhesive backing provides strong sticking power while being easy to remove from most surfaces without leaving or damage.
• Easy to Use: Peel and stick design allows to easily create faces on various surfaces. The stickers separate cleanly from the backing sheet, making them perfect for little hands to use independently during craft time.
• Wide Application: Ideal for classroom activities, art projects, educational , and creative play. Perfect for making puppets, decorating notebooks, creating greeting cards, and teaching emotional expression recognition.
• Package & Size: Includes 20 sheets with 10 stickers each (200 total). Each sheet measures 3.54x3.54 inches (90x90mm). Individual sticker size: 0.79x1.02 inches (20x26mm).

$9.49

Buy on Amazon

Choose and prepare the icon file

ICO for broad legacy coverage

ICO has broad browser support according to MDN’s link-element documentation and is a practical default when you want one conventional favicon. Place the file at the path you use in the link, commonly the site root, and ensure the server returns it as an image rather than an HTML error page.

PNG for a simple modern setup

PNG is easy to create and inspect. Identify its type explicitly if you wish:

<link rel="icon" type="image/png" href="/images/site-icon.png">

The extension, MIME type, and actual bytes should agree. A file named icon.png that contains another format can produce inconsistent results.

SVG when a scalable source is useful

For vector formats such as SVG, MDN documents sizes="any" as a hint:

<link rel="icon" type="image/svg+xml" sizes="any" href="/images/site-icon.svg">

Support is not identical in every browser or context, so keep a raster fallback when your audience includes older or constrained clients. Do not assume that an SVG used for a tab will automatically satisfy every platform’s install or search-icon requirement.

Make the artwork readable at tiny sizes

Use a square canvas, strong contrast, and a design that remains recognizable when reduced to roughly the size of a tab. Image-editing or icon-design software is optional; the HTML mechanism requires only a valid image file and a correct URL.

Add one favicon to a page

1. Create or obtain the image and save it in a format your target browsers support.
2. Copy it into the deployed site’s asset directory. For the example below, the file is public/images/site-icon.png in a typical project and is published at /images/site-icon.png.
3. Open the HTML document’s <head> and add the link before </head>.
4. Deploy both the HTML and image, then request the exact icon URL directly in a browser to verify that the image loads.

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Example site</title>
  <link rel="icon" type="image/png" href="/images/site-icon.png">
</head>
<body>
  <h1>Example site</h1>
</body>
</html>

For a root icon, the shorter version is sufficient:

<link rel="icon" href="/favicon.ico">

Use multiple icon links when variants matter

A single suitable icon is enough for most sites. When you provide alternatives, browsers can use hints such as type, media, and sizes to select a candidate. If a preferred candidate is unsupported, MDN notes that a browser may try another.

<link rel="icon" type="image/png" sizes="32x32" href="/icons/favicon-32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/icons/favicon-16.png">
<link rel="icon" type="image/svg+xml" sizes="any" href="/icons/favicon.svg">

Only list files that exist at stable URLs. A declaration does not generate or resize an image; it is merely a hint about a resource the browser can fetch.

Relative paths, hosting, and deployment checks

Root-relative versus page-relative paths

Case and server behavior

Many production servers are case-sensitive. Site-Icon.PNG and site-icon.png can be different files. Check spelling, capitalization, directory names, and the final deployed URL. The icon response should have an image content type and the expected bytes, not a 404 page, redirect loop, login screen, or application error.

Generated pages and frameworks

If a framework has a shared document template, put the link in that template so every route receives it. For static HTML, edit each page or use a common build include. Inspect the rendered page source or browser developer tools; checking only a source template can miss a build step that removes or rewrites the element.

Browser tab display versus Google Search display

These are related but separate outcomes. A browser can use a valid rel="icon" resource even when a search engine does not show it in results. Google Search Central’s favicon guidance says the homepage should include a rel="icon" link, Googlebot and Googlebot-Image must be able to crawl the page and icon, and the icon URL should remain stable. For Google’s Search feature, the icon must be square, at least 8×8 pixels, and Google recommends larger than 48×48 pixels. Google lists BMP, GIF, ICO, PNG, JPEG, PPM, and TIFF for this feature and describes one favicon per hostname.

Those thresholds and crawl conditions apply to Google’s search-result presentation, not as universal requirements for a favicon to appear in a browser tab. A browser tab may show an icon that Google has not selected, and search display can take time after a crawl.

Verify the result before troubleshooting

1. Load the deployed page, not only a local editor preview.
2. Use “View Page Source” or the Elements panel and confirm the <link rel="icon"> is inside <head>.
3. Open the exact href URL in a new tab. Confirm the intended image appears and the network response is successful.
4. Check the browser’s developer-tools Network panel while reloading. Look for a request to the icon URL and inspect its status and content type.
5. Test another page and, if possible, another browser profile. This distinguishes a path problem from a cached tab result.

Common problems and fixes

The tab still shows a blank or default icon

First request the icon URL directly. A wrong path, filename case mismatch, missing deployment, or an HTML error response prevents use. Correct the URL and redeploy both files. If the URL now returns the right image but the tab remains unchanged, caching is a plausible explanation. Check the actual resource URL and consult the current documentation for the browser you are using rather than relying on a universal cache-clearing recipe.

The icon works on the homepage but not on subpages

A page-relative path is probably resolving in the wrong directory. Change it to a root-relative path such as /images/site-icon.png, or add the correct relative path for each page’s location.

Only one of several icons is selected

Confirm every declared file exists and that each type, sizes, and media hint describes the actual resource. Browsers choose among candidates; the order of links alone does not guarantee a particular choice.

The image is visible at its URL but rejected as an icon

Inspect the response headers and file contents. Ensure the server returns an image MIME type, the file is not behind authentication, and the HTML declaration matches the format. Replace a corrupted or mislabeled file with a newly exported image.

Google does not show the favicon

Recheck the Google-specific conditions: a crawlable homepage and icon, a stable URL, a square image meeting the stated size guidance, and one icon for the hostname. These conditions affect Search display and do not prove that your browser-tab implementation is wrong.

Performance, reliability, and maintenance

• Keep the icon small enough that fetching it does not delay page rendering, while retaining enough resolution for the contexts you support.
• Use a stable URL. Changing filenames frequently can leave browsers and crawlers with old references.
• Deploy the HTML reference and image atomically so visitors never receive a link to a file that has not yet been uploaded.
• Monitor the icon URL like any other static asset; a later CDN rule, access-control change, or rewrite can break it even when the HTML is unchanged.
• When redesigning the brand, test the new artwork at tab size and verify every declared variant rather than assuming the source image is readable when reduced.

Or skip the browser setup

If your immediate goal is to capture a deployed page and inspect whether its tab and page state look correct, ScreenshotNeo can return a screenshot with one request. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

Use the API documentation at https://screenshotneo.com/docs/ for authentication and all options. A basic capture looks like this:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

For a favicon check, replace the example URL with your deployed page and use the returned image to confirm the page renders as expected. ScreenshotNeo also supports full-page captures with lazy images loaded, CSS-selector element captures, dark mode, device presets and custom viewports, retina scale, PDF output, custom CSS and JavaScript, clicks, selector or network-idle waits, request blocking, custom headers and cookies, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work.

The Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is available on every plan. Create a free ScreenshotNeo account to get started.

FAQ

Frequently Asked Questions

Does a favicon have to be named favicon.ico?

No. The filename is arbitrary; the URL in the href attribute is what matters. The familiar name is simply a convention.

Can I put the link outside the head element?

Use the document head. That is where the page metadata and icon relationship belong, and it makes the declaration predictable for browsers and tooling.

Will adding a favicon change my page’s SEO ranking?

The HTML link supplies an icon relationship. Google’s separate Search display guidance describes crawlability and image conditions for showing a favicon in results; it does not state that the link itself is a ranking factor.

Do I need a web-app manifest to show a browser-tab icon?

No. A manifest concerns installable web-app experiences and is outside the basic browser-tab implementation described here.

Quick Recap

Bestseller No. 1

Hobbspring 200Pcs Make a Face Self-Adhesive Stickers Cartoon 10 Designs

$9.49

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.