Favicon Essentials: Sizes, Formats and HTML

The formats, sizes, markup, and design decisions behind a dependable site icon.

Use this favicon guide cluster in production order

Start with the decisions that affect every favicon implementation: which source artwork survives reduction, which formats cover modern and fallback clients, which sizes belong in the package, and which link elements belong in the shared document head.

The guides in this cluster move from definition to production. Read the size and format references before copying markup, then finish with the design guide and release checklist so technically valid files also remain recognizable at native tab size.

01

Choose the file stack

Use SVG for a scalable browser candidate, PNG for explicit raster and platform assets, and a multi-frame ICO for conventional and compatibility requests.

02

Design for the smallest surface

Judge the mark at 16×16 and 32×32 while editing. A clean 512-pixel master does not compensate for closed counters, thin strokes, or insufficient edge space.

03

Install and verify

Declare only files that exist, use stable public paths, request every URL directly, and inspect the rendered head rather than trusting a source template.

Editorial visual for What Is a Favicon? The Small Icon With a Big Job

Start with: What Is a Favicon? The Small Icon With a Big Job

A favicon is the compact identity mark browsers, bookmarks, search results, and installed web apps use to represent a site.

Use this foundational guide first, then choose the route below that matches your file format, platform, failure symptom, design constraint, or implementation layer.

Begin with this guide →

Favicon Essentials questions

Use these answers to choose the correct guide or tool before changing production files.

Which favicon guide should I read first?+

Begin with the favicon sizes guide, compare SVG, PNG, and ICO, then use the HTML reference and production checklist.

Do I need every historical favicon size?+

No. Start with a documented modern core and add legacy standalone files only for a measured client or platform requirement.

Is one large PNG enough?+

It is a useful source, but browsers, Apple shortcuts, ICO clients, and installable apps still benefit from purpose-specific files and metadata.