DEV Community: Alexander

Export Figma variables to CSS custom properties using Style Dictionary

Alexander — Wed, 15 Apr 2026 15:00:36 +0000

TL;DR: We are going to take raw JSON from Figma variables and automatically turn it into working CSS custom properties using Style Dictionary.

The problem

Picture this. You are building a new component. You open Figma to check the design. You click on a button and see it uses a specific blue. You copy the hex code. You paste it into your CSS file.

Then the designer decides that blue is actually a bit too dark. They update it in Figma. But your code still has the old hex value. You do not find out until someone complains that the staging environment looks weird.

This happens all the time. Keeping code in sync with design is a massive headache. Tbh it is usually the worst part of building a UI. You just want to write logic and layout. You do not want to be a human copy machine for hex codes.

The good news is we can fix this. Figma lets you use variables for colours and spacing. We can take those variables as JSON and convert them directly into CSS. No more manual copying.

What you need

You only need a few things to follow along. Make sure you have Node.js installed on your machine. We are going to use a tool called Style Dictionary. It is an amazing open source package. It takes raw design data and formats it for any platform. We will focus on CSS today.

Open your terminal and create a new folder for this project.

mkdir figma-to-css
cd figma-to-css
npm init -y
npm install style-dictionary

Step 1: The raw data

First we need some data to work with. When you export variables from Figma they usually come out as a JSON file. The format often follows the W3C Design Tokens draft specification.

Let us create a fake export file to play with. Create a file called tokens.json in your project folder.

{
  "color": {
    "primary": {
      "value": "#0052CC",
      "type": "color"
    },
    "background": {
      "value": "#FFFFFF",
      "type": "color"
    },
    "text": {
      "value": "#172B4D",
      "type": "color"
    }
  },
  "spacing": {
    "small": {
      "value": "8px",
      "type": "dimension"
    },
    "medium": {
      "value": "16px",
      "type": "dimension"
    },
    "large": {
      "value": "24px",
      "type": "dimension"
    }
  }
}

This is a very simple example. Real Figma exports will be much bigger. But the structure is the same. You have categories like colour and spacing. Inside those you have your actual values.

Step 2: Setting up the build script

Now we need to tell Style Dictionary what to do with this JSON file. We need a configuration file. Create a new file called build.js in your folder.

We are going to write a short Node script. This script will read our JSON and output a nice CSS file.

const StyleDictionary = require('style-dictionary');

const config = {
  source: ['tokens.json'],
  platforms: {
    css: {
      transformGroup: 'css',
      buildPath: 'build/css/',
      files: [{
        destination: 'variables.css',
        format: 'css/variables'
      }]
    }
  }
};

const sd = StyleDictionary.extend(config);
sd.buildAllPlatforms();

Let me explain what is happening here. First we import the library. Then we define our configuration object.

The source array tells it where to find our JSON files. You can have multiple files here.

The platforms object is where the magic happens. We defined a CSS platform. The transformGroup tells Style Dictionary to use its built in rules for CSS. This handles things like converting names to kebab case.

The buildPath is where the final file will be saved. Finally the files array tells it exactly what to name the output file and what format to use.

Step 3: Running the build

We just need to run our script now. Go back to your terminal.

node build.js

You should see a message saying the build was successful. Check your project folder. You will see a new build folder. Inside that is a css folder. And inside that is your variables.css file.

The output

Let us look at what Style Dictionary actually generated. Open the variables.css file.

/**
 * Do not edit directly
 * Generated on Fri Oct 20 2023
 */

:root {
  --color-primary: #0052CC;
  --color-background: #FFFFFF;
  --color-text: #172B4D;
  --spacing-small: 8px;
  --spacing-medium: 16px;
  --spacing-large: 24px;
}

Look at that. It took our nested JSON and flattened it out. It added the CSS custom property syntax automatically. It even added a comment warning people not to edit the file directly.

You can now import this CSS file into your main project. When you use --color-primary in your styles it will perfectly match the Figma design.

Handling dark mode

