Skip to content
testcritic

BackstopJS vs Percy

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 and open source

Open source

Free tier available

Free tier

What drives the bill

The metric that actually scales your invoice.

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

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 tier

Everything, self-hosted

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

Open source

MIT

Self-hostable

No-code authoring

Languages

JavaScript
JavaScriptTypeScriptPythonRubyJava

Platforms

Web
Web

Fits teams

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

Adoption

Established

OSS community · since 2015

Widely used

BrowserStack · since 2015

Strengths

  • 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.
  • 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.

Limitations

  • 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.
  • 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.

Best for

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

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

All of these integrate with: Playwright, Jenkins.

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