Styler is the most-used Figma design system plugin, with 229K users. It creates, renames, extracts and detaches styles in bulk, which is the slow part of setting up a library or migrating an old one.
Top 20 picks
Styler
#1 · 229K users
Quick answer
Most used
by Andrei Iancu
Best free audit before handoff
by Daniel Destefanis
Best for style guide pages
by Eddy Salzmann
Outside the ranking · Disclosure
The full list
Generate component specs including anatomy, props and layout & spacing
Free + $8/mo · 5.5K likes
Apply styles and variables to all your designs with one click!
Free + $15 · 3.2K likes
Free · 1.8K likes
Create the brillant Color Styleguide page using your local Color Styles.
Free · 1.4K likes
Create, attach, clone and move components in a couple of clicks without losing overrides! 🔥
Free + paid · 2.3K likes
Generate complete design systems from Bootstrap, Tailwind, Material UI & more — with AI-powered layo
Free · 174 likes
Automatically generate text style guides based on your defined local text styles.
Free · 485 likes
View and control all nested variants and component properties in selection
Free · 623 likes
Free · 135 likes
Free · 613 likes
Generate and sync a full Figma library from Storybook or Histoire
Free + paid · 669 likes
Automatically generate color style guides based on your defined variables including modes
Free · 393 likes
Buying guide
Figma's native tools cover the building blocks: components with variants and properties, styles, variables with modes, and published libraries. Where teams reach for plugins is auditing and documenting. That means finding layers with hardcoded values, generating style guide pages, tracking down instances, and deleting components without breaking files. Most of this top 20 does one of those jobs.
Several plugins here were built for color and text styles before variables existed. If your system runs on variables, check the plugin handles them; Kigen, Auto Documentation and Color Variables Style Guide Generator do. For token export and syncing, see our variables and tokens list.
Older plugins only read styles. If your library is moving to variables, a style-only auditor will report bound variables as errors or miss them entirely.
Design system work happens across hundreds of layers. Favour plugins that act on a whole page or file, and test on a copy first.
Generated style guide pages go stale. Pick a tool you can rerun after changes rather than one that draws a one-time snapshot.
Moving or deleting main components can break instances in other files. Plugins like Master and Safely Delete Components exist to keep overrides and usage intact.
If your components live in Storybook, Storybook Connect and story.to.design close the gap between the Figma library and the coded one.
FAQ
Generate foundations pages for colors, type and variables with a plugin like Auto Documentation, then write component specs covering anatomy, spacing and properties. The design specs guide explains what each spec should include.
Variables store single values (color, number, string, boolean), support modes like light and dark, and can reference each other. Styles can hold composite values that variables can't, such as text styles, effects and multi-layer fills. Most systems use both.
Instance Finder lists the instances of a component in the current file, and Select all instances is another option for inspecting and selecting them. For usage across files, check library analytics if your plan includes them.
Run Design Lint or Roller to find layers with hardcoded colors, fonts and effects instead of styles. Fix issues from the plugin panel, then rerun until the list is clear.
Keep one property per axis (size, state, type) and consistent value names. Simple Sort orders variants in a set. See our component variants guide.
Keep exploring
variables and design tokens
See the top picksdeveloper handoff and Dev Mode
See the top picksrenaming, sorting and cleaning up layers
See the top picksGuides