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
  • Figma Data Limits
  • Why is this happening?
  • How it works
  • Sync Tokens to remote storage to avoid issues
  • Remote storage guides
  • Resources

Was this helpful?

Edit on GitHub
Export as PDF
PreviousLocal Document - Figma File Token StorageNextRemote Token Storage Integrations

Last updated 19 days ago

Was this helpful?

Figma Data Limits

You may have noticed the size of your Token project is showing in the footer of the plugin.

This can happen when you:

  • Import a large volume of Styles or Variables from Figma.

  • Upload a Token project into Tokens Studio from a JSON file or folder.

  • Expand an existing Token project to have more Token Sets or Themes.

As soon as the Plugin detects the project size is at 100kb and set to Local Document storage:

  • The footer of the Plugin will display your current file size.

  • You can select the file size to open a modal with easy access to more information.

    • Selecting the View Storage Settings actions brings you to the settings page where you can add a new sync provider.

Having a Token project that is over 100kb isn't a problem, it means you are doing great work! However, Figma's efforts to tackle their performance issues means Plugins like Tokens Studio are being limited by Figma.

Why is this happening?

The Tokens Studio Plugin uses Figma's plugin API to to interact with your design elements, styles and variables.

As of May 2025, Figma is enforcing a limit on how much data a plugin can store in a Figma file via its setSharedPluginData API call.

This means, if you are using Local Document storage for your larger projects (small component libraries, lots of variables etc), you are likely to hit the 100kb data limit.

The data limit does not apply if you are syncing your Tokens to a remote storage provider as the Token project data is being stored outside of the Figma file.

How it works

There is no action required by you! The plugin will work some magic under the hood to keep file sizes as small as possible.

Whats happening under the hood?

When the Plugin detects the project size is at 100kb and set to Local Document storage, it will:

  • Compress the data and break it into chunks smaller than 95kb when writing to Figma

  • Combine the chunks and decompress when reading from Figma.

When the Plugin is storing Token data remotely and you close the Plugin before you have pushed changes to your sync provider, the Plugin will:

  • Store the changes you haven't pushed using a different API figma.clientStorage which stores it locally to your machine.

  • Client storage still has a data limit, but it is much larger (5mb).

However, this process takes time! You will notice the Plugin starts to perform tasks slower as your file size increases.

The best way to avoid slowdowns in your workflow is to store your Tokens remotely using one of our integrated sync providers.

Sync Tokens to remote storage to avoid issues

Figma's 100kb data limit only applies when a plugin has to store (or save) information locally to the Figma File.

This means, if you switch to a remote storage provider, the data limit does not apply and the plugin does not perform the extra steps listed above, giving you optimal performance in your Figma file.

Remote storage guides

If you haven't set up a remote sync provider yet, don't worry! These guides will walk you through it.

If you don't know which sync provider to use, try Github as a free option.

Resources

Figma API Documentation Mentioned:

Known issues and bugs

Requests, roadmap and changelog

  • None yet

The total size of your entry (namespace, key, value) cannot exceed 100 kB. -

Figma Developer -

Figma Developer -

Tokens Studio Plugin GitHub -

Figma Developer, Plugin API
Plugin API setPluginData
Plugin API figma.clientStorage
Open issues for Sync Local Storage
The user flow for Token projects that exceed Figma's 100kb file size limit is pictured. On the right, the Tokens Page of the plugin has the file size highlighted in the bottom left. Selecting the file size opens the informational picture in the middle. The far right image shows the Settings page of the plugin currently set to store the Token data as Local Document, with the Add new sync provider action highlighted.
Cover

Add a new sync provider to start storing your tokens remotely.

Cover

Switch from local to remote storage if you already have a sync provider set up.

Cover

See all the remote Token storage providers that Tokens Studio is integrated with.

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