Why one favicon.ico is not enough anymore#
A single favicon.ico was sufficient in the era of desktop-only browsing, but modern devices each expect their own optimized size: a browser tab wants a small, crisp icon; an iPhone home screen icon needs to be 180×180 to avoid getting blurrily upscaled; Android and PWA install prompts look for 192×192 and 512×512 specifically. Serving only a tiny favicon.ico means the icon that shows up when someone adds your site to their home screen is often a stretched, soft version of something never meant to be shown that large.
What each size in this set is actually for#
16×16 and 32×32 are the classic browser tab and bookmark icons — 32px covers higher-DPI displays where a 16px icon would look soft. 48×48 is used by Windows for site shortcuts and some browser UI. 180×180 is Apple's required size for the home-screen icon on iOS — smaller sizes get scaled up and look noticeably worse. 192×192 and 512×512 are the two sizes the Web App Manifest spec expects for Android home-screen icons and PWA install/splash screens respectively.
Why the source image matters more than the resizing#
Resizing down from a large, sharp source image produces a clean result at every smaller size; resizing up from a small source image cannot recover detail that was never there — a 32×32 favicon.ico upscaled to 512×512 will look blurry no matter how good the resizing algorithm is. Starting from at least a 512×512 source image, ideally simple and legible at a glance (a mark or a single letter reads better than fine detail at 16px), gives every generated size the best chance of looking sharp.