Design Tokens (DTCG) format (.tokens)

The Design Tokens (DTCG) format reads W3C Design Tokens Community Group token files (.tokens / .tokens.json), the JSON interchange format used by Style Dictionary, Tokens Studio, and similar tooling.

Token values are typed design data (colors, dimensions, font families, aliases), not natural language, so the format extracts only the human-readable $description documentation on tokens and groups as translatable content; every token $value, $type, $extensions, and the surrounding structure passes through untouched. Detection claims the unique .tokens extension and sniffs DTCG content ($value + $type); .tokens.json files resolve to the JSON format by extension unless -f designtokens is given. Round-trip is byte-faithful, inherited from the JSON reader/writer.

IDdesigntokens

SourceBuilt-in

Extensions.tokens

CapabilitiesRead + Write

Parameters

Parameter	Type	Default	Description
extractDescriptions	boolean	true	Pakk ut $description-verdier (lesbar token- og gruppedokumentasjon) som oversettbare blokker. Dette er det eneste naturlige språkfeltet i DTCG; $value er alltid en typet designverdi (farge, dimensjon, skriftnavn, …) og pakkes aldri ut. Deaktiver for å lese filen som en fullstendig ikke-oversettbar struktur.

Configure it live

Configuration

Loading form…

Configuration output

vs defaults no changes

apiVersion: neokapi/v1
kind: DesigntokensFormatConfig
metadata:
  name: designtokens
spec:
  # (default configuration)

Examples

Disable description extraction

Treat the file as fully non-translatable.

extractDescriptions: false

Processing notes

• Only $description is extracted; token values and structure are non-translatable passthrough.

• A token file with no $description yields zero translatable blocks, which is expected for machine-generated token sets.

← Back to the Format Reference