How to find unused, duplicate and hand-typed colors in a Framer project
By Jake Marsh · Updated
To find unused, duplicate and hand-typed colors in a Framer project, open Tokenmend's Audit tab and click Scan project. It lists every color and text style with where it's used, styles nothing uses, duplicates, colors typed by hand on frames and borders, text layers with no text style, and every font in use. From there, bind hand-typed colors to a style, merge duplicates, replace a font and delete unused styles. The scan and Download audit CSV are free.
What the audit shows
| Section | What it lists |
|---|---|
| Styles | Every color and text style, and how many layers use each |
| Unused | Styles not on any frame or text layer and not used by a text style |
| Duplicates | Color or text styles with the same values under different names |
| Colours typed by hand | Fill and border colors set directly on layers, grouped by value |
| Text without a style | Text layers that don't use a text style |
| Fonts | Every font in the project, with Replace font |
Steps
- Open Tokenmend (Cmd+K or Ctrl+K) and click Audit.
- Click Scan project. It reads every color style, text style, frame and text layer.
- Bind hand-typed colors. Under Colours typed by hand, each value has a menu of your color styles, with the same or a close match marked. Set Match within to catch near misses (0 means exact). Click Select to see the layers on the canvas, choose a style and click Bind chosen colours.
- Merge duplicates. Each duplicate set has a Merge into button naming the style that stays; layers using the others move to it.
- Replace a font across text styles and loose text layers. Tokenmend picks the nearest weight in the new font.
- Delete unused styles. Tokenmend checks the project again before deleting.
- Click Download audit CSV for a client or a ticket, then Scan again to confirm.
Before you delete
The scan can't see inside code components or CMS rich text. A style used only there looks unused. If your project uses either, check those styles before clicking Delete unused. The re-check before deleting covers layers and text styles, not code.
Turning the clean set into tokens
Once the styles are tidy, Export writes them as W3C design tokens (one file, or a light and a dark file), CSS custom properties with a dark scheme, or a Tailwind v4 theme, so developers get the same names. For importing tokens the other way, see how to import Figma variables into Framer.
What it costs
Scanning and the CSV are free. Binding, merging, replacing a font or deleting is one of the trial's 10 runs over 7 days, each changing up to 40 styles and 200 layers, with no card. After that Tokenmend is $12 a month, $89 a year or $119 once per seat. Plans are on the Tokenmend page.
Tokenmend
Turn design tokens into Framer color and text styles, keep them in sync, audit and clean up styles, and export them to CSS, Tailwind and JSON $12 a month or $89 a year per seat, or $119 once.
Questions
Does binding a color change how the layer looks?
Not with an exact match. With Match within above 0, the layer takes the style's color, which can differ slightly; the menu marks those as close.
Is anything deleted without asking?
No. Deleting unused styles is a button you press, and Tokenmend checks the project again first, so a style that got used since the scan is kept.
Why are there two styles with the same color?
Often one was made for a component and another for a page. Duplicates lists them so you can keep one.
Can I share the results with a client?
Yes. Download audit CSV saves every style with its uses, plus the duplicates, unused styles and hand-typed colors, and it's free.
More Tokenmend guides
- How to set Framer text style breakpoints from type tokens
- How to import Figma variables into Framer as color and text styles