
figma-export
CLIExports Figma components (such as a full icon set) to SVG in bulk and styles like colors, text and shadows to Sass/SCSS variables or Style Dictionary tokens, keeping site icons and styles in sync with designs. Needs Node.js, a Figma token (FIGMA_TOKEN) and the matching output plugins.
Export tool for Figma.
You can easily and automatically export your figma components and styles and use them directly into your website.
:sparkles: In Short
Components
You can export your Figma Components as SVG and use them inside your website.
This is particularly useful when you have your own icon set and you want to keep your website icons up-to-date with your Figma file.
Styles
You can export your Figma Styles into different output like .sass format, .scss format, Style Dictionary tokens or you can create your own outputter.
If you want to keep the style of your Figma file in-sync with the
.cssof your website, this is a must-have.
:art: Colors (paints)
- Color
- Linear Gradient
:lollipop: Effects
Shadow and Blur effects cannot be combined together since they use two different CSS properties.
- Inner Shadow
- Drop Shadow
- Layer Blur
:pencil2: Text
- font-family
- font-weight
- font-size
- line-height
- letter-spacing
- font-style
- font-variant
- text-transform
- text-decoration
- text-align
:old_key: Personal Access Token
First of all you have to set the environment variable FIGMA_TOKEN.
To do so, you need a Personal Access Token. You can generate one from your Account Settings.
Inside the Account Settings click on Create a new personal access token and enter a description.
Copy the token, this is your only chance to do so!
export FIGMA_TOKEN=<personalAccessToken>
You can use dotenv or
exportthe variable using.bash_profile/.bashrcfile.
:test_tube: Just Try
Ensure you have Node.js installed in your system, the latest LTS is recommended. If you are not familiar with Node.js you can read their guide.
If you wanna try it just run following command and you will be able to download all components from https://www.figma.com/file/fzYhvQpqwhZDUImRz431Qo as .svg :sunglasses:
# export figma token
export FIGMA_TOKEN=<personalAccessToken>
# export figma components as svg
npx -p @figma-export/cli -p @figma-export/output-components-as-svg figma-export components fzYhvQpqwhZDUImRz431Qo -O @figma-export/output-components-as-svg
or you can export all styles into .scss
# export figma token
export FIGMA_TOKEN=<personalAccessToken>
# export figma styles as .scss variables
npx -p @figma-export/cli -p @figma-export/output-styles-as-sass figma-export styles fzYhvQpqwhZDUImRz431Qo -O @figma-export/output-styles-as-sass
:package: Packages
@figma-export/core
This package contains the core functionalities for figma-export. You can download and use it as a dependency of your project.
@figma-export/cli
This package allows you to consume all core functionalities from your terminal.
:book: Usage
Typically you'll prefer to use the cli. Here different ways to do the same:
Build Process
You can use figma-export as part of your build process.
npm install --save-dev @figma-export/cli @figma-export/output-components-as-svg @figma-export/output-styles-as-sass
# or using `yarn`
yarn add @figma-export/cli @figma-export/output-components-as-svg @figma-export/output-styles-as-sass --dev
Now you can create a script command inside your package.json.
Following an example:
{
"scripts": {
+ "figma:export-components": "figma-export components fzYhvQpqwhZDUImRz431Qo -O @figma-export/output-components-as-svg",
+ "figma:export-styles": "figma-export styles fzYhvQpqwhZDUImRz431Qo -O @figma-export/output-styles-as-sass",
}
}
Use it on the fly
Alternatively you can use npx to use it on the fly:
npx @figma-export/cli --help
Global Setup
You can also install it as a global dependency:
npm install -g @figma-export/cli
# or using `yarn`
yarn add @figma-export/cli --global
figma-export --help
Advanced
Last but not least, you can create a configuration file and use a single command to rule them all :ring:
Let's create the file .figmaexportrc.js and paste the following:
// @ts-check
import outputComponentsAsSvg from '@figma-export/output-components-as-svg'
import outputStylesAsSass from '@figma-export/output-styles-as-sass'
import transformSvgWithSvgo from '@figma-export/transform-svg-with-svgo'
/** @type { import('@figma-export/types').StylesCommandOptions } */
const styleOptions = {
fileId: 'fzYhvQpqwhZDUImRz431Qo',
// version: 'xxx123456', // optional - file's version history is only supported on paid Figma plans
// ids: ['138:52'], // optional - Export only specified node IDs (the `onlyFromPages` option is always ignored when set)
// onlyFromPages: ['icons'], // optional - Figma page names or IDs (all pages when not specified)
outputters: [
outputStylesAsSass({
output: './output'
})
]
}
/** @type { import('@figma-export/types').ComponentsCommandOptions } */
const componentOptions = {
fileId: 'fzYhvQpqwhZDUImRz431Qo',
// version: 'xxx123456', // optional - file's version history is only supported on paid Figma plans
// ids: ['54:22'], // optional - Export only specified node IDs (the `onlyFromPages` option is always ignored when set)
onlyFromPages: ['icons'],
transformers: [
transformSvgWithSvgo({
plugins: [
{
name: 'preset-default',
params: {
overrides: {
removeViewBox: false,
}
}
},
{
name: 'removeDimensions'
}
]
})
],
outputters: [
outputComponentsAsSvg({
output: './output'
})
]
}
/** @type { import('@figma-export/types').FigmaExportRC } */
export default {
commands: [
['styles', styleOptions],
['components', componentOptions]
]
}
:information_source: Take a look at .figmaexportrc.example.js for more details.
now you can install the @figma-export dependencies that you need
npm install --save-dev @figma-export/cli @figma-export/output-styles-as-sass @figma-export/transform-svg-with-svgo @figma-export/output-components-as-svg @figma-export/types
and update the package.json.
{
"scripts": {
+ "figma:export": "figma-export use-config"
}
}
If needed you can also provide a different configuration file.
{
"scripts": {
+ "figma:export": "figma-export use-config .figmaexportrc.production.js"
}
}
TypeScript
If you prefer, you can create a .figmaexportrc.ts and use TypeScript instead.
For doing so, you just need to install a few new dependencies in your project.
npm install --save-dev typescript tsx @types/node
and slightly change your package.json
{
"scripts": {
+ "figma:export": "tsx ./node_modules/@figma-export/cli/bin/run use-config .figmaexportrc.ts"
}
}
Take a look at .figmaexportrc.example.ts for more details.
Pure ESM package
This package is pure ESM. It cannot be require()'d from CommonJS.
If your package.json does not contain the "type": "module" field then you'll need to rename your .figmaexportrc.js configuration file:
- .figmaexportrc.js
+ .figmaexportrc.mjs
adjust the command you run:
figma-export use-config .figmaexportrc.mjs
and start using import foo from 'foo' instead of const foo = require('foo') to import the packages inside the .figmaexportrc.mjs. You can take a look at .figmaexportrc.example.js as an example.
:books: More Packages
For the list of all official packages or if you want to create your own transformer or outputter you can continue reading CLI Documentation.
Ähnliche Ressourcen