You are probably thinking about dark mode now. Most modern apps need it. Figma handles this using variable modes. You might have a light mode and a dark mode in Figma.

When you export that data you usually get two different JSON files. Or you get one big file with different themes inside. Style Dictionary can handle this perfectly. You just create different source files for each theme. Then you output them to separate CSS files or scope them to specific CSS classes.

Here is a quick example of a dark mode JSON file. Let us call it tokens-dark.json.

{
  "color": {
    "background": {
      "value": "#172B4D",
      "type": "color"
    },
    "text": {
      "value": "#FFFFFF",
      "type": "color"
    }
  }
}

You can update your build script to output a variables-dark.css file too. Then you just load the right CSS based on the user preference. It makes theming incredibly easy to manage.

Automating the whole thing

So basically this script is great. But you still have to get the JSON out of Figma manually. You have to download it and put it in your folder. That still leaves room for human error. I actually got tired of doing this exact workflow. So I built a plugin called Design System Sync to completely automate it. It connects Figma directly to your GitHub or Bitbucket repo. When a designer changes a variable in Figma the plugin automatically generates a pull request with the updated CSS files. You can check it out at ds-sync.netlify.app or find it directly on the Figma Community. It uses the exact W3C formats we just talked about.

Try setting up Style Dictionary in your next project. It honestly changes how you think about CSS architecture.

Building a Figma to GitHub token pipeline that actually works

Alexander — Sat, 11 Apr 2026 18:24:01 +0000

The problem

Picture this. It is a Friday afternoon. Your team is getting ready for a big release. The design team decided earlier that week to tweak the primary brand colour. They changed it from a flat blue to a slightly more vibrant indigo. They updated Figma. They dropped a message in a crowded Slack channel.

And you completely missed it.

The release goes out with the old blue. The designers are frustrated. The developers are annoyed because they were not told properly. Honestly this happens all the time. Hardcoding colours and spacing values into CSS is a recipe for disaster.

We realised we needed a single source of truth. Figma had to be that source. But we also needed developers to review changes before they hit production. We needed a pipeline that turned Figma variables into actual code. And we needed it to happen via standard Pull Requests.

What we tried that didn't work

Our first attempt was pretty basic. We asked the designers to export a JSON file from Figma manually. Then they would zip it and send it to us on Slack. It was a disaster. People forgot to send the file. Versions got mixed up. We had tokens_final_v3_really_final.json floating around.

Next we tried writing a quick local script. A developer would run a command on their machine to fetch the tokens via the Figma REST API. This was slightly better. But it meant developers had to remember to pull the updates. The design team had no control over when their changes went live.

We needed a system where the design team could push changes directly to the codebase. But they had to do it safely. They needed to create a Pull Request automatically.

The architecture

We mapped out a new flow. It had to be simple for both sides.

First the designers update their variables in Figma. When they are happy they run a process to export those variables as standard W3C Design Tokens.

This process talks directly to the GitHub API. It creates a new branch. It commits the JSON file. Then it opens a Pull Request.

Finally a GitHub Action picks up that Pull Request. It runs Style Dictionary to transform the raw JSON into CSS variables. Developers just review the PR and click merge. Everyone stays in their comfort zone.

Implementation walkthrough

Let me show you exactly how we built the core parts of this pipeline.

First you need the tokens in a standard format. The W3C Design Tokens format is the best way to go. It looks something like this.

{
  "colors": {
    "primary": {
      "500": {
        "$value": "#4F46E5",
        "$type": "color"
      }
    },
    "background": {
      "$value": "{colors.primary.500}",
      "$type": "color"
    }
  }
}

The magic happens when you send this to GitHub. You can write a Node script to interact with the GitHub API. You need a personal access token with repo permissions.

Here is a simplified version of the script that creates a new file in a branch.

import { Octokit } from "@octokit/rest";

const octokit = new Octokit({ auth: process.env.GITHUB_TOKEN });

