Tokens Studio for Figma
  • Getting Started
    • Tokens Studio Plugin for Figma
    • Install the Figma Plugin
    • Pro Licence for the Figma Plugin
    • Join the Slack Community
    • Feature Requests - Featurebase
    • Changelog - Featurebase
  • Design Token Fundamentals
    • Intro to Design Tokens
      • Token Anatomy - Type
      • Token Anatomy - Value
      • Token Anatomy - Description
      • Token Anatomy - Name
  • Token Management
    • Token Types
      • Asset
      • Boolean
      • Border - Composite
      • Box Shadow - Composite
      • Color
        • Modified Colors (pro)
        • Gradient Colors
      • Dimension
        • Border Radius
        • Border Width
        • Sizing
        • Spacing
      • Number
      • Opacity
      • Other
      • Text (string)
      • Typography - Composite
        • Font Family
        • Font Weight
        • Font Fallbacks
        • Font Size
        • Line Height
        • Letter Spacing
        • Paragraph Indent
        • Paragraph Spacing
        • Text Case
        • Text Decoration
      • Composition (legacy)
    • Token Values
      • Token Values with References
      • Using Math in Token Values
    • Token Names
      • Token Name Technical Specs
      • Token Groups
      • Edit Token Names
    • Token Description
    • Token Sets
      • JSON View
  • Themes management
    • Themes (pro)
    • Themes that switch
  • Working in Figma
    • Variables and Tokens Studio
    • Styles and Tokens Studio
    • Export to Figma Guide
      • Export Options
      • Export Using Themes (pro)
      • Export Using Token Sets
      • Variables Skipped on Export
      • Styles with Variable References
    • Import from Figma Guide
      • Import Styles from Figma
      • Import Variables from Figma
        • Connect Themes to Imported Variables
        • Imported Variable Types and Token Types
    • Non-local Variables and Styles (pro)
    • Remove Tokens from Figma elements
    • Dev Mode in Figma
  • Settings Management
    • Plugin Settings
    • Base Font Size Setting
    • Token Format - W3C DTCG vs Legacy
  • Token Storage and Sync Integrations
    • Local Document - Figma File Token Storage
      • Figma Data Limits
    • Remote Token Storage Integrations
      • GitHub - Git Sync Provider
      • GitLab - Git Sync Provider
      • Bitbucket - Git Sync Provider
      • Azure DevOps - Git Sync Provider
      • JSONBin - Cloud Sync Provider
      • Supernova - Cloud Sync Provider
      • Tokens Studio Platform - Cloud Sync Provider
      • URL - Server Sync Provider
      • Generic Versioned Storage - Server Sync Provider
    • Multi-file Sync to Remote Storage (pro)
    • Manage Sync Providers
      • Edit Sync Provider
      • Change Active Sync Provider
      • Remove Sync Provider
    • Sync Changes to Remote Storage - Push and Pull
    • Branch Switching (pro) - Version Control
  • Inspect and Debug Tokens
    • Inspect Tokens
    • Remap Tokens
  • Transform Tokens for Development
    • Style Dictionary + SD Transforms
    • Official docs for Style Dictionary
  • Style Dictionary Playground
  • Troubleshooting
    • Reset Tokens from Dev Console
    • Tokens Studio Status
  • Open Source
    • Contribute
    • Shared Plugin Data
Powered by GitBook
On this page
  • Text Case - Token Type
  • Design decisions
  • Possible Values
  • Values that reference another Token
  • W3C DTCG Token Format
  • Transforming Tokens
  • Resources

Was this helpful?

Edit on GitHub
Export as PDF
PreviousParagraph SpacingNextText Decoration

Last updated 4 months ago

Was this helpful?

Text Case - Token Type

Text Case Tokens define a transformation to the capitalization of letters as an individual property to be composed within a . It is not intended to be applied to text elements directly.


Design decisions

Text Case defines that the system should transform the capitalization of letters in a text element regardless of how they are typed.

Text Case design decisions are typically used to:

  • communicate the visual emphasis of text or

  • standardize data inputs and data display to ensure consistency

