Web manifests can be annoying to maintain. Favvy keeps them in sync with your actual icons. When you export a package, the plugin writes manifest.json with the correct file paths, sizes, and theme colors drawn from your design.

Keep metadata honest

No more guessing which icon is 512x512 or whether the maskable flag is set. Favvy’s manifest lists every asset accurately because it’s generated from the same export.

Update without hassle

If your brand refreshes or you tweak the icon, rerun Favvy and replace the manifest + icons in your repo. The HTML snippet automatically references the new files.

Manifest workflow

1. Design/update the icon.
2. Run Favvy, specify the short name, background color, and theme color.
3. Download the package, drop the manifest into your project, and commit.

It’s a painless way to keep your favicon metadata aligned with the design system.

Collaboration tip

Share the generated manifest with developers via pull requests so they can review changes alongside icons. Because Favvy standardizes the format, diffs become easy to read and approve.

Keep docs current

Include Favvy’s manifest output in your design system documentation. When future teams spin up microsites, they’ll know exactly which settings to reuse and how to regenerate assets without pinging the design org.