Playwright

Playwright screenshots vs Argos

Choose Argos when visual tests run in a team: baselines from your Git history, comparisons made in CI only and a review on the pull request. Stay with toHaveScreenshot() on a solo project where committing PNGs and regenerating them in Docker is fine.

Read the migration guide

Choose Argos if

  • Several people update baselines, and PNG merge conflicts slow you down.
  • Screenshots differ between macOS and Linux CI, and you regenerate baselines in Docker.
  • You want designers or product people to review changes on the pull request.
  • You want Playwright traces, retries and flaky test detection next to the review.

Stay with toHaveScreenshot() if

  • You work alone or on a small project, and committed PNGs aren't a problem.
  • Everything has to run offline, with no external service.
  • You already generate baselines in a pinned Docker image and review them in Git.
ArgosPlaywright screenshots
Snapshot testing for any file
Diff Markdown, JSON, HTML and more, not just images		YesLocal only
Deployments & PR previews
Host Storybook or any static build on a live URL		YesNo
Collaborative reviews
Pinned comments, threads, reactions, real-time presence		YesNo
Agent-ready CLI & API
Agents inspect and review builds from the CLI and REST API		YesNo
Cloud baselines
No committed *-snapshots/ PNGs in Git		YesNo
Review UI on the pull request
Approve changes without --update-snapshots		YesNo
Cross-platform consistency
No -darwin vs -linux baseline mismatches
YesNo
Playwright debugging
Playwright trace viewer and failure screenshots		YesLocal only
Playwright test retries
Separate test retries to have a clear overview		YesLocal only
GitHub SSO
Synchronize your GitHub users with Argos		YesNo
Spend Management
Control your spendings by setting a budget limit		YesNo
Open Source
SDK and platform code available		YesYes
GitHub integration without code access
Offer a mode without content permission required		YesNo
Sensitivity threshold per screenshot
Set a threshold by screenshot to reduce flakiness		YesPer assertion
GitHub Actions partial re-runs
Save time and resources with partial re-runs		YesNo
Monitoring mode
Run periodic checks on your website		YesNo

Sources for Playwright screenshots: Playwright visual comparisons. Checked October 2026.

Frequently Asked Questions

Does Argos replace Playwright?

No. Argos runs on top of Playwright. You keep your Playwright tests and config, and swap toHaveScreenshot() for argosScreenshot(). Argos adds cloud baselines, a review UI, and pull request checks around the tests you already have.

What happens to my committed PNG baselines?

You delete them. With native snapshots, baselines live in *-snapshots/ folders in Git. With Argos, baselines are selected from your Git history in the cloud, so there are no PNGs to commit, no merge conflicts, and no repo bloat.

How do I approve an intended visual change?

In the Argos review UI, right on the pull request. A visual difference becomes a check you review and approve, instead of a failed test you fix by re-running with --update-snapshots and committing new images.

Do I still get cross-browser and cross-platform consistency?

Yes. Native snapshots are platform-specific (-darwin vs -linux), so teams run them only in Docker or CI to stay consistent. With Argos, screenshots taken in CI are compared with baselines also taken in CI, so a laptop never produces a baseline and there is one set of images, not one per platform.

Read the migration guide for the step-by-step.

Playwright

Supercharge your product quality

Ready to switch to Argos? Get started for free today. No credit card required.

Sign upRequest demo