Favicon Sizes You Actually Need
A practical favicon sizing guide for browser tabs, Apple touch icons, and PWA install icons.
Favicon sizing gets confusing because different platforms use different icon surfaces. If you only export one size, quality breaks in real usage.
This guide covers a minimal set that works well for modern projects.
Recommended size set
Use these as your baseline:
16x16PNG: classic tab and small browser surfaces32x32PNG: standard browser icon fallback180x180PNG: Apple touch icon192x192PNG: Android / PWA icon usage512x512PNG: high-resolution PWA install iconfavicon.ico: legacy/fallback packagefavicon.svg: modern vector tab icon where supported
Why this set is enough for most teams
It balances compatibility and maintenance:
- small files for common tab usage
- larger files for app-like install surfaces
- vector fallback for crisp scaling
Going far beyond this can add complexity with little practical gain unless you have very specific platform constraints.
Sizing rules that prevent blur
- Start from a clean square source.
- Keep simple shapes for tiny sizes.
- Avoid thin details that disappear at 16px.
- Check icon silhouette first, then color nuance.
Practical workflow
- Build symbol in Free Logo Maker if you need a fresh mark.
- Generate all favicon sizes in Favicon Generator.
- Test rendered icons in real browser tabs and mobile environments.
- Add head tags + manifest references.
Common mistakes
- Using only SVG and skipping PNG fallbacks
- Exporting one large PNG and resizing in browser
- Keeping text-heavy logos as favicons
- Forgetting
180x180for iOS home screen
If your icon is not recognizable at 16px, simplify the design. No export setting can fix an over-detailed mark at that scale.
Quick test matrix
- Desktop Chrome tab
- Desktop Safari tab
- Mobile Safari home screen
- Android install prompt
- Bookmark list
If icon identity remains consistent across these surfaces, your size setup is strong.
Practical FAQ
Quick review checklist
- Test all sizes in-browser.
- Compare light and dark tab surfaces.
- Validate manifest icons.
- Confirm crisp rendering on high-DPI displays.
Final recommendation
Maintain one approved size set and reuse it across releases. Stable sizing standards prevent recurring visual regressions and simplify deployment.
Asset maintenance policy
Keep exported favicon files and source mark versions together in version control. This makes refreshes safer when branding evolves and prevents stale icon files from lingering in production.
Additional source references: 1 2 3.