Lazyweb vs Chromatic: Product References or UI Testing?
Choose Chromatic to test and review your own UI. Choose Lazyweb to study how other products handle a flow. Both can help a coding agent, but they provide different evidence: your components versus external product references.
What Chromatic covers
Chromatic documents workflows for Storybook, Vitest, Playwright and Cypress. Available visual, interaction and accessibility checks depend on the integration. Start with the guide matching the tests you already have. [1]
The MCP distinction that matters
Chromatic can publish a Storybook MCP server alongside a Storybook. The documented setup requires React and Storybook 10.3 or later. Private Storybooks require authentication.
Only documentation tools are available on the published MCP server. Development and testing tools require the local Storybook dev server. Do not assume that connecting to a hosted MCP gives an agent the ability to run the local tests. [2]
What to give the agent
For a new onboarding screen, first ask it to identify the components and states already available in your project. If you need outside examples, use Lazyweb to inspect the flow and capture dates. Then translate the idea into your components and tests.
Treat a reference as a reason to investigate a choice. Treat a test result as evidence about the checked states. Neither establishes that the change will convert better. [3] [2]
Price the test matrix
On October 7, 2026, Chromatic lists a free tier with 5,000 billed snapshots and Chrome testing. Starter is $179 per month with 35,000 billed snapshots, additional browser coverage and $0.008 per extra billed snapshot. Check the current plan before budgeting.
Our recommendation: estimate the states, viewports, browsers and builds you will actually run. Then compare that estimate with a pilot’s billed usage. Raw screenshot counts and billed snapshots need not be interchangeable. [4]
Run one change through review
Our recommendation: choose a representative component with loading, error and success states. Make one intentional visual change and one accidental break. Confirm the reviewer can find both, approve the intended change and keep the defect blocked.
If your main requirement is operating an open-source screenshot suite yourself, evaluate BackstopJS separately. If your main requirement is finding better onboarding ideas, begin with product research. We have not run a comparative reliability benchmark of these tools.
Continue
Source Notes
-
1. Chromatic documentation
Official documentation · chromatic.com · Supported testing workflows. -
Official documentation · chromatic.com · Published documentation tools, local-only testing tools and setup requirements.
-
3. Lazyweb
Lazyweb product page · lazyweb.com · Product growth toolkit built around real UI evidence, with free browsing and plan-dependent installed research reports. -
Official documentation · chromatic.com · Snapshot allowances, browser coverage and paid plans checked October 7, 2026.