Keys / Chromatic

CHROMATIC_PROJECT_TOKEN

The project token the Chromatic CLI uploads your Storybook builds with in CI.

Expires
the docs don't say
API
none documented; Manage > Configure only

Get it

Create one on www.chromatic.com/start. The steps aren't recorded yet.

Set it

CHROMATIC_PROJECT_TOKEN=...

The Chromatic CLI reads it when you don't pass --project-token. The GitHub Action takes it as projectToken. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. Open the project, then Manage > Configure, and reset the project token.
  2. The docs don't say whether the old token keeps working. Put the new one in every CI secret named CHROMATIC_PROJECT_TOKEN right away.
  3. In a monorepo, each subproject has its own token; replace only the one you reset.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16