Favicon Sizes: 16, 32, 48, and 180px Explained

PublishedToolFavicon Generator

Contents
  1. Why do you need multiple sizes?
  2. Where each size gets used
  3. Making a favicon set without a tool
  4. It won't update after you changed it: narrowing it down in order
  5. Common Sticking Points
  6. Summary
  7. Frequently Asked Questions

You uploaded a new logo to your site, but the browser tab icon hasn't changed. Or you add the site to your iPhone home screen and the icon comes out blurry. That's because a favicon isn't a single file — each place it appears needs a different size.

This post covers which sizes you need and why, what to put in <head>, and the order to check things when you changed the icon but it won't update.

Summary ① When you declare multiple icons, the browser reads sizes and picks one. Those sizes values are actual pixels, not CSS pixels. ② The iOS home screen icon is set separately with rel="apple-touch-icon", and the iPhone Retina example size in Apple's docs is 180×180. ③ When it won't update, narrow it down in this order: file → tag → cache. The icon in search results can take anywhere from a few days to a few weeks, until it gets crawled again.

Why do you need multiple sizes?

Here's how the HTML standard handles favicons. When you declare multiple icons, the browser looks at the type, media, and sizes attributes and picks the one that fits that spot best.

The unit used in sizes is the key here. The standard states flatly that the sizes keyword means actual pixels, not CSS pixels. The standard's own example: on a device with a 2x screen density, an icon that displays at 50 CSS pixels wide is 100 actual pixels wide.

That's why you ship a 32px icon alongside the 16px one that tab icons used for years. The space on screen is the same, but at 2x density you need twice the actual pixels.

Where each size gets used

SizeTagWhere it's used
16×16rel="icon"The smallest spots, like tabs and the address bar
32×32rel="icon"The same spots on 2x displays, and slightly larger spots
48×48rel="icon"Headroom for larger spots
180×180rel="apple-touch-icon"When added to the iOS home screen

The first three are all rel="icon" and differ only in their sizes value. The browser decides which one to use, so all you have to do is provide the candidates.

The iOS home screen icon uses a different tag

Apple's docs say that if you want one icon for your whole site, put a PNG file in your root folder named apple-touch-icon.png, or add <link rel="apple-touch-icon" href="...">. If you want several for different devices, attach sizes, and the value given as the iPhone Retina example is sizes="180x180".

The same docs explain why 180px alone is fine. If there's no size that matches the device, the rule is to use the smallest one that's larger than the recommended size, and if nothing larger exists, use the largest one.

Also, if there are no link tags at all, it looks in the root for a filename starting with apple-touch-icon. So naming your file to match and uploading it still works.

Search result icons follow their own rules

Google's Search documentation states that a favicon must be square (1:1) and at least 8×8, and recommends larger than 48×48 so it looks good across screens. The supported rel values are icon, shortcut icon, apple-touch-icon, and apple-touch-icon-precomposed.

It also says only one favicon is supported per site (based on hostname), and it must be declared on the home page. Don't stop at small tab sizes — having one extra larger square file helps in search results.

Making a favicon set without a tool

There are four steps.

  1. Prepare the largest square original you can. Enlarging a small image makes it blurry, so always scale down from the big one.
  2. In an image editor, resize to 16, 32, 48, and 180px separately and save each as PNG. On macOS Preview it's Tools > Adjust Size; in Windows Paint it's the Resize menu.
  3. Upload the saved PNGs to your site root.
  4. Add the link tags to <head>.
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="48x48" href="/favicon-48x48.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">

There are two things to watch out for. The standard says you must not list sizes in sizes that the file doesn't actually have. If you have one 32px file and write sizes="16x16 32x32", the browser's choice will be off.

The other is the Apple touch icon. If you leave the background transparent, the transparent areas can show up black on the iOS home screen, so it's safer to fill in a background color.

The annoying part is repeating the same resize four times, and since every editor uses a different downscaling algorithm, small sizes like 16px are especially prone to getting mushy.

Check it with our tool. Upload one image and you get 16/32/48/180px PNGs all at once, plus the same link tags above to copy from the same screen. Turn off the Keep transparent background checkbox and you can pick a background color to fill in, which takes care of the Apple touch icon in the same place.

Favicon Generator

It converts right in your browser with no install and no sign-up, and the images you upload are never sent to a server.

It won't update after you changed it: narrowing it down in order

First you need to separate whether the cause is the file, the tag, or the cache. Follow the order and you'll usually be done within 2 or 3 steps.

Step 1: Did the file actually change?

