assets.dev docs
Guides

Brands

How an extracted website becomes a versioned, renderable brand.

The brand editor for Vercel: name, verified domain, tagline, and default plus dark-variant logos, with a version history panel on the right showing v1 extracted and edits through v4 (current).
A brand document — name, domain, logos, and colors — with every save kept as a version.

Brand document

A brand is a single canonical document. It holds the design decisions a template needs to render on-brand: colors, typography, logo, and voice. You create it three ways — extract it from a URL, upload assets, or edit it by hand — and every path writes to the same shape.

Tokens

Templates never read raw brand fields. They consume derived tokens — resolved colors, typography, spacing, and semantic roles (primary, surface, accent). Extraction produces a first pass; your edits refine it. Because templates only see tokens, the same copy renders consistently across every template.

Versions

Each save creates a new brand version. A render captures the version it used, so past renders stay reproducible even after you keep editing the brand. You can list versions and restore an earlier one.

Re-extraction

When a site changes, re-run extraction against an existing brand. assets.dev computes a per-field diff so you choose what to accept before it becomes a new version — nothing is overwritten silently.

The relevant endpoints are grouped under Brands and Extractions in the API reference.

On this page