Best Cypress Alternatives for Screenshots in 2026

If you need visual regression tests, cy.screenshot() alone is not enough: Cypress captures images but does not compare them with a baseline. Choose Playwright Test if you are ready to change runners and want built-in screenshot assertions, a Cypress image-diff plugin if you want local comparisons while keeping Cypress, or a hosted visual testing service if managed rendering and review workflows matter more than keeping the whole process local. There is no universal best choice; migration effort, baseline ownership, browser coverage, comparison style, and review workflow decide the fit.

For website screenshots outside a test suite, ScreenshotNeo is the first API alternative to try: it removes consent banners, popups, and chat widgets before capture, bills only clean shots, and has the lowest paid plan listed here. It complements visual regression tooling; it is not a replacement for a baseline comparison workflow.

1. What a Cypress screenshot does—and does not—do

Cypress provides cy.screenshot() for capturing a page or test failure and configuration for screenshot storage and video capture. A visual regression test needs more: it must preserve a reference image, capture the same state again, compare the two, and make a change reviewable. Cypress’s visual testing guide states that Cypress itself does not compare images. Add a plugin or connect a service to perform that comparison. Cypress visual testing documentation and its screenshots and videos guide describe the distinction.

A screenshot regression workflow captures a stable state, compares it with a reference, and routes changes for review.

A passing screenshot test therefore depends on more than capture syntax. You need stable test data, a known browser and viewport, a baseline-update policy, and a way to decide whether a difference is a regression or an intentional change.

2. Cypress alternatives for screenshots: the shortlist

Option	Best fit	What it provides	Main tradeoff
ScreenshotNeo	Capturing clean website screenshots through an API or AI agent	One-call PNG, JPEG, WebP, or PDF capture; consent and widget cleanup; only clean shots billed; MCP tools	It captures pages; use a visual testing tool to compare versioned baselines
Playwright Test	Teams willing to move tests to Playwright and keep snapshots with code	Built-in `toHaveScreenshot()`, pixel-diff controls, stylesheet support to hide volatile content	Team manages reference files and must keep comparison environments consistent
Local Cypress image-diff plugins	Teams staying on Cypress who want local or CI comparison	Local comparison and baseline files; Cypress lists Cypress Image Diff, Cypress Image Snapshot, Cypress Visual Regression, and Visual Regression Diff	Team owns baseline updates, rendering consistency, artifact storage, and diff review
Applitools Eyes	Cypress users seeking AI-assisted comparison and cross-browser visual testing	Cypress describes Visual AI, end-to-end and component testing, cross-browser rendering, and root cause analysis	Hosted commercial service; confirm current integration and terms with the vendor
Chromatic	Teams wanting cloud snapshots and structured review and approval with Cypress	Cypress plugin, archived page upload, snapshot generation, pixel diff, and review workflow	Its Cypress instructions require Chrome for snapshotting and use an archived-project workflow
Percy (BrowserStack)	Teams wanting cloud rendering across browsers and responsive widths	Cypress documents DOM snapshots through `cy.percySnapshot()`, cloud rendering, and review and approval	Hosted workflow; verify supported configurations and terms
Other listed services	Teams whose provider-specific browser matrix or workflow is a match	Argos, Happo, LambdaTest SmartUI, Sauce Labs Visual, SmartBear VisualTest, and Wopee.io have integrations documented by Cypress	Check exact Cypress versions, browser coverage, workflow, and current terms directly

Cypress’s visual testing guide describes open-source plugins and commercial services, and explains their different baseline and review responsibilities. Its plugin directory is useful for checking current package compatibility. Directory entries and supported versions change; recheck before adopting. The reviewed material does not establish a comparable current price table for the listed visual testing providers, so compare their current plans directly rather than relying on an assumed ranking.

3. How to choose a visual regression workflow

Decide whether to keep Cypress. If migration is acceptable, Playwright supplies screenshot assertions in its test runner. If the rest of your suite is established in Cypress, a plugin or service adds comparison without replacing the runner.
Choose baseline ownership. Local plugins usually leave reference images and updates in the project or CI workflow. Hosted services manage more of the baseline and review process. Decide who approves changes and how updates are audited.
Set the required coverage. A single controlled browser and viewport may be enough for a component or page. If you need multiple browsers, responsive widths, or device rendering, confirm the chosen tool supports the exact matrix you require.
Pick comparison behavior. Pixel differences are straightforward and can be noisy when rendering shifts. Cypress describes Applitools as using AI-assisted Visual AI comparison. Understand what the tool flags and how reviewers inspect a diff.
Make review part of the test. A difference without a clear artifact and approval path can be ignored or accepted blindly. Ensure developers can inspect changed regions and record intentional baseline updates.
Check compatibility and terms. Verify the Cypress version, browser versions, CI environment, install steps, supported operating systems, plan limits, and current commercial terms against vendor documentation.

