Responsive Bands
Width bands, per-band values, and how every prop decides what varies per device.
A band is a range of page widths — not a device. Each band holds its own values for the parts of your page that should change per screen size, and the published site picks the band that matches each visitor's window. This page explains bands, which properties can vary per band, and how band values combine with states.
Bands are width ranges
The header's segmented control shows the bands. Every document starts with three:
- Desktop — the base. Everything you author starts here, and desktop values always exist.
- Tablet — applies at and below its width (1023 by default).
- Mobile — applies at and below its width (767 by default).
"At or below" is the whole rule: a visitor at 900 pixels wide gets the tablet band, because 900 ≤ 1023 but 900 > 767. Above the widest defined band, everything is desktop.
The three defaults are permanent — you can rename them or change their widths, but never delete them. Add your own bands with the + button: name it, give it a width, and it joins the switcher. Deleting a custom band strips its overrides from every scene and object in one undo step (with a confirmation when overrides exist).

Bands are not devices
The devices menu (beside the band switcher) is a convenience, not a storage place: picking "iPhone 14" just resizes the preview frame to that device's width, which activates whatever band that width falls into. You can define your own devices too — they persist with your editor preferences, never with the document. The preview frame itself can clamp anywhere from 200 to 7680 pixels wide.
What varies per band: three homes for every value
Every value on every object lives in exactly one of three homes:
- Root — never varies. Identity and authoring detail: an object's name, the shape type you picked, which modifiers sit on its stack. Editing these writes the same value for every device and every state.
- Band — varies per width. These are the values with a responsive story: font sizes, a light's shadow settings, a speaker's spatial spread, camera clamps. When you edit one at a non-desktop band, that band remembers the new value; the base keeps its own.
- State — varies per interaction (see States). A state's content can additionally be refined per band — more below.
You never configure this mapping — each property ships knowing its home. The editor just follows it: edit a value while the tablet band is active, and if that property varies per band, the tablet band stores the change. Edit the same property on desktop, and you are editing the base.
Overrides are complete values
A band's value for a property is a complete value, not a patch. If a property holds a list — a modifier's settings, an object's transform — its band override replaces the whole list for that band; it never merges item-by-item with the desktop list. In practice you never see the machinery: you edit at a band, that band owns the value, other bands keep theirs.
Refine a state per band
States and bands compose: a state authored at desktop can carry a different value at mobile. Switch to the mobile band, select the object, switch to the state, and edit — the mobile refinement is stored for that state in that band only. A hover state that scales a card 1.2× on desktop can scale 1.05× on mobile, with no extra states to author.
Editing at a band
Switch bands with the header control (or pick a device, or drag the frame edge across a band boundary). The stage resizes to the band's range and every panel edit routes to that band. Switch back to desktop to see — and edit — the base values.
Next
States
Interaction states that restyle objects and page elements when visitors hover, click, or scroll.
Materials (Layers)
How materials are stacks of layers that blend top-down, the thirteen layer kinds, and what changes rebuild versus apply live.
Last updated on