audreyfeldroy/favicon-cheat-sheet

Obsessive cheat sheet to favicon sizes/types.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 6th, 2026
Created on August 5th, 2013
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 397
Total Stargazers: 9,906 (+0)
Total Subscribers: 265 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 213.8 days
Mean response time: 1597.4 days
90th percentile: 4507.4 days
Tracked items: 28

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 0% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

favicon-cheat-sheet is a reference guide that documents favicon sizes, types, and implementation approaches for web projects.

The guide addresses the problem of favicon complexity by providing a curated set of recommendations for modern browsers alongside historical context for legacy support. It distinguishes between the minimal viable approach for contemporary projects—which relies on SVG favicons with dark mode support and PWA manifest icons—and the fuller set of specifications needed for comprehensive browser and platform coverage. The tool explains how SVG favicons leverage media queries to automatically adapt to user preferences without JavaScript, and documents the specific requirements for different platforms such as Safari pinned tabs, iOS touch icons, and Windows tiles.

Developers building new projects should focus on the modern minimum section, which covers the majority of real-world use cases with just SVG and manifest configuration. The guide is most useful for those who need to understand why certain favicon sizes and formats exist, rather than blindly following outdated practices. It suits projects where design consistency across light and dark modes matters, and where supporting older browsers is either unnecessary or explicitly required. The resource provides enough detail to implement favicons correctly without over-engineering for obsolete platforms, while remaining comprehensive enough for teams that must maintain legacy browser support.

Development activity shows consistent maintenance focused on keeping recommendations current with browser capabilities. The project receives updates to reflect changes in browser support, particularly around SVG favicon adoption and dark mode preferences. Contributions address both the core reference material and clarifications to existing guidance. The maintainer actively refines the modern minimum guidance as browser landscape shifts, ensuring the resource remains practical rather than becoming a historical archive.