Percy

Name: Percy
Author: BrowserStack

Visual review as a pull-request check, integrated with your existing E2E suite.

Visual TestingFree tier

What it is

Percy captures DOM snapshots during your existing Cypress, Playwright, Selenium or Storybook runs, renders them on its own infrastructure across widths and browsers, and posts a visual diff as a PR status check. Because it renders server-side from a captured DOM rather than storing raw screenshots, rendering is consistent regardless of the machine that ran the test. BrowserStack owns it.

Best for

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

Where it is strong

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.

Where it falls short

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.

Pricing

Free tier available

Free tier

Free tier: 5,000 screenshots a month, unlimited users and projects.

What drives the bill: 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.

Check current pricing on BrowserStack’s site

Figures are indicative and were last reviewed August 2026. Vendors change pricing often; confirm before you commit.