Favicon generator skill

When the user wants to implement, optimize, or audit favicon and app icons.

by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗

Use now

Files of Favicon generator

kostja94/main1 file shown
SKILL.md
Show the full text104 lines

Components: Favicon

Guides favicon and app icon implementation for brand consistency across browser tabs, bookmarks, mobile home screens, and Google Search results. Favicons help users identify sites; missing or incorrect icons hurt trust.

When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify:

  1. Tech stack: Next.js, WordPress, static HTML, etc.
  2. PWA: Is the site a PWA or planning to be?
  3. Existing assets: Logo, icon files

Required Sizes

Size Use
16x16 Browser tabs, standard displays
32x32 Retina/HiDPI browser tabs
180x180 Apple Touch Icon (iOS home screen); no transparency
192x192 Android Chrome home screen, PWA launcher
512x512 PWA splash screens, adaptive icons

Optional: 48x48, 96x96, 120x120, 152x152, 167x167, 256x256 for broader coverage.

Formats

Format Use
SVG Modern browsers; scalable; supports dark mode via media queries; lightweight
PNG High-DPI; explicit sizes; easy to generate; required for Apple Touch Icon
ICO Legacy; bundles multiple sizes; fallback for older browsers

Recommended: Provide SVG + PNG fallbacks. Never skip Apple Touch Icon (180x180); iOS shows a generic screenshot without it.

Google Search (SERP Display)

See serp-features for SERP feature types and optimization.

Favicons can appear in Google Search results next to your site's listings. Google Search Central requirements:

Requirement Guideline
Placement Add <link rel="icon" href="/path/to/favicon.ico"> to homepage header
One per hostname One favicon per hostname; example.com and code.example.com are separate; example.com/sub-site shares the same favicon
Crawlability Googlebot-Image must crawl favicon; Googlebot must crawl homepage; do not block either in robots.txt
Shape Square (1:1 aspect ratio); minimum 8x8px; preferably >48x48px for quality across platforms
Stable URL Do not change favicon URL frequently
Appropriate No inappropriate content (pornography, hate symbols); Google may replace with default icon
Timing Crawling can take days to weeks; use Search Console URL Inspection to request indexing

Supported rel values: icon, shortcut icon, apple-touch-icon, apple-touch-icon-precomposed. href can be relative (/favicon.ico) or absolute; favicon can be hosted on CDN.

Implementation

<link rel="icon" href="/favicon.ico" sizes="any">
<link rel="icon" href="/icon.svg" type="image/svg+xml">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
Next.js

Place in /app: favicon.ico, icon.png, apple-icon.png. Next.js auto-generates tags.

PWA Manifest

Include icons array in manifest.json with 192x192 and 512x512 for maskable icons.

Best Practices

  • Simplicity: At 16x16, complex details are illegible; use simplified logo mark; design for brand recognition in SERPs
  • Consistency: Favicon should match logo/brand (logo-generator, brand-visual-generator)
  • Cache: Use long cache; version for updates (e.g. /favicon.ico?v=2)
  • Tools: RealFaviconGenerator, favicon.io, or favicons npm package for automation
  • Test: Check across browsers, dark mode, and Search Console (favicon may take days to weeks to appear)

Output Format

  • Size checklist (16, 32, 180, 192, 512; >48x48 for Google Search)
  • Format recommendations (SVG, PNG, ICO)
  • Implementation notes per tech stack (homepage header placement)
  • Google Search checklist (crawlability, stable URL, appropriate content)
  • Manifest (if PWA)
  • logo-generator: Favicon typically derived from logo; consistent branding
  • media-kit-page-generator: Media kit should include favicon or link to brand assets
  • brand-visual-generator: Visual identity; favicon aligns with brand colors and mark
  • indexing: Favicon requires crawlable homepage; URL Inspection for indexing