4. Playwright visual comparisons: runnable example

This is the code-first route when you can use Playwright Test. Install the test runner, save the test below, and run it once to create a reference snapshot. Later runs compare against that reference; inspect and intentionally update it when the design change is expected. Consult the official Playwright visual comparisons guide for current configuration and platform details.

npm init playwright@latest

For example, save this as tests/homepage.spec.ts:

import { test, expect } from '@playwright/test';

test('homepage visual appearance', async ({ page }) => {
  await page.setViewportSize({ width: 1280, height: 800 });
  await page.goto('http://127.0.0.1:3000');
  await page.getByRole('heading', { name: 'Welcome' }).waitFor();

  await expect(page).toHaveScreenshot('homepage.png', {
    fullPage: true,
    maxDiffPixels: 80,
    stylePath: 'tests/visual-stability.css',
  });
});

Create tests/visual-stability.css if the page contains a clock or other known volatile region:

.live-clock,
.ad-slot {
  visibility: hidden !important;
}

Run the test with npx playwright test. To deliberately create or refresh snapshots, Playwright Test supports its snapshot update workflow; check the documentation for the appropriate update flag and review the resulting files before committing. Do not update every baseline automatically in ordinary CI: that would turn unexpected changes into accepted references.

Useful assertion controls and boundaries

fullPage: true captures the full page; omit it for the viewport screenshot. Prefer a focused locator screenshot when a page-wide image adds unrelated noise.
maxDiffPixels allows a specified number of differing pixels. Tune it only after stabilizing the test, since a permissive threshold can conceal a real change.
stylePath applies a stylesheet during capture; hide a small known volatile region rather than loosening comparison across the whole page.
Control test data, animation, time, viewport, browser, and font availability. Playwright warns that screenshots can vary with operating system, browser version, settings, hardware, and headless mode; generate and compare snapshots in the same environment.

The sample assumes the application is already running at 127.0.0.1:3000 and that the heading is present. Replace the URL and readiness condition with those for your app. If you use a locator assertion instead of a page assertion, confirm the current Playwright API and options in its documentation.

5. Keep Cypress and add a visual comparison

If Cypress remains the right end-to-end runner, use its maintained plugin directory as the starting point. Cypress lists Cypress Image Diff, Cypress Image Snapshot, Cypress Visual Regression, and Visual Regression Diff as open-source options, and Pixeleye as a self-hostable visual review platform with a Cypress integration. Plugin APIs differ, so use the current package documentation for installation, commands, threshold configuration, and CI setup; no single plugin API applies to all of them.

The general workflow is consistent:

Install a plugin compatible with your Cypress version and browser.
Configure where baseline images are stored and how the plugin names snapshots.
Write tests that navigate to a stable page state before capture.
Run locally or in CI to create the initial baseline.
On later runs, inspect generated diffs and artifacts; update baselines only for reviewed design changes.
Keep the capture environment stable and make artifacts available to the people reviewing failures.

Use Cypress’s plugin directory to recheck compatibility. For example, the September 2026 directory entries in the supplied research list Chromatic’s Cypress plugin and Cypress Image Snapshot with a Cypress minimum of 15.10.0, and Visual Regression Diff with Cypress 13.0.0 or later. Treat these as time-sensitive directory listings, not permanent guarantees; verify the current entry before installing.

6. Hosted services: what you gain and what to verify

Hosted tools can take on baseline storage, rendering consistency, cross-browser capture, and team review. They can be a good fit when a local diff is hard to distribute or the project needs browser coverage that the CI environment does not provide. The tradeoff is an external workflow and subscription terms, plus the need to confirm that the provider supports your exact app and Cypress setup.

Chromatic’s Cypress documentation describes an archived-project flow, Chrome for snapshotting, pixel diffing, and review and approval. Percy documents DOM snapshots from Cypress followed by cloud rendering and review. Applitools is described by Cypress as an AI-assisted visual comparison service. Cypress also documents integrations for Argos, Happo, LambdaTest SmartUI, Sauce Labs Visual, SmartBear VisualTest, and Wopee.io. These capabilities do not establish that any one provider supports every browser, component framework, or current Cypress release. Check the vendor’s current integration guide and pricing before committing.

7. Reliability: reduce noisy screenshot diffs

Capture a deliberate state. Wait for the page content and application state that the test is meant to verify. Avoid taking a snapshot while requests or transitions are still changing the page.
Use deterministic data. Fix API responses, timestamps, randomized content, and account state where the test allows it. Control animations and rotating content.
Pin the rendering conditions. Keep browser version, operating system or container image, fonts, viewport, device scale, and headless settings consistent between baseline and comparison.
Keep the target useful. Use full-page captures when below-the-fold layout is part of the requirement. Otherwise, capture the relevant component or viewport to limit unrelated differences.
Mask narrowly. Hide or mask a small uncontrollable area. A page-wide threshold increase can make real regressions harder to see.
Review artifacts, not just status. Make the changed screenshot and diff easy to inspect in CI or a service dashboard. Record why a baseline changed.