async function pushTokensToGitHub(tokensJson: string) {
  const owner = "your-org";
  const repo = "your-repo";
  const branchName = `design-tokens-update-${Date.now()}`;

  // Get the main branch reference
  const { data: refData } = await octokit.git.getRef({
    owner,
    repo,
    ref: "heads/main",
  });

  // Create a new branch
  await octokit.git.createRef({
    owner,
    repo,
    ref: `refs/heads/${branchName}`,
    sha: refData.object.sha,
  });

  // Commit the file
  await octokit.repos.createOrUpdateFileContents({
    owner,
    repo,
    path: "tokens/design-tokens.json",
    message: "Update design tokens from Figma",
    content: Buffer.from(tokensJson).toString("base64"),
    branch: branchName,
  });

  // Open a Pull Request
  await octokit.pulls.create({
    owner,
    repo,
    title: "🎨 Update Design Tokens",
    head: branchName,
    base: "main",
    body: "This PR was automatically generated to sync the latest design tokens.",
  });
}

Once the PR is created you need to turn that JSON into CSS. We use a tool called Style Dictionary for this. You set up a configuration file to tell it how to process the W3C format.

// build.js
const StyleDictionary = require('style-dictionary');

const myStyleDictionary = StyleDictionary.extend({
  source: ['tokens/**/*.json'],
  platforms: {
    css: {
      transformGroup: 'css',
      buildPath: 'build/css/',
      files: [{
        destination: 'variables.css',
        format: 'css/variables'
      }]
    }
  }
});

myStyleDictionary.buildAllPlatforms();

To automate this we added a GitHub Actions workflow. Every time a PR is opened or updated the action runs Style Dictionary and adds the compiled CSS to the PR.

name: Compile Design Tokens

on:
  pull_request:
    paths:
      - 'tokens/**.json'

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          ref: ${{ github.event.pull_request.head.ref }}

      - name: Setup Node
        uses: actions/setup-node@v3
        with:
          node-version: '18'

      - name: Install dependencies
        run: npm install

      - name: Build tokens
        run: node build.js

      - name: Commit compiled CSS
        run: |
          git config --global user.name 'github-actions[bot]'
          git config --global user.email 'github-actions[bot]@users.noreply.github.com'
          git add build/css/variables.css
          git commit -m "chore: compile tokens to CSS" || echo "No changes to commit"
          git push

Edge cases we hit

Building this wasn't totally smooth sailing. We ran into a few annoying edge cases.

The biggest issue was naming conventions. Designers love spaces and capital letters in their Figma variable names. Developers hate that. We had to write a custom transformer in Style Dictionary to clean up the names. It forces everything into kebab case. This prevents CSS errors.

Another tricky part was dealing with light and dark modes. Figma handles modes beautifully now. But exporting them requires you to split the modes into separate JSON files or nest them carefully. We ended up exporting a light.json and a dark.json. Then we configured Style Dictionary to output them into separate CSS files wrapped in media queries.

Math was also a problem. Sometimes designers use calculations for spacing variables. Standard JSON does not understand math formulas. We had to add a parser step to calculate those values before saving the JSON.

Results

Getting this pipeline running changed everything for us.

The friction between design and development dropped to zero. Designers now have total control over the visual foundation. When they want to update a colour they just hit export. A Pull Request pops up. The developers look at the diff to ensure nothing looks wildly broken. Then they merge it.

No more missing Slack messages. No more hunting down random hex codes in the codebase.

I actually spent the last few months turning this exact workflow into a proper Figma plugin. Setting up the GitHub API scripts and token transformers from scratch is a bit tedious. I wanted a tool that just did it out of the box.

I call it Design System Sync. It connects your Figma files directly to GitHub or Bitbucket. It exports your Figma variables into W3C Design Tokens or CSS Variables automatically. It even generates the Pull Requests with visual diffs so developers know exactly what changed.

You can check out the website at https://ds-sync.netlify.app?utm_source=devto&utm_medium=post&utm_campaign=bot. You can also grab it directly from the Figma Community if you want to give it a spin. It has a free tier that covers most small projects perfectly.

Building a solid bridge between design and code takes a bit of effort upfront. But the peace of mind is totally worth it. Let me know if you have tried building something similar for your team.