Skip to main content

Frequently Asked Questions

General​

What is GitFig?​

GitFig is a Figma plugin that syncs design tokens between Figma and GitHub, enabling version control for your design system.

Is GitFig free?​

GitFig's core workflow is free: bi-directional sync, branches, pull requests, the commit workflow, and all token formats.

Variable modes (syncing every mode of your collections, light/dark or multi-brand, instead of the first mode only) is also free for everyone during the v1.3 preview. It becomes part of GitFig Pro, a paid plan, in a future release. Pricing will be announced before that happens, and you can opt in to a launch notice from inside the plugin.

Does GitFig support variable modes?​

Yes, and it is free during the v1.3 preview. Mode-keyed token files use the mode name as the root key:

{
  "light": { "color": { "bg": { "$value": "#ffffff", "$type": "color" } } },
  "dark":  { "color": { "bg": { "$value": "#111111", "$type": "color" } } }
}

Set a mapping's Variable Modes option to "All modes" to sync every mode of that collection, both directions. Aliases are written as {Collection.path.to.token} references. Note that the number of modes per collection is limited by your Figma plan (the Figma Starter plan allows one mode per collection).

Does GitFig store my data?​

GitFig stores:

  • Your GitHub user ID and access token (used server-side to authenticate API requests)
  • Repository connection info and file mappings
  • Sync history (purged after 90 days)
  • Pending commit snapshots between Commit and Push (deleted after push)
  • If you opt in: a contact email, used for the GitFig Pro launch notice during the preview, or for billing support once you are a Pro subscriber

Pull and push transfer token data directly between the plugin and GitHub.

Features​

What happened to Make Bridge mode?​

Make Bridge mode was removed in v1.2.0 to focus on the core workflow. The functionality has been archived and may return in a future release based on user feedback.

If you were using Make Bridge to sync Figma Make repositories, we recommend connecting directly to your target repository.

What token formats are supported?​

  • W3C Design Tokens (recommended)
  • Style Dictionary
  • Tokens Studio
  • Custom JSON

Does GitFig preserve $extensions in my token files?​

Yes. When pushing, GitFig merges against the file currently in your repository: $extensions, $deprecated, and any other $-prefixed metadata your build pipeline keeps on tokens or groups survive the push untouched. GitFig only owns $value, $type, and token-level $description (those always reflect Figma). Tokens deleted in Figma are removed from the file along with their metadata.

Can I undo a Pull?​

Yes. Every pull is one step in Figma's undo history. The summary toast offers Undo for a few seconds, which reverts the pull and restores your change list as long as you have not edited anything since; Figma's own Edit > Undo does the same.

Why did a change I left unchecked disappear after pushing?​

It does not. Unchecked changes are excluded from the commit and stay listed after the push, so you can commit them later or revert them in Figma.

Can I sync text styles and effect styles?​

Yes. Map a JSON file to the Text styles or Effect styles target in Mapping. Pull creates or updates the styles by name, and Push writes them back.

Does GitFig support multiple themes?​

Two ways:

  • Variable modes (free during the preview): sync all modes of a collection in one mode-keyed file. This is the recommended approach for light/dark and multi-brand systems.
  • Git branches (free): keep one theme per branch. See the Multi-Brand Themes tutorial; this workflow remains fully supported.

The plugin text is too small (or too large) on my monitor​

Zoom the plugin UI with Ctrl/Cmd +, Ctrl/Cmd −, and Ctrl/Cmd 0 (reset), or hold Ctrl/Cmd and scroll. The current level shows as "Zoom: 100%" in the footer, and the setting is remembered per Figma account, so you can keep different comfort levels on a high-resolution monitor and a laptop. You can also drag the plugin window larger from its right or bottom edge.

Technical​

Why Device Flow instead of regular OAuth?​

Figma plugins run in a sandboxed iframe that can't handle OAuth redirects. Device Flow works around this limitation.

Is my GitHub token secure?​

Your token is stored in Figma's encrypted clientStorage on your machine. It is also sent to GitFig's API server with each request (as the authentication credential) and stored there to operate the service. Traffic is encrypted in transit (HTTPS). Sign out at any time to clear the token from the plugin, and revoke GitFig's access from your GitHub settings to invalidate it everywhere.

Can multiple people use GitFig on the same file?​

Yes, but coordinate to avoid conflicts. The last push wins for any given token.

Compatibility​

Does GitFig work with Figma Web?​

Yes, GitFig works in both Figma Desktop and Web.

What GitHub permissions are required?​

  • repo - Read/write repository access
  • user:email - Your email for commits

Does it work with GitHub Enterprise?​

Currently GitFig only supports github.com. Enterprise support may come in future updates.

Billing​

Is there anything to pay for right now?​

No. Everything in GitFig v1.3, including variable modes sync, is free during the preview. GitFig Pro, the paid plan that variable modes sync will become part of, launches in a future release. Pricing and the free-plan behavior for existing mode-keyed files will be announced before anything changes, and your files and variables are never affected by plan changes.

How will I know when GitFig Pro launches?​

The plugin offers a one-time, optional email opt-in for a launch heads-up. It is used for that one notice and nothing else. You can also follow the changelog.