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, as conflicts may arise when importing collections and variables from different files. In Supernova, we do not allow conflicting token names. In the case of a potential name conflict, we prefix the token name with the collection name (Token name → Collection / Token name).
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, the import preserves variable references. However, if the referenced variable is from a different Figma file, you need to make sure to import the referenced variables first, and then alias variables.
If the referenced variables are not imported, only the raw token value will be imported into Supernova.
Does import assign token types based on Figma variable scopes?
Yes, it does! To be imported to corresponding token type, variable needs to have unique scope, otherwise it will be imported as Generic string or number. Learn more about scopes mapping.
Referenced variable contains invalid value. What happened?
When a dimension variable is out of range for its specific token type, it’s flagged with an error message. To fix it, adjust the variable in Figma so it falls within the allowed range. See a list of allowed ranges below.
|
Token type |
Value range |
|---|---|
|
Generic dimension, Letter spacing, Paragraph spacing, Z-index |
All values |
|
Border radius, Border width, Duration, Font size, Line height, Size, Space |
Equal to or greater than 0 |
|
Opacity |
Between 0 and 100 |
Referenced variable has incompatible unit. What happened?
Figma variables don’t have units by default, but when we import them into Supernova, we automatically assign units to fit. Most tokens are set to pixels, while opacity values are converted to percentages.
A current limitation is that an opacity token can’t reference or be referenced by another dimension token. To resolve this error for opacity token, remove the alias in the Figma variable.
|
Token type |
Unit assigned in Supernova |
|---|---|
|
Border radius, Duration, Generic dimension, Font size, Size, Space, Paragraph spacing, Letter spacing, Line height |
Pixel (px) |
|
Opacity |
Percentage (%) |
Is code syntax imported along with variables?
Yes, code syntax is imported along with variables.
The variable in Figma has a reference, but it was imported to Supernova without the reference. What happened?
We imported the token as a raw value because we couldn't determine the value of the referenced token. This happens when the referenced variable is from a different Figma file that was not imported to Supernova yet.
To resolve this issue:
- From the Supernova plugin, import the missing file containing the referenced variables (File 1 in above diagram).
- Now, push changes in the variables file containing the references (File 2 in above diagram).
If these steps do not resolve the issue, please contact our support team with more details.
Is it possible to edit the token in Supernova and then push it back to Figma?
No, imported tokens from Figma cannot be edited in Supernova. This is because Figma is considered the authoritative source for them — all editing, grouping, ungrouping, and deleting of tokens 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, the tokens will be grouped by collection name.
What happens when I change the variable or mode name?
When you push changes to Supernova from the plugin, the token or theme name will be updated in Supernova.
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.
Referenced variable contains invalid value. What do to?
When variable is referencing invalid value, such as negative value for opacity or incorrect unit for particular type, the easiest way to fix it is to update variable or alias directly in Figma and push updates via plugin.
Modes
The first mode from the collection was not imported to Supernova.
By default, the value of the first mode in a collection is imported as the base token value for the token in Supernova. To import the mode and preserve its name, you must also enable the Import as theme option.
Is it possible to import only selected modes to Supernova?
Yes! To do this, define the mode you would like to import for base token values, then enable Import as theme to select the modes you want to import.
Can I import modes as brands to Supernova?
Importing modes as brands is not yet possible, but the plugin supports importing selected modes as themes to any brand of your choice. We are exploring advanced brand support for future improvements.
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.
Multiple data sources in Supernova
Can I import design tokens from both Figma variables and Figma styles?
Yes, both Figma variables and Figma styles are supported. Variables are commonly used for importing colors and dimensions, while styles can be used for importing typography and shadows.
Please note that if you have a Figma style and a corresponding Figma variable with the same name, they will be imported 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.