1---
2name: favicon-generator
3description: When the user wants to implement, optimize, or audit favicon and app icons. Also use when the user mentions "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," or "tab icon." For visual system, use brand-visual-generator.
4metadata:
5 version: 1.0.1
6---
7 
8# Components: Favicon
9 
10Guides favicon and app icon implementation for brand consistency across browser tabs, bookmarks, mobile home screens, and **Google Search results**. Favicons help users identify sites; missing or incorrect icons hurt trust.
11 
12**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
13 
14## Initial Assessment
15 
16**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
17 
18Identify:
191. **Tech stack**: Next.js, WordPress, static HTML, etc.
202. **PWA**: Is the site a PWA or planning to be?
213. **Existing assets**: Logo, icon files
22 
23## Required Sizes
24 
25| Size | Use |
26|------|-----|
27| **16x16** | Browser tabs, standard displays |
28| **32x32** | Retina/HiDPI browser tabs |
29| **180x180** | Apple Touch Icon (iOS home screen); no transparency |
30| **192x192** | Android Chrome home screen, PWA launcher |
31| **512x512** | PWA splash screens, adaptive icons |
32 
33**Optional**: 48x48, 96x96, 120x120, 152x152, 167x167, 256x256 for broader coverage.
34 
35## Formats
36 
37| Format | Use |
38|--------|-----|
39| **SVG** | Modern browsers; scalable; supports dark mode via media queries; lightweight |
40| **PNG** | High-DPI; explicit sizes; easy to generate; required for Apple Touch Icon |
41| **ICO** | Legacy; bundles multiple sizes; fallback for older browsers |
42 
43**Recommended**: Provide SVG + PNG fallbacks. Never skip Apple Touch Icon (180x180); iOS shows a generic screenshot without it.
44 
45## Google Search (SERP Display)
46 
47See **serp-features** for SERP feature types and optimization.
48 
49Favicons can appear in Google Search results next to your site's listings. [Google Search Central](https://developers.google.com/search/docs/appearance/favicon-in-search) requirements:
50 
51| Requirement | Guideline |
52|-------------|-----------|
53| **Placement** | Add `<link rel="icon" href="/path/to/favicon.ico">` to **homepage** header |
54| **One per hostname** | One favicon per hostname; `example.com` and `code.example.com` are separate; `example.com/sub-site` shares the same favicon |
55| **Crawlability** | Googlebot-Image must crawl favicon; Googlebot must crawl homepage; do not block either in robots.txt |
56| **Shape** | Square (1:1 aspect ratio); minimum 8x8px; **preferably >48x48px** for quality across platforms |
57| **Stable URL** | Do not change favicon URL frequently |
58| **Appropriate** | No inappropriate content (pornography, hate symbols); Google may replace with default icon |
59| **Timing** | Crawling can take days to weeks; use Search Console URL Inspection to request indexing |
60 
61**Supported rel values**: `icon`, `shortcut icon`, `apple-touch-icon`, `apple-touch-icon-precomposed`. **href** can be relative (`/favicon.ico`) or absolute; favicon can be hosted on CDN.
62 
63## Implementation
64 
65### HTML Link Tags
66 
67```html
68<link rel="icon" href="/favicon.ico" sizes="any">
69<link rel="icon" href="/icon.svg" type="image/svg+xml">
70<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32.png">
71<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
72```
73 
74### Next.js
75 
76Place in `/app`: `favicon.ico`, `icon.png`, `apple-icon.png`. Next.js auto-generates tags.
77 
78### PWA Manifest
79 
80Include `icons` array in `manifest.json` with 192x192 and 512x512 for maskable icons.
81 
82## Best Practices
83 
84- **Simplicity**: At 16x16, complex details are illegible; use simplified logo mark; design for brand recognition in SERPs
85- **Consistency**: Favicon should match logo/brand (logo-generator, brand-visual-generator)
86- **Cache**: Use long cache; version for updates (e.g. `/favicon.ico?v=2`)
87- **Tools**: RealFaviconGenerator, favicon.io, or favicons npm package for automation
88- **Test**: Check across browsers, dark mode, and Search Console (favicon may take days to weeks to appear)
89 
90## Output Format
91 
92- **Size** checklist (16, 32, 180, 192, 512; >48x48 for Google Search)
93- **Format** recommendations (SVG, PNG, ICO)
94- **Implementation** notes per tech stack (homepage header placement)
95- **Google Search** checklist (crawlability, stable URL, appropriate content)
96- **Manifest** (if PWA)
97 
98## Related Skills
99 
100- **logo-generator**: Favicon typically derived from logo; consistent branding
101- **media-kit-page-generator**: Media kit should include favicon or link to brand assets
102- **brand-visual-generator**: Visual identity; favicon aligns with brand colors and mark
103- **indexing**: Favicon requires crawlable homepage; URL Inspection for indexing
104 

Discussion