How the $extensions property lets teams innovate with design tokens without waiting for spec updates

Always Twisted

The W3C Design Tokens specification includes a $extensions property that provides a structured way to add custom metadata to design tokens without breaking compatibility. This freeform property allows teams to store tool-specific configuration, governance data, workflow annotations, and experimental features using reverse domain notation. While the core spec remains clean and portable, $extensions enables innovation without waiting for standardization. Tools like Penpot, Style Dictionary, and Tokens Studio support extensions, though adoption varies. Best practices include documenting extensions, keeping them optional, versioning changes, and treating them as a proving ground for potential future standardization.

Understanding $extensions in the Design Tokens Specification