Sync Figma Token
SkillSyncs design tokens between code and Figma variables: normalizes both sides, reports drift by value, alias, mode and scope in a dry run, then stops for explicit approval before writing, archives rather than deletes, and saves JSON reports. Requires the Figma MCP server; invoked manually.
firebenders/sync-figma-token-skill27
designlang
CLIReads any website's design system in a headless browser and exports DTCG design tokens, Tailwind config, Figma variables and a brand guide in one command, scoring contrast and cross-page consistency. Also an MCP server or Claude Code plugin. Needs Node.js and Chromium or Chrome.
Manavarya09/design-extract4.2k
Figma Code Connect
CLIFigma's official CLI that links Figma design-system components to real components in your code, so Dev Mode and the Figma MCP show production snippets instead of generated examples. Needs Node.js 18+, a Figma Organization or Enterprise plan, a full Design or Dev Mode seat and an access token.
figma/code-connect1.6k
figma-use
CLIRead and write Figma from the terminal with commands or JSX: create frames and components, insert Iconify icons, set layout, and export nodes as JSX or Storybook; can also run as an MCP server. Needs Figma Desktop; version 126+ requires daemon --pipe mode.
dannote/figma-use611
Figma (Codex)
PluginFigma's Codex plugin in OpenAI's official marketplace: implements UI from designs, generates Code Connect mappings, and creates or updates pages, component libraries, FigJam diagrams and slides in Figma. Needs a connected Figma account.
openai/plugins7.5k
Talk to Figma MCP
MCPUses a Figma plugin and a local WebSocket server so agents can read and directly edit designs: create frames and text, adjust auto layout and styles, and replace copy in bulk. Requires Bun; now maintained by Grab.
grab/cursor-talk-to-figma-mcp7.1k