Occasionally, they are used for creative styling decisions, for example, a personal blog where the author wants:

  • HEADINGS to have all letters capitalized.

  • contact details to appear in lowercase.

When we apply a Typography Composite Token to a text layer in Figma, these Text Case values will change the letter casing:

  • All letters appear as typed - null

    • By default, the system will not transform the capitalization of letters

  • All letters capitalized - uppercase

    • Examples:

      • button labels

      • list of countries presented as abbreviations

  • No letters are capitalized - lowercase

    • Examples:

      • email address listed in a contact section

      • username entered in a sign-up form

  • The first letter of each word is capitalized - capitalize

    • Examples:

      • full name entered in a sign-up form

      • list of city names


Possible Values

The syntax used to write string values for Design Tokens is important, so be sure to write your Text Case Token value with all lowercase letters and ensure there are no spaces.

Hard-coded Values

The Text Case Token has a few specific string Values depending on your needs.

null

Most of the time, text will appear as typed; the Text Case Token Value will be:

null

uppercase

When all letters should be capitalized, set the Text Case Token Value to:

uppercase

lowercase

When none of the letters should be capitalized, set the Text Case Token Value to:

lowercase

capitalize

When the first letter of each word should be capitalized, set the Text Case Token Value to:

capitalize

Many people confuse Figma's "capitalize" with "title case," but they are different.

  • Title case has some words capitalized while others remain lowercase.

    • For example Hyma for Tokens Studio

  • Capitalize transforms all words.

    • For example Hyma For Tokens Studio

Not supported by Figma

Additional text-transform properties commonly used in CSS are not supported in Figma, such as Full Width.

You can still create Text Case Tokens with these Values using the Tokens Studio plugin.

When you apply them to design elements in Figma, the Token will be present and visible to engineers inspecting the design element in Figma, but the Token won't interact with the Letter Case property in Figma's UI.

Values that reference another Token

When trying to reference another Token as the Value for a Text Case 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 = textCase


W3C DTCG Token Format

Text Case is not yet an official Token type in the W3C Design Token Community Group specifications.

Tokens Studio has added Text Case as an unofficial Token Type in anticipation of its inclusion in the W3C specs in the near future.


Transforming Tokens

When transforming Test Case tokens, there are no specific transforms to be aware of.

Running the SD-Transforms pre-processor as part of the generic package will prep your Text Case Tokens for Style Dictionary.

However, Text Case, as part of Typography Composite Tokens, requires the SD-Transforms option to expand composite Tokens into multiple Tokens.


Resources

Mentioned in this doc:

Figma resources:

CSS resources:

Community resources:

  • None yet!

Known issues and bugs

  • None yet

Requests, roadmap and changelog

  • None

In , this property is called text-transform.

→

SD-Transforms -

Style Dictionary -

Design Tokens Community Group -

Design Tokens Community Group -

Design in Figma -

MDN Web Docs -

Tokens Studio Plugin GitHub -

CSS
SD-Transforms Read-Me Doc, Using the preprocessor
Read Me
https://styledictionary.com/
W3C Draft
9.7 Typography
Explore Text Properties, Letter Case
Letter Case
Open issues for Token Type Text Case
Typography Token

🐞 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.

💡 Something to share?

community Slack
submit it on our feedback tool
Submit it here!
https://feedback.tokens.studio/
Creating a new Text Case Token in the Tokens Studio Plugin for Figma.
The Typography Composite Token form is open, with each property referencing another Token. The Text Case property is highlighted.
Page cover image

However, like all Token Types, you can "force" a reference by manually entering the Token Name between curly brackets.

For example {token.name.here}

The value will show a broken reference until the originating Token Set is marked as enabled.

Jump to the guide on Token Values with References by selecting the card below to learn more.

Token Values with References

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.

Style Dictionary
@Tokens-studio/sd-transforms

Make sure you look at the generic SD-Transforms package to include this option, which allows you to further customize this transformation further using Style Dictionary.

→

"object, object" When you transform your Typography Tokens and they show "object, object", it means your SD-Transforms configuration needs to be adjusted to include "expand".

SD-Transforms Read-Me Doc, Using Expand