Skip to content
testcritic

Percy vs BackstopJS

Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.

Entry price

Free tier available

Free tier

Free and open source

Open source

What drives the bill

The metric that actually scales your invoice.

BrowserStack no longer publishes standalone Percy prices — its own /percy/pricing page is gone and Percy now appears bundled into wider BrowserStack packages (it is one of the products in Team Ultimate at $375/month billed annually) or priced by sales. Paid plans still include a fixed screenshot allowance with overage on top, so multiply pages x widths x browsers x commits before committing — this is where budgets are misjudged.

Free and open source. You pay in engineering time and CI minutes.

Free tier

5,000 screenshots a month, unlimited users and projects.

Everything, self-hosted

Open source

MIT

Self-hostable

No-code authoring

Languages

JavaScriptTypeScriptPythonRubyJava
JavaScript

Platforms

Web
Web

Fits teams

StartupScale-up / mid-marketEnterprise
Solo / side projectStartupScale-up / mid-market

Adoption

Widely used

BrowserStack · since 2015

Established

OSS community · since 2015

Strengths

  • Plugs into an existing suite with a few lines rather than requiring new tests.
  • Server-side rendering removes machine-to-machine screenshot inconsistency.
  • Good PR-based approval workflow that developers actually use.
  • Free with no snapshot quota — run it as often as you like.
  • Baselines stay in your repository, which suits regulated or air-gapped environments.
  • Simple JSON configuration that a junior engineer can extend.

Limitations

  • Screenshot-based billing escalates faster than teams expect.
  • Dynamic content requires careful masking or you drown in false diffs.
  • Responsive widths are rendered, not truly executed in each browser, which occasionally hides real issues.
  • Pixel-diff comparison means font rendering differences between machines cause false failures; Docker is effectively mandatory.
  • No hosted review or approval workflow — approving means committing new images.
  • Reference images bloat the Git repository over time.

Best for

Teams with an existing E2E or Storybook suite who want visual coverage without new tests.

Teams that need visual testing without a SaaS vendor or a per-snapshot bill.

All of these integrate with: Playwright, Jenkins.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.