Set up favicons for browsers and home screens
Favicons have a strange history. A tiny browser icon somehow turned into folders containing:
favicon.ico
favicon-16x16.png
favicon-32x32.png
apple-touch-icon.png
android-chrome-192x192.png
android-chrome-512x512.png
mstile-150x150.png
browserconfig.xml
site.webmanifest
...
Some of those files had real reasons to exist. Some are leftovers from older browsers and platforms. In 2026, a normal website can often use a much smaller setup.
Evil Martians published a useful current overview in How to Favicon in 2026, and the main lesson is something I like: you probably do not need a favicon generator that produces twenty files.
The basic files
A practical setup can be very small:
favicon.ico
icon.svg
apple-touch-icon.png
Then add a web app manifest only if your site needs installable app metadata or Android home-screen behaviour.
Keep favicon.ico
Even though ICO is old, it remains a useful compatibility fallback. Put:
/favicon.ico
at the site root. Browsers and other tools often look there automatically. A small multi-size ICO can cover older use cases.
Use SVG for modern browsers
<link
rel="icon"
href="/icon.svg"
type="image/svg+xml">
SVG is useful because it scales cleanly and can remain tiny. For a simple logo or letter mark, it is often the nicest main favicon format.
SVG can support dark mode
An SVG file can contain CSS:
<style>
path {
fill: #111;
}
@media
(prefers-color-scheme: dark) {
path {
fill: #fff;
}
}
</style>
Now the favicon can adapt to the user’s theme in browsers that support this behaviour. That is a nice advantage over one fixed PNG.
Apple touch icon
For iOS home-screen bookmarks:
<link
rel="apple-touch-icon"
href="/apple-touch-icon.png">
A PNG around:
180 × 180
is a common choice. Unlike a browser favicon, this icon may appear much larger, so make sure the artwork still looks good at home-screen size.
A simple head
<link
rel="icon"
href="/favicon.ico"
sizes="any">
<link
rel="icon"
href="/icon.svg"
type="image/svg+xml">
<link
rel="apple-touch-icon"
href="/apple-touch-icon.png">
That is enough for many ordinary websites.
What about a manifest?
A web app manifest may contain:
{
"name": "My Website",
"icons": [
{
"src": "/icon-192.png",
"sizes": "192x192",
"type": "image/png"
},
{
"src": "/icon-512.png",
"sizes": "512x512",
"type": "image/png"
}
]
}
If you are building a Progressive Web App or want installable app metadata, that makes sense. For a simple personal website that is not meant to be installed as an app, I would not create a manifest only because a favicon generator told me to.
Keep artwork simple
A favicon may be displayed at:
16 × 16
pixels. A detailed logo that looks great at 500 pixels can become a muddy blob. Use:
- one letter;
- a simple shape;
- a strong symbol;
- high contrast.
Use a shape that remains recognisable at small sizes.
Test real browsers
Check:
- browser tab;
- bookmarks;
- dark mode;
- Safari;
- Chrome;
- Firefox;
- iPhone home-screen icon if you support it.
Do not assume a generated preview matches every real use.
Cache can be annoying
Favicons are cached aggressively. If you replace one and still see the old version, try:
- hard reload;
- new private window;
- changing the file name temporarily;
- clearing site data.
Do not spend an hour rewriting the HTML before considering cache.
Add app icons only when the site needs them
I like the modern favicon approach because it matches how I think about websites in general. Start with the smallest set that covers real needs. Add app-specific files when the site actually behaves like an app.
For most normal websites, three good favicon files are much easier to understand than a folder full of historical compatibility assets.