Short answer: if your team already uses Playwright, start with its built-in screenshot assertions. If you need shared visual review, hosted baselines, and a collaborative workflow, evaluate a hosted service against your actual test runner and coverage needs. Not using Storybook does not automatically rule out Chromatic: its comparison guide lists Playwright and Cypress integrations, but verify that the current integration supports your workflow.
What changes when you do not use Storybook?
Visual regression testing compares a rendered page or component with an approved reference image and flags visual differences. The main choice is not simply “Chromatic or another tool.” It is whether your team wants to generate screenshots, keep baselines, and review changes in its existing test and CI setup, or use a hosted service to provide more of that shared workflow.
As an Amazon Associate I earn from qualifying purchases.
- Existing browser tests: capture the screens your tests already visit and keep reference images in the repository.
- Hosted workflow: use a service that fits your runner and offers hosted capture, baseline history, or review tools.
- Storybook-based workflow: add Storybook stories as the units of visual testing. This is relevant only if adopting Storybook is an option.
Compare tools by capture and execution, whether they cover components, routes, or both, where baselines live, who can review diffs, how checks integrate with pull requests, how much rendering noise needs human review, and the combined cost of subscriptions, CI, storage, and maintenance.
Can you use Chromatic without Storybook?
Chromatic’s own comparison guide lists integrations with Storybook, Playwright, and Cypress. So a team not using Storybook should not exclude Chromatic solely for that reason. Confirm the current integration documentation and test the workflow against your own cases before choosing it; the vendor’s comparison page is a product claim, not an independent evaluation.
Chromatic is most directly associated with a collaborative hosted visual-testing workflow. Whether its non-Storybook integrations provide the specific coverage, review process, and CI behavior you need is a practical evaluation question, not something to assume from the existence of an integration.
Option 1: Add screenshot assertions to Playwright Test
If Playwright is already your browser-test runner, its screenshot assertions are the most direct way to begin without adopting another platform. The documented API is await expect(page).toHaveScreenshot(). The first run creates reference screenshots; later runs compare new screenshots with those references. Playwright’s guide explains the assertion and snapshot workflow at Playwright: Visual comparisons.
Minimal example
In a Playwright Test test file, navigate to the page or state you want to check, then assert its screenshot:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
import { test, expect } from '@playwright/test';
test('pricing page visual baseline', async ({ page }) => {
await page.goto('https://example.com/pricing');
await expect(page).toHaveScreenshot();
});Use your real route and test setup. On the initial run, Playwright creates a baseline snapshot. Review that image and commit the intended reference to version control. On later runs, a mismatch indicates that the rendered image differs from the stored baseline; inspect the diff, decide whether the change is expected, and update the snapshot only when the new rendering is approved.
What your team must own
- Baseline review: snapshot files belong in version control and need review like other test artifacts. Agree on who approves visual changes and who updates references.
- Consistent rendering: Playwright warns that screenshots can vary by operating system, browser version, settings, hardware, power source, and headless mode. Generate and compare baselines in a consistent environment, ideally the same CI environment and browser configuration.
- Noise triage: investigate whether a diff is a real UI change or a rendering/environment difference before accepting it. Dynamic content and unstable page states can make comparisons harder to interpret.
- Collaboration: repository snapshots provide a reviewable baseline, but the team is responsible for providing the review process and access to diffs. Do not assume this is equivalent to a hosted service’s shared workflow.
When this is the better fit
Use Playwright assertions when the team already runs Playwright, wants visual checks in its existing tests, and is comfortable maintaining snapshots and review practices in its repository. If you need hosted capture or a shared review workflow, compare hosted services rather than treating Playwright alone as a complete substitute.
Option 2: Compare hosted services by how they capture and review
Hosted products are not interchangeable. Argos’s vendor-authored comparison of visual-testing tools, published July 16, 2026, describes different capture approaches: Percy uploads DOM for cloud rendering, Chromatic renders and captures in its cloud, and Argos captures screenshots in the test browser before uploading them for diffing. Treat these as vendor descriptions to verify against each provider’s current documentation, not as an independent ranking.
| Approach described by Argos | What to evaluate |
|---|---|
| Percy: DOM uploaded for cloud rendering | Whether cloud rendering covers your routes and states reliably, and how its review and CI workflow fits your team. |
| Chromatic: rendering and capture in its cloud | Whether its Playwright or Cypress integration covers your non-Storybook tests and the collaboration workflow you need. |
| Argos: capture in the test browser, then upload for diffing | Whether keeping capture in your test browser better fits your test environment, and what hosted review and CI features are available. |
Before committing, run a representative set of component states and end-to-end routes, including a known expected visual change. Check how each candidate stores and updates baselines, exposes diffs to reviewers, reports results on branches or pull requests, handles rendering noise, and charges for the usage your team expects. Those checks are more useful than assuming a product’s positioning applies to every test suite.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Dated price figures are not current quotes
Argos’s July 16, 2026 comparison reports Argos Pro at $100/month, Chromatic at $179/month for a stated 35,000-snapshot tier, and a Percy entry tier at $599/month. These are figures attributed to Argos, not independently verified current official prices. Confirm current pricing, allowances, billing terms, and availability directly with each provider before budgeting.
Option 3: Adopt Storybook plus Chromatic only if the workflow fits
If the team is open to adopting Storybook, Storybook’s official visual-testing guide describes a workflow in which the Chromatic addon turns stories into visual tests, captures them in the cloud, and supports reviewing and accepting changed baselines in the addon and CI, including pull-request checks. See Storybook visual testing.
Rank #4
This can make sense when component stories are a useful unit of review and your team wants that component-workbench workflow. It is not the answer for a team firmly avoiding Storybook. Storybook also documents importing stories into Playwright or Cypress end-to-end tests in its general testing guide, which is a separate way to reuse stories rather than a reason to assume Storybook is required for all visual assertions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose based on your test model
- Already on Playwright, willing to manage snapshots: start with
toHaveScreenshot()and establish consistent baseline generation, review, and update practices. - Need shared hosted review, but do not use Storybook: shortlist services that document support for your runner. Include Chromatic in the evaluation rather than ruling it out automatically, and verify the exact integration.
- Open to Storybook and component-level review: assess Storybook plus Chromatic as a different workflow, not as a drop-in equivalent to existing route-based tests.
- Need screenshots as files or a capture API rather than test baselines: ScreenshotNeo is the alternative to try first: it returns clean PNG, JPEG, WebP, or PDF captures from one GET request, removes supported consent banners and overlays before capture, and bills only clean shots.
Or skip the browser setup
If the immediate need is to capture a URL rather than build a visual-regression test suite, ScreenshotNeo offers a one-call screenshot API. Create an API key, then run this cURL example; the endpoint and supported parameters are documented in the ScreenshotNeo documentation.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/pricing -o shot.webpScreenshotNeo accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo free to get 1,000 screenshots a month with no card.
Best Value
Frequently Asked Questions
Does Playwright create a baseline automatically?
Yes. The first screenshot assertion run creates a reference image; later runs compare against it.
Is a screenshot API the same as visual regression testing?
No. An API captures an image; visual regression testing also needs a reference baseline, a comparison, and a process for reviewing changes.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
