Best Chromatic Alternatives for Open Source Projects
Compare open-source eligibility, integrations, review workflows, and maintenance when choosing a Chromatic alternative for your project.
Happo is the clearest first hosted alternative to evaluate if your project needs an explicitly stated open-source plan: its pricing page says free plans are available for open-source projects. Argos is another hosted candidate with documented Storybook and Playwright workflows. If you need full control, consider a self-managed visual-testing workflow, but budget for the infrastructure and review process your team will own. Check each provider’s current eligibility and terms; Happo’s policy does not establish the same terms for other services.
The best fit depends on what you test and how you want to review changes: Storybook components, application pages, or end-to-end states; CI or vendor-managed capture; and hosted approvals or project-maintained baselines. This guide compares the options supported by the available product documentation and flags details to verify before adopting one.
Start with your open-source eligibility question
Ask each vendor directly: Can I use this plan in my open-source project, and what does eligibility require? Happo’s pricing page explicitly says free plans are available for open-source projects. It describes a free plan with 5,000 snapshots per month in Chrome, visual and accessibility testing, and Storybook, Playwright, and Cypress integrations. These are current-page details, not a permanent promise; check the live plan limits, browser coverage, eligibility conditions, and activation process before relying on them. Happo pricing and open-source FAQ.
The research sources do not establish equivalent open-source eligibility for Argos, Chromatic, or the other named commercial products. Do not infer that a public free tier, if one exists, applies to public repositories. Confirm the terms for your exact project and usage.
Shortlist: which alternatives deserve evaluation?
1. Happo: start here when an open-source plan is the deciding factor
Happo is the strongest documented starting point for an open-source team because its own pricing page explicitly addresses open-source projects. The described free plan includes 5,000 monthly Chrome snapshots and lists Storybook, Playwright, and Cypress integrations, plus visual and accessibility testing. Confirm the current quota and eligibility before choosing it: plan details can change, and the page’s statement alone does not answer every project-specific condition.
Choose it for evaluation if you want a hosted workflow and your framework is covered. Check whether Chrome-only capture is sufficient, how the service handles your CI environment, what the shared review experience includes, and what happens when the project exceeds its monthly allowance.
2. Argos: evaluate for Storybook and Playwright workflows
Argos documents integrations for Playwright, Cypress, Storybook, WebdriverIO, and a CLI. Its Playwright quickstart describes installing an SDK, configuring a reporter, taking screenshots, and running tests in CI. That makes it a relevant hosted candidate for teams already using those tools. See the Argos Playwright quickstart and its product information.
Argos publishes a comparison with Chromatic, but comparative judgments there are vendor-authored. Treat them as Argos’s perspective and check the current Argos pricing page and documentation for plan limits, browser options, capture environment, and open-source eligibility. The available research does not verify an open-source discount or free plan for Argos.
3. Self-managed visual testing: consider it when control outweighs maintenance
A self-managed workflow may suit a project that wants control over screenshot capture and baselines. The tradeoff is ownership: the team needs to plan how tests run, where reference images live, how diffs are reviewed, how CI reports failures, and who maintains the environment as browsers and dependencies change.
Chromatic’s alternatives page says, from its vendor perspective, that other open-source libraries require teams to stand up and maintain visual-testing infrastructure before the first test. That statement should not be treated as an independent description of every tool. Use it as a prompt to estimate the actual work for the specific project and tool you are considering. Read the Chromatic alternatives page alongside the candidate project’s own setup guide.
4. Lost Pixel: relevant history, but check its sunset status
Lost Pixel’s repository describes visual regression support for Storybook, Ladle, Histoire, and application pages. Its current README says, “We are sunsetting the product and building what’s next.” That makes it risky to select as a new production dependency without checking the repository and hosted platform’s current status. The available information does not establish a shutdown date or a continuing maintenance commitment. See the Lost Pixel repository and verify its status before adoption.
Other names to investigate
Chromatic’s alternatives page lists Applitools, Percy, Sauce Labs Visual, LambdaTest SmartUI Visual, SmartBear VisualTest, and TestingBot Visual Testing. These are leads for further research, not recommendations here: the available sources do not independently establish their open-source eligibility, current pricing, or fit for your framework. Check each provider’s official documentation and terms against your project’s requirements.
Comparison table
| Option | Open-source eligibility evidence | Documented integrations or coverage | Review and ownership considerations | What to verify |
|---|---|---|---|---|
| Happo | Pricing page says free plans are available for open-source projects. | Storybook, Playwright, and Cypress; described free plan includes 5,000 snapshots/month in Chrome. | Hosted candidate; confirm the review flow and capture details for your project. | Eligibility process, current quota, browsers, overages, and CI behavior. |
| Argos | Not established by the available research; ask the vendor. | Storybook, Playwright, Cypress, WebdriverIO, and CLI are described in official product material. | Hosted workflow; Playwright quickstart documents SDK, reporter, screenshots, and CI steps. | Open-source terms, plan limits, pricing, capture environment, and browser coverage. |
| Self-managed workflow | Depends on the specific project and components selected. | Depends on the chosen framework and capture tooling. | More project control; the team owns setup, baseline storage, CI, review, and maintenance. | Ongoing maintainer effort, reproducibility, browser updates, and collaboration needs. |
| Lost Pixel | Repository is open source; hosted eligibility is not established here. | Repository describes Storybook, Ladle, Histoire, and application pages. | README announces sunset; do not assume ongoing product support. | Current repository activity, hosted status, migration path, and maintenance commitment. |
Choose by workflow, not by a generic ranking
- List the UI you need to cover. If the target is Storybook stories, confirm the integration tests those stories in the states your project cares about. If you need full application pages or end-to-end states, verify that the tool supports your browser automation workflow.
- Confirm the framework path. Check the exact integration for Storybook, Playwright, Cypress, or WebdriverIO in the vendor’s current docs. A listed integration does not guarantee that every reporter, runner, or CI setup is supported.
- Decide where capture runs. Determine whether screenshots are captured in your CI browser or in vendor-managed infrastructure. Differences in browser version, fonts, operating system, device scale, and rendering environment can change diffs. Confirm the provider’s current capture model and pin or record relevant versions where possible.
- Decide who owns review. If pull-request checks and shared approvals are essential, inspect the hosted review flow. If local baselines are adequate, estimate who will maintain image storage, diff presentation, CI status, and contributor guidance.
- Verify the project’s eligibility in writing. Ask what repository visibility, proof, usage, and approval conditions apply. Do not extend Happo’s stated policy to another vendor.
- Estimate real usage and total cost. Count screenshots per pull request, browser and viewport combinations, retries, and scheduled runs. Compare included volume, overages, and any multipliers in the plan you can actually use.
- Check maintenance risk. Review recent releases, issue activity, documented upgrade paths, and sunset notices. Lost Pixel’s README currently includes a sunset statement, so status verification is especially important there.
Pricing: compare dated plan details carefully
Published numbers are useful only with their date, quota unit, and plan conditions. Happo’s pricing page describes a free plan with 5,000 monthly Chrome snapshots and says free plans are available for open-source projects; check the live page for current terms.
An Argos-authored August 2026 pricing article reports Chromatic Starter at $179/month for 35,000 snapshots, plus $0.008 per additional snapshot, and Argos Pro at $100/month for 35,000 screenshots. The article says its pricing was checked in July 2026. These are vendor-published figures, not an independent price survey. Confirm current prices on each provider’s official pricing page before making a budget or publishing a procurement decision. See Argos’s 2026 pricing comparison.
For a self-managed setup, the subscription line item may be lower or absent, but account for CI compute, storage, engineering time, maintenance, and review friction. Estimate those costs for your own team rather than assuming they are zero.
ScreenshotNeo: an alternative to try first for page screenshots
ScreenshotNeo is a website screenshot API and MCP server for developers. It can complement a visual-testing setup when you need page screenshots through an API or want an AI agent to capture a page. It is not presented here as a drop-in replacement for Storybook visual regression or a shared approval workflow. For those needs, assess the tools above against your test and review requirements.
ScreenshotNeo accepts one GET request with a URL and returns a PNG, JPEG, WebP, or PDF. It removes known consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. It identifies bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits in response headers, and only clean shots are billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.
Here is the one-call cURL example. Replace the example target URL and API key with your own. See the ScreenshotNeo API documentation for parameters and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo has a free plan with 1,000 shots per month and no card required. Paid plans start at $5 for 3,000 shots, and every feature is on every plan. For a team that needs page captures in CI or through an MCP client, this offers a small way to evaluate that workflow alongside its visual-testing choice.
Sign up for 1,000 free screenshots a month, with no card.
Troubleshooting evaluation problems
| Problem | Likely cause | What to do |
|---|---|---|
| The project cannot use the free plan. | Open-source eligibility may have conditions, or may not be offered by that provider. | Ask the vendor about the exact repository, required proof, activation steps, and usage limits. Happo’s explicit policy does not apply to other providers. |
| Local and CI screenshots keep differing. | Different browser versions, fonts, operating systems, device scale, timing, or test data can affect rendering. | Compare environments and pin versions where possible. Wait for stable content and remove nondeterministic data or animations in the test setup. |
| A framework integration does not run in CI. | The project may be following a different runner, reporter, SDK, or configuration than the documented path. | Follow the provider’s current quickstart for that framework, verify package versions and CI configuration, and reduce the failure to one screenshot test. |
| Usage exceeds the estimate. | Each story, page, browser, viewport, retry, or scheduled run may add captures. | Count the actual capture matrix from a representative pull request and confirm how the provider counts snapshots and overages. |
| A tool looks suitable but its maintenance status is unclear. | Repository health and hosted product status can change. | Check current release and issue activity, roadmap or sunset notices, and whether you can export baselines before adopting it. This is especially relevant to Lost Pixel given its README notice. |
Reliability and performance considerations
Visual comparisons are only useful when the capture is repeatable. Keep test data stable, wait for the relevant content rather than relying on arbitrary short sleeps, and make fonts, viewport, browser, and device scale consistent across baseline and comparison runs. Decide how retries work: a retry can help with transient CI failures, but it can also conceal flaky rendering if the underlying cause is not fixed.
For hosted tools, include the provider’s CI integration and review service in the failure path: determine how a failed upload, delayed comparison, or unavailable review interface affects a pull request. For self-managed tools, the project owns capture capacity, artifact retention, and result presentation. The available sources do not provide comparable latency or reliability benchmarks for the listed services, so measure your own representative workflow before setting expectations.
Frequently asked questions
Is Happo free for every open-source project?
Its pricing page says free plans are available for open-source projects. Check the current eligibility requirements and plan limits for your repository.
Does a Storybook integration cover application end-to-end states?
Not automatically. Confirm that the integration and test runner cover the routes and interactive states your project needs.
Should a new project choose Lost Pixel?
Only after checking its current status. The repository README says the product is being sunset, and the available sources do not provide an exact shutdown date or ongoing maintenance commitment.
Can ScreenshotNeo replace Chromatic?
ScreenshotNeo is a screenshot API and MCP server. The facts available here do not establish it as a replacement for Chromatic’s Storybook visual-testing and review workflow. Consider it for page captures through an API or AI agent, and evaluate a visual-testing service for component regression and approvals.
Recommendation
Start with Happo if explicit open-source plan language is your main filter, and verify its current limits and eligibility. Evaluate Argos when its documented framework integrations match your test suite, while confirming its terms and pricing directly. Choose self-managed testing only when your team is ready to own capture, baselines, CI, and review. Treat Lost Pixel’s sunset notice as a maintenance risk, and verify its current status before adoption. For API or agent-driven website screenshots alongside that workflow, try ScreenshotNeo first: its free plan includes 1,000 shots each month with no card, and paid plans start at $5 for 3,000.
