Softwr

Testing · head to head

Percy vs Testsigma

Percy logo

Percy

Testing

Visual regression testing owned by BrowserStack, with a permanent free tier for low screenshot volume

From
Free
Rated
-
Testsigma logo

Testsigma

Testing

Natural language test automation for web, mobile and API with a self hosted open source edition

From
Free
Rated
-

The short version

  • Each has a real cost: Percy pixel-based diffing generates more false positives from font rendering and anti-aliasing noise than Applitools' AI-based comparison, which trains some teams to start ignoring diff alerts over time.; Testsigma the natural language layer is a fixed vocabulary rather than real English, so testers spend the first weeks learning which phrasings the parser accepts, which is learning a language after all.
  • They diverge on capability: Percy covers Screenshot diffing, Testsigma covers Natural language authoring.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Percy and Testsigma actually diverge.

Attributes where Percy and Testsigma differ
AttributePercyTestsigma
Pricing modelFreemium, paid tiers by screenshot volumePer user per month
PlatformsWebWeb, iOS, Android, Linux

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Testing).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Percy

  • Screenshot diffing
  • Framework integrations
  • Responsive and cross-browser snapshots
  • Review workflow
  • Build history
  • BrowserStack platform integration

Only in Testsigma

  • Natural language authoring
  • Unified web, mobile and API tests
  • Self hosted community edition
  • Cloud device and browser grid
  • Data driven runs
  • Custom functions

What people use each for

The jobs each tool is most often brought in to do.

Percy

  • A team already on BrowserStack for device testing that wants to add visual regression without a separate vendor relationshipnot Testsigma
  • A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot Testsigma
  • A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot Testsigma
  • A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot Testsigma

Testsigma

  • A team maintaining separate Selenium and Appium suites that wants one place for web and native mobile coveragenot Percy
  • Organisations that must keep test data and execution on premises for regulatory reasonsnot Percy
  • QA groups with manual testers being asked to automate without first learning Javanot Percy
  • Evaluating low code test automation properly before committing budget, by running the free edition against the real applicationnot Percy

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Percy

  • Pixel-based diffing generates more false positives from font rendering and anti-aliasing noise than Applitools' AI-based comparison, which trains some teams to start ignoring diff alerts over time.
  • It is billed separately from core BrowserStack device testing, and stacking Percy with other BrowserStack modules such as Accessibility Testing materially increases total contract value beyond the headline device testing price.
  • Paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale.
  • The free tier's 5,000-screenshot cap is easy to exceed for any team running visual tests across multiple browsers and viewports on every commit, pushing many active projects into a paid tier faster than the free number suggests.
  • As part of a larger acquired portfolio, Percy's roadmap priority within BrowserStack's broader product strategy is less certain than it would be as a standalone company's sole focus.

Testsigma

  • The natural language layer is a fixed vocabulary rather than real English, so testers spend the first weeks learning which phrasings the parser accepts, which is learning a language after all.
  • Anything conditional or arithmetic falls through to custom Java or JavaScript, and that code lives in the platform editor rather than your repository, where it gets no code review and no version history you control.
  • The community edition lags the cloud product and is not the version the vendor demonstrates, so a self hosted evaluation can understate or overstate what you would actually buy.
  • Cloud execution is billed separately from authoring seats, so a suite that grows from two hundred to two thousand tests changes the bill without anyone changing the plan.
  • Support and engineering are concentrated in Indian time zones, which slows incident turnaround for teams working in the Americas.

Pricing, plan by plan

Percy

Free
  • FreeFree
    • 5,000 screenshots a month
    • Unlimited users and projects
    • 30-day build history
  • Percy$undefined/month
    • Priced by screenshot volume above the free tier
    • Sold separately from core BrowserStack device testing plans
    • Get a current quote before assuming bundled pricing with other BrowserStack products

Testsigma

Free
  • Community Edition$undefined/month
    • Self hosted, open source, no licence fee
    • You supply the infrastructure and the browser or device grid
  • Cloud$undefined/month
    • Priced per authoring user with additional charges for parallel cloud executions and device minutes
    • Published tiers exist but the figures that matter at team scale come from sales

Which should you pick?

Choose Percy if

  • You need screenshot diffing.
  • You want to start without paying.
  • You also want framework integrations.

Choose Testsigma if

  • You need natural language authoring.
  • You want to start without paying.
  • You work on Web, iOS, Android, Linux.
  • You also want unified web, mobile and api tests.

Questions people ask

Is Percy or Testsigma better?
Neither clearly leads. Percy starts at Free and Testsigma at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Percy or Testsigma?
Percy starts at Free and Testsigma at Free.
Does Percy or Testsigma run on more platforms?
Percy runs on Web. Testsigma runs on Web, iOS, Android, Linux.
Can I use Percy for free?
Both have a free tier, so you can try either at no cost before committing.
What is Percy best used for?
Percy is most often used for a team already on browserstack for device testing that wants to add visual regression without a separate vendor relationship, a low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anything, a team wanting a lower cost per screenshot than applitools and willing to tolerate more manual false-positive triage, a cypress or playwright test suite adding visual checks without changing its existing test runner. Of those, a team already on browserstack for device testing that wants to add visual regression without a separate vendor relationship and a low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anything are not what Testsigma is typically brought in for.
What can Percy do that Testsigma cannot?
Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow. Testsigma covers Natural language authoring, Unified web, mobile and API tests, Self hosted community edition, Cloud device and browser grid.

Answered from the vendors’ own pages

Percy: Is Percy free?

Yes for up to 5,000 screenshots a month with unlimited users and projects; beyond that it is a paid, quote-priced module.

Testsigma: Is the open source edition genuinely usable in production?

Yes for self hosted execution, though it trails the cloud version on newer features and you maintain the grid yourself.

Percy: Is Percy included if I already pay for BrowserStack device testing?

No, it is billed separately by screenshot volume, not bundled into core device testing plans.

Testsigma: Do testers need to know Selenium?

Not to write ordinary steps. They will need someone who does as soon as the suite needs custom functions or awkward waits.

Percy: How does it compare to Applitools?

Percy uses pixel-based diffing, which is generally cheaper per screenshot but produces more false positives than Applitools' AI-based perceptual comparison.

Testsigma: Can it test native iOS and Android applications?

Yes, through Appium underneath, on the hosted device grid or your own devices.

Share

Related pages

Other head to heads