Migrate to Argos

Step-by-step guides for switching to Argos from Percy, Chromatic, Applitools, native Playwright screenshots, or BackstopJS.

Already running visual tests with another tool? These guides walk you through moving to Argos without rewriting your test suite. In most cases you keep your existing tests and only swap the SDK, the snapshot call, and the CI step.

Argos is built around three ideas that shape every migration:

• Keep your tests. Argos plugs into Playwright, Cypress, Storybook, WebdriverIO, and Puppeteer, or takes screenshots from any pipeline through the CLI. You don't rewrite tests to switch.
• Baselines live in Git, not in your repo. Argos selects the baseline build automatically from your Git history, so there are no reference images to commit, update, or resolve in merge conflicts.
• Review happens on the pull request. Diffs are approved or rejected in the Argos app and reported back as a commit status and PR comment.

Pick your current tool

Percy (BrowserStack)

Replace @percy/* SDKs and percy exec with the Argos reporter.

Chromatic

Move Storybook, Playwright, or Cypress visual tests off the chromatic CLI.

Applitools Eyes

Replace eyes.check() and the Ultrafast Grid with Argos screenshots.

Playwright screenshots

Move off committed toHaveScreenshot() snapshots to hosted review.

BackstopJS

Move from self-hosted backstop.json scenarios to a hosted workflow.

Don't see your tool?

If you're coming from a tool that isn't listed, the Any test framework quickstart covers the generic path: capture screenshots however you do today, then upload them with argos upload. Contact support if you'd like help planning a migration.