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
  • URL sync setup guide
  • How it works
  • URL sync setup instructions
  • Configure the Tokens Studio Plugin
  • Shared source of truth
  • Resources

Was this helpful?

Edit on GitHub
Export as PDF

URL sync setup guide

If your Design Token storage is set up on a local server, you can access your Token files (via their URL) in the plugin using the URL Sync option.

URL Sync operates in read-only mode.

  • This means you can't use the Tokens Studio plugin to create or modify your design Tokens, but you can apply your Tokens to design elements in Figma.

  • You'll need to modify the Token JSON files stored on your server and pull the updates into the plugin.

This means the Design Tokens living in code are the source of truth for our design decisions, which can be shared between design and development teams.

This guide outlines how to access your Token files stored on your local server using the URL Sync provider option in the plugin.

How it works

  • Once your Token JSON files are stored on your server, capture the URL.

  • Configure a new URL sync provider within the plugin.

  • Use the plugin to sync Design Token changes between your server and Figma design files.


URL sync setup instructions

If you haven't already, store your Design Token JSON files on your server.

1. Server URL

Copy the URL on your server where your Token JSON files are stored. Store the URL somewhere safe, as it's needed for the plugin configuration.

2. Check server headers

Headers are the server authentication instructions for the plugin.

  • Refer to your server technical documentation for more details on headers.

If your server requires authentication:

  • Store the headers as a JSON object in the headers field.

  • Access-Control-Allow-Origin header must be *

  • Copy the required headers and

    • Store them somewhere safe, as they are needed for the plugin configuration.


Configure the Tokens Studio Plugin

In Figma, open the Tokens Studio plugin and navigate to the Settings page.

  • Under the Sync providers section, select the Add new button to see a list of all Token storage providers.

  • Select URL

Add credentials for URL sync

You'll need the information saved from the steps above to complete the Tokens Studio sync configuration form.

1. Name

This is a nickname that shows up in the plugin settings page later on to identify this specific sync provider configuration.

  • Choose something memorable to you and your project.

  • Example: Hyma brand exploration

2. URL

3. Headers

Example: `("Some-Header-Key":SomeHeaderValue)

Save and do the initial sync

Save to confirm your credentials, and follow the prompts in the plugin to finish setting up the sync to your server.


Shared source of truth

As you work in the plugin, pull indicators remind you to stay in sync with your URL storage.

Once your Token JSON files are synced to your URL storage, you have a shared source of truth between Designers and Engineers!


Resources

Mentioned in this doc:

Community resources:

  • None yet!

Known issues and bugs

Requests, roadmap and changelog

    • How might we improve the experience of working with sync providers in general?

PreviousTokens Studio Platform - Cloud Sync ProviderNextGeneric Versioned Storage - Server Sync Provider

Last updated 5 months ago

Was this helpful?

→

Enter the complete URL you saved from

The authentication headers you saved from .

SD-Transforms -

Style Dictionary -

Tokens Studio Plugin GitHub -

🧑‍💻

↕️

🔐

Here's an example Token JSON file stored on a server URL.
Read Me
https://styledictionary.com/
Open issues for URL sync
Sync to external token storage enhancements - Feature Request
Git sync enhancements - push, pull, merge, branching - Feature Request
Data security info request - Feature Request
step 1 above.
step 2 above
Page cover image

→ Read the Add New Sync Provider guide for more details.

Manage Sync Providers

Transforming Tokens

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.

The various Token Types supported by Tokens Studio have unique transforms to be aware of.

Read the Sync Changes guide for more details

Style Dictionary
@Tokens-studio/sd-transforms
Token Types
Sync Changes to Remote Storage - Push and Pull

💡 Something to share?

Submit it here!

🐞 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

community Slack
submit it on our feedback tool

💌 Visit to contribute or subscribe to updates.

https://feedback.tokens.studio/