Applying to Figma

Apply is the last step and the only one that changes your Figma file. Here is exactly what it writes, what it leaves alone, and what you get besides variables.

Real variables, with their aliases intact

Collider writes Figma variables, not a flat dump of values. Foundations land as primitives. Semantic roles land as aliases pointing at those primitives, mode by mode. The structure you reviewed in the plugin is the structure in your file.

Collider writes only into the collections it owns. A collection you created yourself keeps its name and its contents, even when the name resembles one of ours.

Text styles and effect styles

Type roles are compiled into named Figma text styles, and shadow and elevation tokens into named effect styles. Both are matched by name, so applying twice updates the existing styles instead of piling up duplicates.

These are secondary to the variables. If a style cannot be created, you are told, and the variables still land. The apply never half-fails silently.

A documentation page

Collider draws a Foundations page in your file, using real Figma frames rather than an image, with the colour and typography sections of the system you just applied. It is bound to the variables that were written, so it shows what is actually there.

A copy in your account

The finished system is saved to your Isotop account, so it exists outside the file it was applied to. You can open it later, and export it to JSON when you need the tokens somewhere other than Figma.

Changing or cancelling your plan

Your work is yours. Changing or cancelling a plan never deletes it: variables, aliases and tokens stay intact. Downgrading locks the paid editing features in the plugin, and everything you already created stays visible and editable.

We use cookies. Necessary cookies keep Isotop secure and signed in. With your consent we also use analytics (Google Analytics) to improve the product. See our Cookie Policy and Privacy Policy.

Applying a system to Figma | Isotop