Pick the target first: where is this going
An "icon" is a set of files, not one file — the publish target decides the checklist (this site's Icon Generator generates exactly what the target needs, with no unrelated assets mixed in):
| Publish target | File checklist | Easily missed |
|---|---|---|
| Website | favicon.ico (16/32/48) + favicon.svg + apple-touch-icon 180 + manifest 192/512 | Root-path ICO fallback (old browsers only check that location) |
| PWA | the above + 512 maskable (safe-zone version) | maskable — the installed desktop icon gets cropped round |
| Android app | 192×192 + 512 (with adaptive foreground/background) | The foreground layer needs transparent margins |
| iOS app | 180×180 (opaque background) | Transparent areas get filled black by iOS |
| WeChat mini-program tabBar | 81×81 normal + selected states, each file ≤40KB | Size overage — must compress before release |
The generator also hands over integration snippets for nine frameworks (HTML, Next.js, Vite/React, Nuxt, SvelteKit, Astro, uni-app, Taro, WeChat app.json) — not knowing how to wire the files into the project is a more frequent blocker than generating them.
Choosing among four starting points
Drawing from a blank canvas is the slowest path. Pick by scenario:
- Templates (18 graphic templates): product sites with no logo that need to ship — high-contrast letterforms hold up at 16px/32px; change a letter and go;
- Text: the product's initial or abbreviation — naturally high-contrast and centered, the sturdiest route for favicons;
- Emoji: internal tools, demos, campaign pages — fun, but check platform differences (each platform draws emoji differently);
- Uploaded logo: existing brand assets — the key is cropping (a full logo squeezed into a square canvas often becomes a tiny subject; taking a distinctive fragment is clearer).
16px is the truth: four design sins
The design file looks fine at 512px; the browser tab has 16×16 — four frequent causes of death (the generator validates each):
- Low contrast: light subject on light background melts into gray at 16px;
- Tiny subject: the icon occupying a small central patch — brand-manual-style generous whitespace is suicide in a favicon;
- Heavy glow: gradients, shadows, and glows collapse into gray smudge at 16px; solid blocks are the language of that size;
- Transparent-background app icons: iOS fills transparency with black and Android launchers vary — use an opaque background for app scenarios.
Beyond validation, the preview panel is the final judge: real-size previews of the browser tab, search results, mobile desktop, PWA install card, and mini-program tabBar states — far more honest than the design file. Revise once and glance at the preview; that beats agonizing over 512px details.
Honest limits of icon engineering
- Favicons don't update instantly: browsers cache favicons notoriously hard — still seeing the old icon after launch doesn't mean failure; force-refresh, try an incognito window, or check an uncached device before concluding;
- One icon set doesn't manage brand consistency: favicon, PWA icon, app icon, and social share image (og:image) are four different jobs — the generator covers the first three; og:image is another sizing logic entirely;
- Mini-program tabBar limits are platform rules: 81×81 and the 40KB cap are WeChat's constraints, not the tool's — design within them (solid colors, single layer, few details) rather than compressing afterward.
Frequently Asked Questions
Which favicon sizes does a website need?
The modern set is five pieces: favicon.ico (16/32/48, at the root as fallback), favicon.svg (modern browsers), apple-touch-icon.png 180×180 (iOS), and manifest 192×192 plus 512×512 (Android and PWA). Add a 512 maskable version for PWA cropping. It's one generation pass; whatever you skip either doesn't render or gets a low-quality screenshot substitute.
Why does my icon look great in the design file but unreadable in the browser tab?
The tab's favicon is 16×16 pixels — gradients, glows, and layering all evaporate at that size. Three frequent causes: low contrast, tiny subject, heavy glow. The test: shrink the design to 16px and look — the generator's real-size browser-tab preview is more honest than the design file.
What is a maskable icon, and does a PWA really need one?
A maskable icon is prepared for PWA installs: Android launchers crop icons into various shapes, with the cut eating up to ~20% of the edges. Keep important content inside the central safe zone (~80%) and fill the rest with background. Not mandatory, but without it the installed icon can look mangled — serious PWA distribution deserves a 512×512 maskable version.
Should favicon be SVG or ICO?
A combination: SVG for modern browsers (crisp, small, dark-mode adaptable), ICO at the root path for old browsers, bookmarkers, and crawlers. Declare both with link tags — new browsers take the SVG, old ones fall back to ICO. ICO-only blurs on high-DPI screens; SVG-only shows nothing in old environments.