Type the favicon file URL directly into the browser address bar and open it (for example, https://example.com/favicon-32x32.png). The cache can interfere here too, so open it in a private window or force a reload to fetch it again.

If the old image still shows up after that, the problem is on the deploy or CDN side, not the tags.

Step 2: Did the tag actually make it in?

View the page source and search for rel="icon". It's common for tags your framework adds automatically to overlap with tags you added yourself.

The standard says that when several equally appropriate icons exist, it uses the one declared last in the document. If a default tag comes after the one you added, that one wins.

Step 3: An old favicon.ico left in the root

The standard says that when there are no links with the icon keyword, the browser may request /favicon.ico. Pages with the tags in place never use that path, but pages missing the tags keep showing the old file sitting in the root.

Step 4: Browser cache

Open the same URL in a private window or a different browser. If the new icon shows up there, the problem is narrowed down to caching.

In that case, rename the file or change the URL like href="/favicon-32x32.png?v=2" and the browser treats it as a different resource. That said, Google's docs specify that the favicon URL should be stable — in other words, don't change it often. Don't version it on every deploy; change it only when you actually swap the icon.

Step 5: The icon in search results

The icon shown in search results is separate from the browser cache. Google's docs say that Googlebot-Image must be able to crawl the favicon file and Googlebot must be able to crawl the home page (so don't block them with robots.txt).

They also state that recrawling can take anywhere from a few days to a few weeks. If steps 1 through 4 all check out and only the search result still shows the old icon, all that's left is waiting.

Common Sticking Points

SymptomCheck This First
Only the tab icon won't changeOpen the file URL directly → try an incognito window
iOS home screen icon shows up blackWhether the background is transparent, fill in a background color
Looks smudged at small sizesWhether you regenerated each size from the large original
Only search results show the old iconCrawl delay, whether robots.txt is blocking it
sizes is ignoredWhether you listed a size the file doesn't actually have

Summary

  • Each favicon size has its own place, so a set with 16, 32, and 48px plus 180px for iOS is a safe bet.
  • The sizes value is real pixels, not CSS pixels, which is why you need 32px for 2x displays.
  • The iOS home screen icon uses rel="apple-touch-icon", and Apple's documentation uses a 180×180 example for iPhone Retina.
  • Google recommends favicons for search results be square, at least 8×8, and larger than 48×48, and it uses only one per site.
  • When it won't update, narrow it down in this order: file → tags → old /favicon.ico → cache → crawl delay.
  • In sizes, list only the sizes the file actually contains.
Favicon Generator

It converts right in your browser with no install and no sign-up, and the images you upload are never sent to a server.

Frequently Asked Questions

Do I have to make a .ico file?

The HTML standard doesn't define a default format for the icon keyword — it only says the resource is expected to be an image. Google's search documentation also states that it supports any valid favicon format. If you set up the link tags properly, PNG alone is fine. That said, on a page with no icon link at all, the browser may request /favicon.ico, so if an old .ico file is still sitting at the root, that's what can show up.

Can't I just use one size?

It works. The standard only says to pick the most appropriate of the available candidates; it doesn't require more than one. But with just one file, it gets stretched or shrunk everywhere it's used, and strokes tend to smudge when it's scaled down small. Making a separate small size keeps it much sharper in those spots.

Can I use an SVG favicon?

The standard defines a keyword called sizes="any", which means an icon that scales up and down, like SVG. Whether it actually works is best checked directly in the browser you're targeting. Declaring a PNG candidate alongside it is safer, since environments that can't handle SVG will fall through to the next candidate.

Does my uploaded image get sent to a server?

No. This tool uses the browser's canvas to shrink your image to each size and generate PNGs, then lets you download the results right in the browser. The image file you upload is never sent to or stored on a server.

I want to grab another site's favicon, not my own

Sometimes you need the original favicon of a site that's already live — for example, to reference a competitor's branding or to use a logo in place of a placeholder in a presentation. The tool in this post is for building a new favicon set from your own image. If you want the opposite — to enter any site address and download the favicons already set up there, size by size — use the Site Favicon Downloader tool.

This article was adapted from our Korean original. Read the Korean original

Related articles

  1. GIF Thumbnail Extraction: Why You Always Get the First FrameWhy extracting a still from an animated GIF always gives you the first frame, how browsers capture frames, and how to grab a specific scene instead.
  2. HEIC to PNG Lossless Conversion: Keep Photo Quality for PrintWhy HEIC photos lose quality in print and design work, and how to convert them to lossless PNG in a free browser tool, with no extra compression.
  3. Why HEIC Won't Open on Galaxy or Windows — and How JPG Fixes ItLearn why iPhone HEIC photos won't open on Galaxy phones or Windows PCs, and what you gain and lose when you convert them to JPG.
  4. ICO File With Multiple Sizes: Sharp Favicon EverywhereSee how one favicon.ico holds 16–256px images, how to read the header to count them, and how to build a multi-size ICO from a PNG.
  5. Changing Image DPI Won't Change Quality: Print Size FormulaChanging an image's DPI doesn't change how it looks on screen. See the pixel, DPI, and print size formula, and how to set both with our free tool.
  6. Why Saved Instagram Photos Look Blurry: Screen vs OriginalSaved Instagram photos look blurry because you get the 351×350 preview crop, not the upload. Here's how to check the real original size yourself.

Related tools