October 10, 2026 · Updated November 7, 2026 · By Dhurka Manchukan, Software Engineer · Guides · 4 min read
Favicon sizes in 2026: what you actually need
Favicon advice online is full of long lists of sizes, many of them out of date. In practice a small set of files covers every browser, phone and installed web app. This guide explains what each file is for so you can stop guessing.
The short list
- favicon.ico containing 16, 32 and 48 px images, placed at the site root.
- favicon.svg for browsers that support scalable icons.
- apple-touch-icon at 180 px for iPhone and iPad home screens.
- icons at 192 and 512 px, referenced from the web manifest, for Android and installed apps.
- maskable versions of the 192 and 512 px icons.
Why favicon.ico still matters
Some browsers, feed readers and crawlers request /favicon.ico without reading your page. Keeping an ICO at the root means they find something. Because the format can bundle several sizes, one file serves tabs, bookmarks and high-density screens.
SVG for sharp, flexible icons
A vector icon stays crisp at any size and can even adapt to a dark or light browser theme using a prefers-color-scheme media query inside the SVG. It only works if your source really is vector. A logo exported as a raster image should stay a PNG rather than being wrapped in an SVG.
Apple touch icons
When a visitor adds your page to an iPhone or iPad home screen, iOS uses the apple-touch-icon. A single 180 px PNG is enough for current devices. Use a solid background rather than transparency, because iOS fills transparent areas with black.
Android, manifests and maskable icons
Android and installed web apps read icons from the web manifest. Provide 192 and 512 px PNGs. Maskable icons let the system crop your icon into a circle or rounded shape, so keep the important artwork inside the central 80% safe zone, otherwise the edges may be cut off.
Linking them in the head
The files do nothing until your page points at them. Add a link tag for the ICO and the SVG, a link tag for the Apple touch icon and a link to the manifest. A generator that outputs this markup saves a common source of mistakes.
Common problems
- A favicon that does not change: browsers cache aggressively, so hard-refresh or rename the file.
- A blurry icon: the source was too small or too detailed. Start from a simple square mark at 512 px or larger.
- A missing icon on dark tabs: a dark logo on a transparent background disappears. Add a background colour.
- A wrong path: use absolute paths from the site root so nested pages still find the files.
What the markup looks like
A complete head section for the set above is only four lines: a link with rel="icon" pointing at /favicon.ico and sizes="48x48", a second rel="icon" link for /favicon.svg with type="image/svg+xml", a rel="apple-touch-icon" link for the 180 px PNG, and a rel="manifest" link to /site.webmanifest. The manifest itself lists the 192 and 512 px icons, and marks the maskable ones with a purpose of maskable.
Frameworks and platforms
- Next.js (App Router): place favicon.ico, icon and apple-icon files in the app directory and the framework adds the link tags for you.
- WordPress: set a Site Icon in the Customizer. WordPress asks for a square image of at least 512 px and generates the smaller sizes.
- Plain HTML or static sites: copy the files to the site root and paste the markup into every page head, or into your shared layout.
- Single-page apps: put the files in the public folder so they are served from the root unchanged.
What you can safely skip
Older guides list a dozen Apple icon sizes, Windows tile images and several legacy Android densities. Modern iOS scales the 180 px icon down itself, Windows no longer uses tile images in current browsers, and Android reads the manifest. Unless you have a specific old device to support, the short list at the top of this article is enough. Fewer files also means fewer things to keep in sync when the logo changes.
How to check your work
Open the site in a private window so no cached icon is shown, then look at the tab, a bookmark and, if you can, the home-screen icon on a real phone. In the browser's developer tools, the Application panel lists the manifest and its icons and flags any that fail to load. Requesting /favicon.ico directly should return the file rather than a 404 page. Finally, test at the smallest size: if your mark is unreadable at 16 px, simplify it rather than adding detail.
If you want the whole set generated and checked in one step, Faviqo builds every file above from a single logo, in your browser, and gives you the markup to paste. The story behind it is in Why I built a favicon generator that never uploads your logo.
Written by
Dhurka Manchukan
Software Engineer · Sri Lanka
Dhurka Manchukan is a software engineer based in Sri Lanka and the person behind MDXTORA. Dhurka designs, builds and runs QRinst, Faviqo and Wayvert, and writes the articles in the Journal from what comes up while building them.
About the author →Keep reading
- ProductWhy I built a favicon generator that never uploads your logoNotes on building Faviqo — a browser-only favicon and app-icon toolkit — and the decisions behind keeping it private and server-free.
- GuidesCommon QR code mistakes and how to avoid themThe most frequent reasons QR codes fail in the real world, from poor contrast to broken links, and how to prevent each one.
- GuidesHow to estimate a trip budget before you bookA practical way to estimate what a trip will cost: the four daily categories, how to handle flights and currency, and how much buffer to add.
