Context at Meta

Meta operates many design systems rather than a single consolidated one. Each major app has its own, and further systems exist for areas such as VR experiences and cross-Meta experiences like the Accounts Center. The stated goal is not consolidation but sustainable support for the 20-plus systems in use, which is what makes design systems at scale a technical problem.

  • Facebook Design System (FDS)
  • Instagram Design System (IGDS)
  • Messenger Design System (MDS)
  • WhatsApp Design System
  • Design systems for VR and cross-Meta experiences
  • More than 20 design systems in total

Source: Design Systems @ Scale | At Scale Conferences

What the platform covers

DSP is described as a foundational layer for any design system to represent its foundational elements via design tokens. It sits within a wider effort of three major areas addressing the cost of supporting many systems. The other two areas are theming infrastructure, which makes shipping UI updates faster and easier, and a library of "chameleon components" that support many design systems.

  • Design Systems Platform (DSP) as the token layer
  • Theming infrastructure for faster UI updates
  • Chameleon components supporting multiple design systems

Source: Design Systems @ Scale | At Scale Conferences

How design tokens work

The article sets out the token workflow in three steps. Tokens are first defined, then synced into both code and design, and finally used in product code. This is the mechanism by which foundational design decisions are carried into implementation.

Step 1
define tokens
Step 2
sync tokens into code and design
Step 3
use tokens in product code

Source: Design Systems @ Scale | At Scale Conferences

Components of a design system

Each design system at Meta is described as being made up of three parts. Foundational elements cover colours, fonts, spacing and more. UI components are the reusable building blocks of an app, such as Text, Button and Profile Photo, while design principles are instructional guidelines and UX patterns for applying elements and components consistently.

Foundational elements
colours, fonts, spacing
UI components
Text, Button, Profile Photo
Design principles
guidelines and UX patterns

Source: Design Systems @ Scale | At Scale Conferences

Stated benefits

The article gives three reasons design systems matter at this scale. Branding and consistency come from baking brand elements into product foundations, giving scalable expressions such as typographic scales and colour palettes. Quality and accessibility are raised through built-in considerations for accessibility, usability and performance, solved once and reused. Speed comes from collecting a design system in one place, helping manage design and technical debt and allowing design-language updates to be tested and released at scale.

  • Branding and consistency across apps
  • Accessibility, usability and performance built in
  • Faster testing and release of design-language updates

Source: Design Systems @ Scale | At Scale Conferences

Where it is documented

DSP is not offered as a public product in the source material; it is an internal Meta platform described in an article on the @Scale Conferences site. The piece is published under the site's Articles type for the year 2023 and is attributed to the @Scale team. Readers seeking detail on how DSP works can consult the "Design Systems @ Scale" article, which covers the platform, theming and chameleon components including their "Variants" concept.

  • Published as an @Scale article, 2023
  • Attributed to the @Scale team
  • Covers DSP, theming and chameleon component variants

Source: Design Systems @ Scale | At Scale Conferences

Sources

  1. Design Systems @ Scale | At Scale Conferences https://atscaleconference.com/design-systems-scale/ Verified 31 Oct 2026

Last verified 16 Sep 2026. This entry is compiled from the public web pages listed above. Nothing here is stated that those pages do not, and each of them was read on the date shown.