Last updated
Was this helpful?
Last updated
Was this helpful?
Border Radius was one of the first Token Types we supported in the plugin.
Since then, a lot has changed.
The Design Tokens Community Group (DTCG) hosts a Token specification on the W3C community group pages for web standards. Although it's in draft form, the tools and technologies working with Design Tokens are trying to align with the W3C DTCG specification.
If we want to fully align with the spec, it requires Tokens Studio to phase out the Border Radius Token. However, we believe the choice should be yours!
If aligning with the W3C DTCG spec is important to your project, we suggest using Dimension Tokens instead.
If you love Border Radius Tokens and want to make your voice heard, we've set up a forum in our feedback tool where you can leave your comments! Hopefully with enough support the DTCG may reconsider having Border Radius as its own Token Type.
→
Border Radius defines the corner roundness of a design element, such as frames, groups, or polygonal shapes.
The Border Radius Token supports numeric values with or without a unit.
The syntax used to write values for Spacing Tokens is important.
Be sure to avoid any spaces between numbers and units of measurement.
Units are always written in lowercase.
For example:
Rem units (rem)
To support responsive design, you can define your Border Radius Token in rem units
, and the plugin automatically converts the value to the pixel equivalent when applying the Token in Figma.
For example, a Border Radius Token with a value of 1rem
will appear as a 16px
corner radius in Figma.
When you have design elements that should remain static even when users change their preferences, Border Radius Tokens can be defined in pixel units.
For example, 4px
.
When trying to reference another Token as the Value for a Border Radius Token, you will see Tokens in the dropdown list that are:
Living in Token Sets that are currently active.
In the left menu on the plugin's Tokens page, a checkmark is visible next to the Token Set name.
Token Type is compatible:
The same = borderRadius
number
dimension
You can define the value of a Border Radius Token to mimic how multi-value Border Radius properties are written in CSS.
When you click to apply the token value (without right-clicking), the plugin will apply the border radius based on the number of values in your token.
Single value - For example, 10px
Applies the value to all corners.
Two values - For example, 8px 64px
The first value is applied to the radii on the top and bottom.
The second value is applied to the radii on the right and left.
Three values - For example, 16px 8px 32px
The first value is applied to the radius on the top.
The second value is applied to the radii on the right and left.
The third value is applied to the radius on the bottom.
Four values - For example, 2px 4px 8px 16px
The first value is applied to the radius on the top.
The second value is applied to the radius on the right.
The third value is applied to the radius on the bottom.
The fourth value is applied to the radius on the left.
You can also write multiple value Border Radius Tokens with references. For example, {radius.sm} {radius.md}
.
Figma does not support Variables with multiple values!
If you export your Tokens to Variables in Figma, multiple value Tokens will be skipped, as Figma only supports single values.
A Border Radius Token defines the corner roundness of polygonal shape, frames, groups or graphic elements in Figma when the Token is applied.
You can apply a Border Radius Token to all sides of the design element at once, or each side independently.
With one or more elements selected in Figma, right-click on the Border Radius Token Name in the plugin to see the its options.
Select your desired design property by clicking on it to apply the Tokens value instantly.
When transforming Border Radius Tokens, there are some specific configurations to be aware of.
The preprocessor in the SD-Transforms package will automatically convert the Tokens Studio specific Token Type of borderRadius
to align with the DTCG Format Token Type of dimension
.
Token Values entered as a number without a unit will be converted to a number with pixels as a unit.
Mentioned in this doc:
Style Dictionary - https://styledictionary.com/
None yet!
If it has multiple values, it will apply the values to the independent properties defined in the Tokens Value.
For independent corner styling, you can repeat the steps above and apply different Border Radius Tokens to each corner position of the same design element. Or, you can modify your Border Radius Tokens to have .
→
→
SD-Transforms -
Design Tokens Community Group -
Design Tokens Community Group -
Design in Figma -
Tokens Studio Plugin GitHub -
Color modifiers break when borderRadius token is renamed
W3C DTCG Spec - Unofficial Token Types -
All Token Types that accept numeric values can use math equations to calculate their value in Tokens Studio.
Jump to the guide on Tokens with Math Values by selecting the card below to learn more.
Rem Units act as a multiplier of the base font size, so when a user changes their preferences to a larger font size or uses a zoom feature in your product, elements defined in rem units will respond accordingly.
The value of 1rem
can be configured in the .
Once a Token has been applied, it will remain attached until you manually remove it.
However, like all Token Types, you can "force" a reference by manually entering the Token Name between curly brackets.
For example {token.name.here}
Jump to the guide on Token Values with References by selecting the card below to learn more.
Engineers typically transform Tokens used in code with , which is tool-agnostic. Tokens coming from Tokens Studio require an additional step: , an npm package that prepares Tokens for Style Dictionary.
💡 Something to share?
🐞 If you are experiencing an issue not listed here, please reach out to us on the Troubleshooting channel of our , , or send us an email support@tokens.studio
💌 Visit to contribute or subscribe to updates.