Chromatic review

Chromatic is a UI testing and review platform for teams that build interfaces from components. It captures interface states in real browsers so teams can compare changes and catch visual regressions in appearance, layout, fonts, or colors. It also checks for accessibility issues and tests interactions such as clicking, typing, hovering, and dragging.

The review side puts comments, change requests, and sign-off beside the components being reviewed. Teams can also publish a shared component library with searchable stories, tests, documentation, metadata, and examples. That makes Chromatic more than a screenshot comparison tool: it covers testing, review, and documentation in one workspace.

The pricing page lists a free plan and paid plans starting at $179 per month. The main cost variable is snapshot volume, so the fit depends partly on how much UI your team needs to capture and review.

Chromatic’s main advantage is that it brings several UI QA jobs together. Teams can check visual changes, accessibility, and interactions, then review the results with comments and approvals beside live components. That can reduce the handoffs between a test report, a pull request, and a separate component reference site.

Real-browser snapshots are useful when a team needs to check more than one appearance or viewport. The product description says teams can capture UI states, themes, and viewports, while Starter adds Safari, Firefox, and Edge testing to Chrome. Free includes Chrome testing, Git and CI integrations, and unlimited projects, users, and collaborators, according to the pricing details.

The free plan also offers 5,000 billed snapshots and a 25,000-turbosnaps equivalent. That gives a team room to start visual testing without paying up front. For teams that need more volume, Starter lists 35,000 billed snapshots per month, while Pro lists 85,000. A shared component library with stories, tests, docs, metadata, and examples adds value for teams that want one searchable home for UI guidance.

Snapshot volume is the pricing constraint to watch. Free includes 5,000 billed snapshots; Starter costs $179 per month for 35,000, and Pro costs $399 for 85,000. Starter lists extra snapshots at $0.008 each. If a team’s testing expands, those caps and overage costs can matter more than the starting price. The pricing details do not list an overage rate for Free or Pro.

The free plan is also limited to Chrome testing. Safari, Firefox, and Edge appear on Starter, so cross-browser coverage means moving to at least $179 per month. Pro adds a custom domain, but the pricing details do not describe other differences beyond what is included in Starter.

Annual billing prices are not published, and Enterprise pricing is not published. Enterprise includes SSO, custom Git integrations, priority support and an SLA, data retention, customizable snapshots and turbosnaps, and unlimited accessibility usage. The exact accessibility allowances on lower plans are not stated, which makes it harder to estimate whether those plans fit a team with heavier compliance needs.

Chromatic has a free plan, but its 5,000 billed snapshots make the cap worth checking against your expected usage. The pricing page lists Free at $0 per month, with Chrome testing, unlimited projects, users, and collaborators, plus Git and CI integrations.

Starter costs $179 per month and includes 35,000 billed snapshots, Safari, Firefox, and Edge testing. That is a $179 jump from Free. Extra Starter snapshots cost $0.008 each. Pro is $399 per month for 85,000 billed snapshots, a $220 increase over Starter; it adds a custom domain. Both paid plans list turbosnap equivalents, but the pricing page does not publish annual prices.

Enterprise pricing is not published. It includes customizable snapshots and turbosnaps, unlimited accessibility usage, SSO, custom Git integrations, priority support and an SLA, and data retention. If your snapshot use is near a plan cap, estimate overages before moving up: the listed per-snapshot add-on price applies to Starter, not Pro.

Switching to Chromatic means evaluating more than visual snapshots: the platform also covers accessibility and interaction checks, UI review, and component documentation. Before moving, inventory which of those jobs your team uses and how they fit into your current Git and CI workflow. The published materials don’t document a migration tool, data-export options, or whether review history and component documentation can be transferred, so confirm those details with Chromatic before committing.

Leaving may mean replacing several workflows, not just snapshot comparisons. Check how you’ll handle browser-based visual checks, reviewer sign-off, and the shared component library after a move. We weren’t given Reddit posts or comments about why users leave Chromatic, so we can’t verify user-reported switching complaints or sentiment. Treat portability and migration effort as questions to resolve with the vendor, rather than assuming your existing tests, comments, or docs will carry over.