Practical Tool Guides
Favicon package deployment checklist
Prepare a source logo, understand every generated asset, deploy the package, and handle stubborn browser caches.
Prepare a source that survives small sizes
A favicon is often shown at 16 or 32 pixels, so fine text and thin lines disappear quickly.
- Start from a transparent square at 512px or larger.
- Use fitting or padding instead of stretching a rectangular logo.
Know what the package contains
ICO covers traditional browser requests, PNG files target explicit sizes, Apple and Android files serve home screens, and the manifest describes installable icons.
- Keep the generated filenames unless you also edit every link.
- Use the generated HTML snippet in the document head.
Deploy and defeat stale caches
Place the files in the public site root, deploy them with the page, and verify direct URLs before checking the browser tab.
- Open /favicon.ico and /site.webmanifest directly.
- Use a hard refresh, fresh profile, or versioned path when an old icon remains cached.