Collections
Will the collection name be imported?
Yes, each imported collection generates a name option in the Collection token property and is subsequently shown as a column in the token table.
Is it possible to import only selected variables to Supernova?
Currently, it is not possible. We import all variables from each selected collection.
If you have a specific use case in mind, please let us know through our feedback form. Please provide as many details as possible about why it is important to you.
Is it possible to import collections from multiple Figma files?
Yes. Be cautious, conflicts may arise when importing collections and variables from different files. In Supernova, we do not allow conflicting token names. Instead, in case of a potential name conflict, we prefix the token name with the collection name (Token name → Collection / Token name).
It is important to note that we do not currently preserve aliases between different Figma files. Any external aliases will be resolved and imported to Supernova as raw values.
Is it possible to push modified collections only?
The beta version of the plugin does not support pushing changes from modified collections only. We are currently exploring this feature for future improvements.
Can I remove collections that I previously pushed to Supernova?
The beta version of the plugin does not support removing previously pushed collections. However, we have plans to include this feature in future updates.
Do we need to publish the collection before pushing it to Supernova?
Publishing a collection is not necessary. The plugin will push all selected collections and their content.
Variables and aliases
Does the import preserve variable references?
Yes, but only if the alias is from the same Figma file. If the alias is from an external library or if we can't import the aliased variable for any reason, we break the original alias and only import the token with the raw value into Supernova.
Does the import assign token type based on Figma variable scopes?
The beta version of the plugin does not support variable scopes. We are currently exploring this feature for future improvements which would allow import number tokens e.g. as Border radius or Size token types.
Is code syntax imported along with variables?
The beta version of the plugin does not import code syntax. We are currently exploring this feature for future improvements.
The variable in Figma has a reference, but it was imported to Supernova without the reference. What happened?
We imported the reference as a raw value because we couldn't resolve the alias for some reason. This can occur when the reference is from a different Figma file. If that’s not the case, please contact our support team with more details.
Is it possible to edit the token in Supernova and then push it back to Figma?
Figma-imported tokens cannot be edited in Supernova. Figma is considered the authoritative source for them, so all editing, grouping, ungrouping, and deleting of tokens imported from Figma should be done within Figma.
What if there are variables with the same name in two different collections that I want to import?
When variable names conflict between collections in Supernova, we group the design token into a new group using the name of the collection.
What happens when I change the variable or mode name?
The token or theme name in Supernova will be changed when you push changes to Supernova from the plugin.
Is it possible to import boolean variables to Supernova?
The beta version of the plugin does not import boolean variables from Figma.
If you have a specific use case in mind, please let us know through our feedback form. Please provide as many details as possible about why it is important to you.
Modes
The first mode from the collection was not imported to Supernova.
The value of the first mode in the collection was imported as the default value for the token in Supernova. Only the additional modes in the collection are imported to Supernova as themes.
Is it possible to import only selected modes to Supernova?
The beta version of the plugin does not support importing only selected modes. We import all modes from each of the selected collection.
If you have a use case for this in mind, please let us know in our feedback form. Share as many details about why it’s important to you as possible.
Can I import modes as brands to Supernova?
The beta version of the plugin does not support brands. Currently, modes in Figma are mapped to themes in Supernova. We are exploring brand support for future improvements.
Multiple data sources in Supernova
Can I import design tokens from both Figma variables and Figma styles?
Importing from both Figma variables and Figma styles is supported. Variables are commonly used for importing colors and dimensions, while styles are used for importing typography and shadows.
Please note that if you have a Figma style and a corresponding Figma variable with the same name, we will import them as a single design token. The Figma variable will be used as the source for this token.
Can I import design tokens from both Figma variables and Token Studio?
No. If you're using the Tokens Studio integration to import styles, you can't import styles from any other Figma design data sources. Learn more about Using Tokens Studio as a data source.
Deleting tokens
Can I delete Supernova tokens that were imported from Figma?
Currently, it is not possible to delete imported tokens from Supernova. We are considering adding this feature for future improvements.
However, there is a workaround available. First, delete the variable in Figma and push the changes to Supernova. We will then convert it to a Supernova token, which can be deleted from Supernova.
Why aren't design tokens automatically removed when variables are deleted from Figma?
At present, we do not automatically remove any tokens from your design system. This is because these tokens may be used in documentation blocks or there may be automatic hooks created for exporting to code. When a token is removed from the Figma data source, we simply disconnect it from its Figma counterpart.
The decision to retain the tokens in the design system was made to preserve these relationships and provide design system managers with complete control over which elements are deleted from the system and which are not.
However, we are aware that this approach may cause maintenance issues for some users. Our team is actively exploring how to make design token management more efficient and automated.