Remembering every favicon size is a losing game. Favvy keeps the list memorized for you—16×16, 32×32, 180×180, 192×192, 512×512, pinned tab SVGs, maskable icons, and more. Drop in a high-resolution design and the plugin handles the rest.

Avoid guesswork

Favvy applies proper padding and rounding for each size, so the icon never looks squeezed or blurry. If a new platform adds another size, the plugin updates faster than your internal docs.

Communicate specs clearly

Each export includes a summary of the generated assets. Hand it to developers or include it in your design system documentation so nobody wonders why a specific size exists.

My approach

1. Maintain one master icon in Figma tied to our brand system.
2. When a request hits, run Favvy and export the entire set.
3. Update the shared documentation with the asset summary so future teams know which sizes to expect.

It’s the easiest way to stay compliant with the ever-changing favicon landscape.

Reduce support requests

When engineering gets a bug report about missing icons, reference Favvy’s exported size summary to confirm deployment. Because the list is standardized, troubleshooting becomes a quick checklist instead of a research project.

Tip

Store Favvy’s summary as part of your automated documentation site. Each time you regenerate icons, replace the snippet so the whole org trusts that it’s current.