The agency favicon problem, briefly
Most agencies ship more client favicons in a year than the average in-house brand team will ship in a decade — one per master brand, then one per microsite, campaign, sub-brand and partnership. The work is small, but the failure surface is large. A 404 on apple-touch-icon shows up as a missing icon when a stakeholder saves the site to their iPhone home screen for a status meeting; a half-resolution favicon looks fuzzy in a Slack unfurl; a stale favicon from the previous brand system sits in a campaign directory for two quarters before someone notices.
None of those individually torpedo a retainer. Together, they erode the “everything looks polished” reputation that wins renewals. The fix is mechanical: a per-client, per-campaign favicon bundle generated once, versioned, and handed to the dev team alongside the rest of the launch package. The generator’s job is to make “once” take ninety seconds.
What a 2026 favicon bundle actually contains
The minimum set has stabilized over the last two browser cycles. A complete bundle for a client microsite includes favicon.ico as a multi-resolution legacy fallback (still requested by older crawlers and a surprising number of email clients), PNG variants at 16, 32 and 96 for tab and bookmark contexts, 192 and 512 PNGs that Android and PWA installers consume, an apple-touch-icon.png at 180×180 for iOS Safari home-screen adds, and a manifest.json referencing the 192 and 512 PNGs along with a theme-color and short-name. The generator outputs all of these in a single ZIP plus the four-line HTML snippet you paste into the <head>.
Skipping any of these still “works” in the sense that browsers fall back gracefully — but each missing file generates a 404 in the Network tab during QA, and procurement teams routinely grep agency-built sites for exactly that pattern. The Web Hypertext Application Technology Working Group’s link relation spec is the source of truth on which rel values are still standard; web.dev’s manifest guide is the practical reference for the manifest.json side.
Where favicon work fits in an agency launch checklist
Favicons belong in the pre-launch QA pass, 48 hours before DNS flip, after the site is on its staging domain. Three checks survive in production: open every templated page on staging and confirm the tab favicon renders correctly; open the Network tab and grep for any 404 on a path matching /favicon* or /apple-touch-icon*; and bookmark the home page to confirm the icon shows in the bookmark bar at retina resolution. Most agencies discover missing favicons the morning of launch when a stakeholder screenshots a browser tab for an internal Slack — running this 48-hour-out check moves the discovery before the fire drill window.
Master brand vs. campaign-specific favicons
The decision rule is simple: match the favicon to the visible logo on the page. If the microsite carries the master brand, use the master favicon. If it’s a sub-brand, partnership co-brand, named campaign with its own visual system, or product line with distinct positioning, ship a campaign-specific favicon. Modern browsers cache by hostname plus path, so a campaign at promo.client.com with its own favicon is what users see in the tab and what gets pinned to the bookmark bar. The visual mismatch when those two diverge — tab says master brand, page says campaign — is the kind of detail a brand-savvy CMO will flag in a 30-second review.
Designing a favicon mark that actually reads at 16px
A full logo legible at 200px collapses to noise at 16px. The standard agency move is to extract a single letterform, a monogram, or an icon element from the master mark, render it on a brand-color background, and treat that as the favicon mark. This is also a chargeable add-on under “digital asset extension” if the client’s brand book doesn’t include a favicon mark already — most don’t.
- Letterform. Pick the strongest letter from the wordmark, set in the brand display face, on a brand-primary fill. Works for ~80% of client brands.
- Monogram. Two letters or a stylized initial. Best for agency-owned client brands and law / professional services where the wordmark is the identity.
- Icon element. A glyph from the master mark used as a standalone. Reserve for clients with a strong existing icon — otherwise a custom one needs to go through the brand-book amendment process.
- Emoji shortcut. For internal tooling, throwaway campaign sites, or a fast-turn build where the brand isn’t finalized. Don’t ship to a flagship client microsite.
How agencies typically integrate the generator into ops
- Discovery doc template. Add a “favicon source asset” field next to logo in the client kickoff form. The PM generates the bundle the day the brand assets land.
- Per-campaign brief. Standard campaign brief lists “favicon: master brand / custom” as a tickbox. Custom triggers a 15-minute design slot and a generator run.
- Versioned deal-room asset. Pin
favicon_v1.zipin the deal record. Increment on rebrand. Future devs and audits find the canonical source instead of resampling from the live site. - QA tickbox. Pre-launch QA template includes the three checks above. Block DNS flip until all three pass.
- Pitch-deck mockup. When pitching a new identity, generate a favicon at the same time and include a browser-tab mockup slide. Underweighted in most decks; high-perceived-effort, low actual cost.
If you also need to label AI-generated copy on those campaign microsites, pair this with the free AI Disclosure Generator; for the meta-tag side of the launch, the SEO Meta Generator covers og:image, twitter:card and the rest of the head block.
Frequently asked questions
How many favicon sizes does a 2026 microsite need?
favicon.ico (multi-resolution), 16/32/96 PNG, 192/512 for Android/PWA, 180 apple-touch-icon, plus manifest.json. The generator outputs the full set so launch QA stops flagging missing files.
One favicon across client microsites, or per campaign?
Match the favicon to the visible logo on the page. Master brand microsite uses master favicon; sub-brand or named campaign gets its own. Tab and bookmark match what users see on the page.
Best way to hand a favicon set to a client’s dev team?
The ZIP plus the four-line HTML snippet that references it. Pin a versioned copy in the deal record so the next dev team finds the canonical source instead of resampling.
Should a favicon match the logo exactly?
Almost never. Extract a letterform, monogram or icon element from the master mark and render that on a brand-color background. Full logos collapse to noise at 16px.
Where does favicon work fit in the launch checklist?
Pre-launch QA, 48 hours before DNS flip. Three checks: tab favicon renders on every templated page, no 404s on /favicon* or /apple-touch-icon* in Network, and bookmark icon shows at retina resolution.