Chromatic · Rate Limits

Chromatic Rate Limits

Chromatic does not publish fixed numeric per-second or per-minute rate limits for its public GraphQL API. In practice the effective limit that matters is the monthly snapshot allowance of your plan, and the CLI's own concurrency: builds run in parallel up to your plan's parallelism and the CLI polls build status over GraphQL until completion. When a build cannot be fully snapshotted within your quota it is marked isLimited (representative stories only) rather than throttled with an error. Numeric GraphQL request-rate limits are not documented as of the review date.

Chromatic Rate Limits is the machine-readable rate-limit profile for Chromatic on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, snapshots, and concurrent builds.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Visual Testing, Storybook, GraphQL, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Visual TestingStorybookGraphQLRate LimitingQuotas

Limits

GraphQL API Request Rate token
requests
not published
No fixed numeric request-rate limit is documented for the public GraphQL API.
Monthly Snapshot Allowance account
snapshots
per plan (Free 5,000; Starter 35,000; Pro 85,000; Enterprise unlimited)
The dominant usage governor. Builds exceeding quota are marked isLimited.
Build Parallelism account
concurrent builds
per plan
Snapshots run in parallel across cloud browsers; plans include unlimited parallel test runs.

Policies

Snapshot Quota Limiting
When snapshot quota is insufficient, a build is limited to representative stories (isLimited=true) instead of failing.
TurboSnap
Change detection skips snapshotting unchanged stories, reducing snapshot usage by up to roughly 80 percent.
Backoff Strategy
The Chromatic CLI retries GraphQL calls with backoff and polls build status until the build reaches a terminal status.

Sources