Cypress recommends stable page states and environments, handling time- and API-driven content, and choosing meaningful snapshot targets. Playwright likewise recommends comparing in a consistent environment. A diff threshold is a tuning control, not a replacement for these practices. See the Cypress guide and Playwright guide.

8. Or skip the browser setup

If you need a clean website screenshot for documentation, a report, an AI agent, or a downstream visual check, ScreenshotNeo takes a URL in one request. See the ScreenshotNeo API docs for parameters and formats.

Screenshot cleanup can remove common overlays before a page image is returned.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

Cookie banners, newsletter popups, and chat widgets are removed before the shot. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers report the page verdict and billing status. The MCP server gives AI agents tools for screenshots, page information, and PDF capture. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000. Other API options include full-page capture, selector targeting, viewport and device presets, custom CSS or JavaScript, wait conditions, request blocking, caching, signed links, asynchronous jobs, bulk capture, PDF output, and usage reporting. Every feature is on every plan. This API does not create or approve visual baselines, so use a visual regression workflow when that is the goal.

9. Troubleshooting common failures

Symptom	Likely cause	Fix
Screenshot assertion fails on every run	Baseline was created with a different browser, OS, font set, viewport, or rendering mode	Use a consistent CI image and browser version; regenerate the baseline deliberately in that same environment
Diffs change between runs	Dynamic API data, time, animation, ads, or rotating content	Stabilize fixtures and time, wait for the intended state, and mask only the small volatile region
Page is captured before it is ready	Navigation completion does not mean the app’s target content has settled	Wait for a meaningful selector or explicit app-ready condition before snapshotting
Large diffs after a harmless environment change	Browser, OS, hardware, headless mode, device scale, or fonts differ	Align the baseline and comparison environment; avoid mixing local and CI baselines without a reason
Plugin install or command fails	Package and Cypress versions are incompatible, or the integration setup changed	Check the current Cypress plugin directory and the plugin’s own install guide; verify the configured browser and CI dependencies
Hosted capture does not match local page	Different rendering path, missing environment access, or unsupported configuration	Check provider docs for DOM versus browser capture, network access, authentication, browser, and viewport requirements
Unexpected snapshot update in CI	Baseline update mode ran where comparison should be read-only	Keep baseline writes in a deliberate review workflow; require a human to inspect changed references

10. Performance, reliability, and cost

Local screenshot comparisons add browser capture and image comparison work to CI; hosted services add upload, remote rendering, and review steps. The supplied sources do not publish comparable benchmark results, so measure the full workflow on representative pages and browser matrices rather than assuming one is faster. Reduce unnecessary full-page or multi-browser captures, reuse the existing test setup where possible, and parallelize only where it does not introduce unstable shared data.

Reliability comes primarily from stable inputs and repeatable rendering. Local plugins avoid a hosted baseline dependency but make your team responsible for storage, artifacts, environment, and review. Services can manage more of the rendering and review workflow, while bringing vendor availability, access, configuration, and plan constraints into the path. Confirm current pricing, usage limits, and terms with each provider; the researched material does not support a price comparison among those services.

ScreenshotNeo pricing for its separate screenshot API is: Free, 1,000 shots per month; Starter, $5 for 3,000; Growth, $15 for 15,000; Pro, $39 for 60,000; Scale, $99 for 250,000; Business, $249 for 1,000,000. Yearly billing gives two months free. Every feature is included on every plan. Its billing model charges only for clean shots, with verdict and billing headers returned per response. See the docs for API behavior and parameters.

11. FAQ

Can Cypress compare screenshots without a plugin?

No. Cypress can capture screenshots, but its visual testing documentation says image comparison requires a plugin or service.

Should I migrate an existing Cypress suite to Playwright just for screenshots?

That depends on migration cost and the value of Playwright’s built-in assertion. If Cypress already serves the suite well, evaluate a compatible plugin or hosted integration first; if you are already considering a runner change, Playwright’s reference snapshots may fit.

Are screenshot assertions the same as visual acceptance testing?

They provide captured images and comparisons. Your team still needs to choose meaningful coverage, review changes, and decide which differences are acceptable.

Can ScreenshotNeo replace Percy or a Cypress image-diff plugin?

Not for baseline comparison and review: ScreenshotNeo captures website screenshots and PDFs through an API or MCP server. Use a visual testing tool to manage and compare baselines.

How often should baselines be updated?

Update them when a reviewed product change makes the old reference obsolete. Keep the changed image reviewable so an accidental regression is not accepted as a new baseline.