Essay 192
Favicon and app icons explained: the smallest piece of your brand
2026-10-01
Nobody consciously admires a favicon and everybody notices its absence: the smallest visible piece of your brand is still your brand.
It is the smallest piece of design your company ships: the mark in the browser tab, the square on a phone's home screen when someone saves your site beside their apps. Nobody consciously admires a favicon, and everybody notices its absence. The tab shows a blank square, the bookmark shows a grey placeholder, and the site reads as slightly unfinished in a place the visitor looks at for hours every day.
The market's false version calls it decoration: ship the site, the icon can come later, it is a detail for a slow Friday. In practice the icon is a small trust signal that travels further than the homepage does. It appears in the bookmarks bar, in the browser history, in the saved home-screen shortcut, in the row of open tabs a busy person stares at all day. The blank tab is a small leak, and it is most visible in exactly the places owners forget. Every one of those places shows either your mark or a hole where your mark should be.
The honest mechanism has two parts. First, one source icon must be produced into the several sizes and shapes the devices ask for, because the same artwork that holds at large has to survive a tiny square, a round mask, a dark background. Second, these files are cached hard: browsers and phones hold on to them with unusual loyalty. Change the icon and the change can stay invisible to you for days while being perfectly live for everyone else.
The failure versions are familiar. The site launched with the platform's default icon, a letter nobody chose, sitting in every visitor's tab from day one. The single small file stretched over every use, blurred wherever it is shown large and mushy wherever it is shown small. And the owner who changed the icon, checked the tab, saw the old one, and concluded the change failed, when their own browser was the only device on earth still refusing to let go.
The practice is short. Design the mark to survive very small and very large: if it only works at billboard size, it does not work. Generate the full size set once, at launch, not as a favor to a later sprint. Test in a private window or on another device, where no cache has memory of the old icon. And keep the icon set on the launch checklist and on the redesign checklist, because a redesign that renews the logo and not the icon ships the mismatch into every tab that carries your name.
Guidance, not guarantees: we treat the icon set as part of a launch, not an afterthought, and we verify changes through a clean view before calling them done. The exact size list and the mechanics of producing it belong to the documentation of whatever you build on, and that list moves. The principle does not: the smallest visible piece of your brand is still your brand.
FAQ
Direct, unambiguous answers
Does a favicon really matter for my website?
Nobody consciously admires a favicon and everybody notices its absence. The blank tab, the grey placeholder in the bookmarks bar, the empty square in a row of open tabs a busy person stares at all day: the site reads as slightly unfinished in a place visitors look at for hours. The icon is a small trust signal that travels further than the homepage does.
Why do I need several icon sizes instead of one small file?
Because one source icon must be produced into the several sizes and shapes the devices ask for: the same artwork that holds at large has to survive a tiny square, a round mask, a dark background. The single small file stretched over every use is a familiar failure, blurred wherever it is shown large and mushy wherever it is shown small.
I changed my favicon but my browser still shows the old one. Did the change fail?
Probably not. Icon files are cached hard: browsers and phones hold on to them with unusual loyalty, so a change can stay invisible to you for days while being perfectly live for everyone else. Your own browser may be the only device on earth still holding the old icon. Test in a private window or on another device, where no cache has memory of it.
When should the icon set be produced, at launch or later?
At launch, once, not as a favor to a later sprint. Design the mark to survive very small and very large first, because if it only works at billboard size it does not work, then generate the full size set before the site goes out. And keep the icon set on the redesign checklist too: a redesign that renews the logo and not the icon ships the mismatch into every tab.
Next step
Web Platforms
Web platforms and engineering (bilingual, RTL-native, fast, and built to be found) on the same stack that runs this site and our ventures.
Start an order, request a private consultation, or simply ask a question: one WhatsApp message in Arabic or English opens the conversation.
Talk on WhatsApp