Changelog

✨ New Features

• OKLCH Color Support
  OKLCH colors are now supported, extending the existing support for RGB, HSL, and hex colors.

🐞 Bug fixes

• Fixed a crash when exporting large token sets (1000+ tokens) to Figma variables. The export now runs smoothly with batching.

• The plugin now remembers your theme choice when creating variables in a file, so you don't have to reselect it every time.

This release includes improvements to how exports work and a few fixes to make syncing and token handling more reliable.

✨ Improvements

• We've changed the default export mode from single file to multiple files to improve clarity and version control during sync.

• If tokens fail to load due to network or credential issues, you’ll now see a retry button in the error callout

🐞 Bug fixes

• Fixed: The “Recover local changes” prompt now reliably appears when reopening the plugin with unsaved changes — even if you didn’t click 'Apply to Selection'.

• Fixed: Empty braces message now correctly appears when studio sync or pull fails.

• Fixed: Tokens weren’t loading at startup even when credentials were correct — now they do.

Fixed a bug with remote storage providers and our check for recovering local changes causing the Enter credentials to be shown

Just like you, in this post-Config world, we’ve had to make a few adjustments.

We took the opportunity to sneak in one of your top-requested features - enhancements to search in the Plugin, and our technical docs!

💾 Changes to data storage

Figma has limited plugins to share a maximum of 100KB of data through their APIs.

But don’t worry, we’ve worked some magic under the hood to make sure your workflow isn’t disrupted! No action is required by you, but there are some things to be aware of.

If you sync your tokens to a remote storage provider:

• The only difference in your workflow is when you close the plugin before pushing changes to remote.

• As of today, when you reopen the plugin, you’ll still see the option to “Recover local changes”, but under the hood we are saving that data to a different source which is specific to your private Figma Client Data storage.

If you store your Tokens locally to the Figma file:

• When your Token project hits the 100kb limit, we’ll show you the project size in the footer of the plugin.

• We’re compressing your Token Data, and for projects above 100kb we also chunk into individual packets to make sure your workflow isn’t disrupted.

• However, this process takes time, and as your Token project grows, you’ll notice the Plugin slows down.

• If you're consuming Token Studio data via the sharedPluginData API with another plugin or with the console, you'll need to access this with a different console command.

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

→ Learn more about local storage data limits and how to switch to remote storage for free.

On GitHub

• 3310 - Move "restore" token values to client storage for remote sync providers

• 3313 - Add size check, indicator and dialog for local document storage

• 3328 - Add compression to storing and reading sharedPluginData (themes and token values)

❇️ New Feature - Search by Token Name Across Multiple Token Sets

When you enter a Token Name into the search input on the Tokens Page, the Plugin now searches across all Token Sets making it much easier to find the needle in the haystack!

You’ll see:

• Count of Tokens found

• Token Set list on the left is filtered to show you where the search result has found a match.

On GitHub

• 3128 - Add filter to global search

🐞 Bug Fixes

• 3331 - Fixes an issue where if your font family was a number we were unable to generate variables

→ Learn more about Font Family in the Plugin

🤓 A new an improved technical docs site

You may have noticed that https://docs.tokens.studio has gotten a glow up!

↳ A new information architecture to help you find what you are looking for.
🤖 You can now chat with the docs using AI in the search.
✨ 35+ new guides and more on the way.

💌 Release notes to your inbox

You can subscribe to our changelog on Featurebase to receive release notes in your email inbox.

→ https://feedback.tokens.studio/changelog

Quality of Life improvements

• Added line numbers to the tokens JSON editor. (#3296)

• Added warning when deleting a token set, when the user is synced with the Studio App platform (#3302)

Bug Fixes

• Fixed importing text styles that reference variables in fontStyle, fontWeight, fontSize, lineHeight, letterSpacing, and paragraphSpacing. (#3299)

Bug Fixes

• Fixed unintended JSON file deletion when syncing single file tokens to GitLab (#3282)

• Resolved theme mapping issue where variables were not properly assigned when importing themes.

New Features

• Theme Creation: Users can now create themes when importing variables from Figma into the plugin. This enhancement improves organization and streamlines your design workflow. (#3260)

Bug Fixes

• .gitkeep File Issue: Fixed a bug where a .gitkeep file was created with every GitLab commit.(#3160)

• Token Format Correction: Tokens synced from the Tokens Studio Platform now default to the DTCG format. (#3259)

• Pro Features Activation: Resolved an issue preventing pro features from activating for users syncing via Tokens Studio with a valid API key.(#3277)

This release addresses an issue with a linear gradient and an issue with the Studio syncing provider.

• Increase Tokens Studio tokens set sync limit to 1000. #3262

• Fixes an issue where a user is unable to apply a linear gradient fill via a composition token. #3251