Compare the tools

Runner integrations, hosted review services, diff engines and mobile tools, compared on facts from their own docs.

Every row is one YAML file in the repository, with a date it was last checked and links to the vendor's own documentation for each claim. Pricing is listed as a model, never as numbers, because numbers are the first thing to go stale. Click a row for the details, the sources, and a link to correct it.

The column most comparisons leave out is machine-readable results: what a tool running after the tests can read. Most tools leave you image folders and nothing else, hosted services keep the results inside their app, and a few write a JSON report. The manifest column says whether a tool writes the run manifest itself, has a converter in visual-regression-manifest, or fits the generic image-triple converter.

31 of 31 tools
ToolCategoryRunsReviewBaselinesPricingMachine-readable resultsManifest

How to read it

  • Runs: where the comparison happens. Local tools diff on the machine running the tests; cloud services take screenshots or DOM snapshots and diff on their side; self-hosted means you run the service.
  • Review: where a human looks at the diff. Local files means opening the images yourself; pull request means a comment or check on the PR; web app means the service's own UI.
  • Baselines: where the reference images live. In the repository they version with the code; in a service they version with the service's notion of a branch.
  • Pricing: free, a free tier with paid plans, per screenshot, per seat, or a custom quote. Check the vendor for the numbers.

Adding or correcting a tool

Open a pull request with a YAML file under apps/site/data/tools/. Every field is validated at build time, every claim needs a source URL from the tool's own documentation, and lastVerified is the day you checked. Vendor contributions are welcome and are held to the same standard as everyone else's.