---
title: Apply a brand change everywhere
description: Bind properties to tokens once, then re-skin every screen from one dropdown or a three-line brand file. Step by step.
section: solutions
order: 7
featured: false
related: design-system/modes-and-brands, solutions/design-system-leads, ai/design-tutorials
---

# Apply a brand change everywhere

How do I change the brand across every screen at once? Bind your properties to tokens, and write the brand as a small file. A brand file is often three or four lines, and switching to it re-skins every bound element. The work is in the binding: do it once, and the switch is free.

<DocFigure src="/docs/images/solutions/brand-changes-scene.webp" srcMobile="/docs/images/solutions/brand-changes-scene-390.webp" stage="panel" alt="A storefront re-skinning when the brand changes" caption="One switch, every bound screen." />

## How do I run a rebrand?

Three steps. The first one is the only real work.

<DocStep n="1" title="Bind properties to roles.">

Reach for semantic roles like color.surface, spacing.md and radius.lg, because they are mode-aware. The right toolbar binds a property to a token with a click, and an agent uses tokens on its own when a system is active. Type and shadows bind too, as composites like typography.h1 and shadow.md.

</DocStep>

<DocStep n="2" title="Write the brand as an overlay.">

Brands are sibling .ds files beside default.ds that hold only their deltas: a seed, maybe a font family, a few overrides. Or ask: "add an alternate brand called sunset with a warm orange primary."

</DocStep>

<DocStep n="3" title="Switch and watch.">

The Design system section sits at the top of the right toolbar, with a dropdown per mode axis and the brand picker. Hover to preview, click to commit. With nothing selected you set the canvas; with a selection, the element.

</DocStep>

```text title="Styles/acme.ds"
primary:     boldness(color(#FF6A00))
font.family: Inter
color.primary { $default: primary.firm, dark: primary.subtle }
```

## Can one area stay on the old brand?

Yes. The cascade runs per element, then per canvas, then per folder, so one screen can hold while the rest moves, and a Marketing folder can carry its own overrides. See [Modes and brands](/docs/design-system/modes-and-brands).

<DocFigure src="/docs/images/solutions/brand-changes-system.webp" srcMobile="/docs/images/solutions/brand-changes-system-390.webp" stage="panel" alt="The same checkout twice: most screens on the new orange brand, the Marketing folder held on the old blue one" caption="The cascade runs per element, canvas and folder, so one area can hold while the rest moves." />

## Common questions

### What will not follow the switch?

A raw hex stays that hex. Select the element and tell the agent to bind the fill to the closest token, then switch again.

### Can a value differ per mode?

Yes, through a semantic. Primitives stay the same in every mode on purpose.

## Where next?

- Theming and multi-brand: [Modes and brands](/docs/design-system/modes-and-brands).
- Every token type: [Tokens](/docs/design-system/tokens).
- Start from the beginning: [Design system overview](/docs/design-system/overview).
- Follow a re-skin: [Design tutorials](/docs/ai/design-tutorials).
- Keep agents on the system: [Build feature UI](/docs/solutions/build-feature-ui).
