Bottom-line: I ship favicon sizes as 16 plus 32 plus 48 in ICO plus 180 for Apple touch plus 192 plus 512 for manifest plus SVG for modern tabs, all exported from one 512 master with versioned paths. Build the matrix in the free favicon generator and verify every surface at true size before launch.

I audited icon coverage for a client launch and found desktop tabs sharp while iPhone home screens showed screenshots and Android splash screens blurred. The cause was a partial pack with only 32 plus ICO. I rebuilt the full matrix from one master and every surface resolved in a single deploy.

Full size matrix from 16 tabs to 512 installs

Size strategy decides whether the mark looks designed or accidental across contexts. I tested the full matrix on 27 Sep 2026 and gaps showed immediately as blurry upscales where tuned layers were missing.

Size matrix I ship for complete coverage
Size shippedSurface testedFile usedResult observed
16 pixelsBrowser tab standardICO 16 layerSharp with bold shapes
32 plus 48 pixelsRetina plus bookmarks plus shortcutsICO layersCrisp on high density
180 pixelsApple touch home screenPNG apple touchFull bleed without crop
192 plus 512 pixelsManifest install plus splashManifest PNG pairSharp install continuity
SVG scalableModern vector tabsSVG fileInfinite zoom clarity
  • Start from 512 minimum with square art and centered mark.
  • Keep 10 to 15 percent padding so masks never clip edges.
  • Version every path with v2 query for instant cache refresh.

When each size matters most

Tabs need 16 plus 32 every day. Bookmarks plus shortcuts need 32 plus 48. iPhone needs 180. Android needs 192 plus 512. Modern desktop needs SVG. Missing any band leaves one surface blurry while the rest shine.

Size priority by launch type I use
Launch typeMust ship sizesCan deferVerify with
Blog plus docs site16 32 180 ICO SVG192 512 manifestTab plus home screen check
PWA installable app192 512 plus maskable plus themeSVG tabsLighthouse plus install test
Marketing launchFull matrix plus OG 1200 by 630Nothing deferredTab plus social debugger

Source rules that keep small sizes sharp

Source discipline makes the matrix work. I tested 512 masters versus 128 sources upscaled and the 512 path won at every small size. Keep strokes heavy, keep negative space generous, and avoid text below 32 pixels.

Consistency routine across templates

Export once from one master, reference versioned absolute paths in every template head, and purge CDN after deploy. I tested mixed old plus new sizes across templates and tabs plus installs diverged within a day.

Next steps to parent L1 plus resize workflow

Return to the parent L1 favicon generator guide for the full build plus install plus cache routine. Then open sizes in the image resizer cropper when masters need prep, and confirm share cards in the meta tags guide.

Respect the ICO container as a multi-resolution bundle, not a single image. Layer 16, 32 and 48-pixel variants inside one ICO so legacy desktop contexts pick the sharpest fit without scaling artifacts. Skipping the 48 layer forces some Windows surfaces to upscale the 32 art with visible blur, and the image resizer cropper produces clean per-size sources.

Serve Apple touch and manifest icons from the same 512 master with different crops. The 180-pixel Apple icon wants full-bleed artwork with safe margins, while maskable manifest icons need extra padding inside the safe zone so launchers never clip the mark. One master with two export recipes covers both without duplicate design work.

Revisit the size matrix yearly because platform requirements drift. New device densities add entries, deprecated contexts drop out, and staying current avoids shipping dead weight. The 2026 table in this guide reflects present targets, and a calendar reminder beats discovering gaps from user screenshots. Pair the review with dependency updates each January.