Skip to main content

Persisting (auto-applied) themes

Plugin Feedback

💡 Current


When selecting and applying a theme using Tokens Studio, all components instances in the Figma file get the selected theme applied to them.

Pulling a new instance of a component, or switching to a different component variant (when not sharing an internal base component), result it having these components not having the desired theme, and forcing users to re-apply the theme, making a pretty disruptive experience to design.

————


✅ Desired

Enable the desired/selected theme to be automatically applied when:

  1. A new component instance is pulled into the file

  2. A component already in the file and themed changes configuration (ex switching to a different variant, size, and whatnot)

————

🚀 Benefits

  1. Enable individuals or smaller teams not on Figma Enterprise (4 modes limit) to still have a convenient way for their users to switch themes and have a less disruptive workflow.

Posted by aln-design ·
Status: ☑️ Completed2 comments

Log in to comment and vote

Comments2

  • Jan Six

    Team•

    Aug 30, 2025

    thanks for raising this @aln-design - i like the idea, we should be able to use figma’s on(“drop”) event for when a user drags a component in. i dont know if it would be expected that we also theme change if the variant changed. perhaps we could introduce a setting that keeps this mode on? it could lead to some performance issues if we do it always

    • aln-design

      •

      Sep 2, 2025

      Yes having a setting to keep it on/off would help! Reason I’m mentioning variant change is a Designer designs for a specific desired theme, they would expect that theme to be always there whether they pull a component from the asset panel or changing variant (similar to what happens if using Variable modes), so there is no confusion and users can trust it’s the right theme.

      That can be particularly useful for some themes that can be look similar so a different themed component isn’t used/switched accidentally without users noticing it (that happened to designers in my org).