The favicon is the smallest detail that most affects how a site feels: a white square in the tab, a blurry block in bookmarks, a cropped ring after adding the site to a phone home screen.
1. How many sizes go inside the ICO
The classic answer is 16x16, 32x32 and 48x48 in one ICO. Two more make it robust today: 64x64 for high-DPI screens and 256x256 for the large Windows icon view. Image to ICO takes a 512x512 PNG and generates the multi-size ICO in one step.
2. Does more sizes mean a bigger file
Not noticeably. Real favicons with embedded PNGs total 20-60 KB across sizes; anything over 100 KB is unoptimised. Browsers only read the size they need, so extra entries cost nothing at runtime -- but uncompressed bitmaps in every size quickly add up.
3. The four files a modern site needs
favicon.icoin the site root (old browsers and RSS readers request this path directly);favicon.svgfor modern browsers: vector, sharp at any size, and can respond to dark mode;apple-touch-icon.pngat 180x180 for iOS home screens, without rounded corners -- the system rounds them itself;og-cover.pngat 1200x630 for social previews, which is a separate job from the favicon.
4. Why a white square appears
The usual cause is a white or very light mark with no background colour: on a white tab bar it simply vanishes. Give the icon a dark or brand-coloured background, or make it a solid shape. The test is whether it is still recognisable at 16x16 -- design at 16 px first, then add detail.
5. Dark mode
An SVG icon can switch fill colours with a media query:
<style>
@media (prefers-color-scheme: dark) {
.bg { fill: #0b1220; }
}
</style>
That way it does not turn into a smudged dark blob in a dark tab bar.
6. Changes that do not show up
Favicon caches are stubborn: browsers, CDNs and OS icon caches each keep a copy. Verify in a private window first, then consider renaming the file (for example favicon-v2.ico) and updating the HTML references.