Skip to content

Features

Here’s the big picture of what Figmage does, with links to the pages that cover each area in depth.

Run figmage sync to read your published Figma library and write design token files to disk. You declare what you want once in figmage.config.js; Figmage fetches the latest values and generates ts, js, json, or svg output.

See: Quickstart · Configuration

Extract the building blocks straight from your Figma styles:

  • Colors from color styles.
  • Typography from text styles.
  • Shadows from drop-shadow effect styles.

See: Token Types → Style-based · Styles & Variables

Generate tokens from Figma components, not just styles:

  • Property tokens — measure component width, height, or corner radius to produce spacing, sizing, and radii scales.
  • Image tokens — export components as individual vectors, a single SVG sprite, or raster (png/jpg) assets.

See: Token Types → Source-based · Components

Control how tokens are generated with global defaults and per-token overrides — color formats (hex, rgb, hsl, …), unit formats (px, rem), name casing, file types, and output directories.

See: Configuration → Transform

Refresh only part of your design system with --only and --skip, so CI jobs can re-export a single token group on demand.

See: CLI → Filtering

Bundle icons into a single SVG sprite for performance — either from Figma components (the imageSprite token type) or from a folder of local SVG files via figmage spritesheet.

See: CLI → spritesheet

Generate TypeScript output (including a typed list of sprite icon IDs) so token names and values are autocompleted and checked at build time.

See: Configuration