Which components are used, and where
Instances, nested instances, files, folders and detached copies for every library component.
Free alpha, by invitation
See how your team uses your design system
A plugin for Figma Design and Dev Mode. Design system adoption and governance for Figma teams on any plan.
Free during the alpha. The audit of the open file needs no account.
1Free audit of any open file. No account, nothing sent.
2How many product files, and how old the oldest scan
3Button copy, named like Button: 48 instances
Three questions
Answers across the files your team scans
Counted in the files your team scans. The panels show a sample workspace with made-up data.
Which aren't used in any product file
Not placed directly or inside other components. Check the signals before you retire one.
Where people may have rebuilt them
Local components named like a library component, the most used first. Click one to go to it in Figma.
Variables and styles
Find library components that use raw values
Your team picks the properties to check, such as fill, stroke or padding. Checks shows which of your libraries' published components use raw values instead of your variables and styles.
- How many of a library's components have raw values, and the share of checked properties that use variables or styles.
- What changed since the previous scan of the library file.
- Each component's properties and variants with raw values. In the library file, select each layer; from any other file, Open in library file.
The workspace owner chooses what to check in Settings. The plugin never changes your files: it shows you the layers, and you fix them.
Trends
See adoption change week by week
Each rescan keeps a file's history, so the plugin shows what was added and when.
- Instances added to a library's components, week by week for the last 12 weeks.
- Compare up to four libraries on one chart, for example an old library and the one replacing it.
Each component also shows its instances over time. Numbers move from one scan of a file to the next, so a file nobody rescans adds nothing.
Deprecated components
Find old components that are still in use
Start a component's name or description with a word your team picks, Deprecated by default. The plugin lists the ones still used, so you know where to replace them.
- A Deprecated view of each library: components still used, most instances first, then those ready to remove.
- A tag in each component's details, and in This file the deprecated components the open file still uses.
The workspace owner sets the word in Settings, and a change needs no rescan. The free audit uses Deprecated.
Free audit
Audit any open file, free and local
Run Design System Census in any design file and click Audit this file. No account, and nothing leaves your computer.
- Library and local instances, and the detached copies of each library component.
- Local components named like a library component the file uses.
How it works
Scans run when your team clicks
Plugins can't run in the background, so each file's numbers are as current as its last scan.
Set up a workspace
Sign in, create a workspace and invite your team. Get started in the plugin lists each step.
Scan your library and your team's files
Open each one and click Scan this file. A file joins the workspace with its first scan.
Rescan when a file changes
Click Rescan with Design System Census in Figma's right panel, or Rescan at the bottom of the plugin.
Every number says how fresh it is
Libraries, Checks and Files show how many product files they count and how old the oldest scan is. Try it:
Rescan the oldest fileShow the old scan again
12 product files, oldest scan 41 days ago.12 product files, oldest scan 33 days ago.
Rescanned. The oldest scan is now 33 days ago.
Privacy
Your designs stay in Figma
The plugin analyzes the open file on your computer and sends only derived data to my server in Frankfurt, Germany.
What the plugin never sends
The content of your designs: layers, text, images, comments, and values such as colors or sizes. The free audit sends nothing at all.
What I keep once you sign in
Counts, keys and IDs, the names of files, folders, components and findings, which properties use raw values, and who scanned each file when.
Delete it at any time
Remove a file, delete your account or delete the workspace in the plugin. Deletion takes effect at once.
No ads, no tracking and no AI training on your data. The privacy policy lists everything I keep and for how long. A data processing agreement is available on request.
Which Figma plans does it work on?
All of them. The free audit works in any file. Tracking your library across your team's files needs a plan with team libraries: Professional, Organization or Enterprise. Where Figma's own library analytics exist, it adds what they don't show, such as local lookalikes and library components that use raw values.
Who on my team can use it?
People with a Full seat, in Figma Design and Dev Mode, and people with a Dev seat, in Dev Mode. Collab and View seats can't run plugins in Figma Design or Dev Mode.
How do I get the alpha?
Fill in a short form about your team and your library. If the alpha fits, I send you the plugin with a short setup guide. During the alpha it runs in the Figma desktop app.
Does it change my files?
A scan adds a small hidden label, so the next scan finds the file, and a Rescan with Design System Census button. Nothing else changes. The free audit changes nothing.
Can we track several teams or clients?
Yes. Set up a workspace for each, then switch between them in the plugin's workspace menu without signing out.
Are these Figma's numbers?
No. Design System Census counts what it finds in the files your team scans, as of each file's last scan. Figma's own library analytics measure differently, so the two don't match.
What does the alpha cost?
Nothing, and I ask for no payment details. A workspace tracks up to 250 files; write to me if you need more.
Try it with your team
The alpha is free and open to a few teams. Tell me about your team and your library.