Softwr

Testing · head to head

Percy vs SoapUI

Percy logo

Percy

Testing

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

From
Free
Free plan
Yes
SoapUI logo

SoapUI

Testing

Open source API testing tool for REST, SOAP and GraphQL, from SmartBear

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Percy lists screenshot diffing; only SoapUI lists REST, SOAP, GraphQL and JMS API testing.
  • Where Percy falls short: paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale.
  • Where SoapUI falls short: open source edition has no data-driven testing or native SDLC integrations.
  • Prices and features on this page were last checked on 20 November 2026.

How do Percy and SoapUI differ?

Percy and SoapUI differ on pricing model and platforms. Only the attributes on which Percy and SoapUI actually diverge.

Attributes where Percy and SoapUI differ
AttributePercySoapUI
Pricing modelFreemium, paid tiers by screenshot volumeOpen-source
PlatformsWebWindows, macOS, Linux

Identical on both: starting price (Free), free tier (Yes), category (Testing).

Which features does each one have?

They share no listed features; 6 appear only for Percy and 8 only for SoapUI. 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 SoapUI

  • REST, SOAP, GraphQL and JMS API testing
  • Groovy and JavaScript scripting
  • Functional test suites with assertions
  • Open source edition under the EUPL
  • ReadyAPI edition with security and performance testing
  • Service virtualisation in ReadyAPI
  • Data-driven testing in ReadyAPI
  • CI integrations with Jenkins, TeamCity and Azure DevOps in ReadyAPI

What is each one used for?

SoapUI is most often brought in for functional testing of SOAP web services. 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 SoapUI
  • A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot SoapUI
  • A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot SoapUI
  • A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot SoapUI

SoapUI

  • Functional testing of SOAP web servicesnot Percy
  • REST and GraphQL API regression checksnot Percy
  • Scripted API tests in Groovynot Percy
  • Evaluating ReadyAPI before a team purchasenot Percy

Where do Percy and SoapUI fall short?

SoapUI's most cited limit: open source edition has no data-driven testing or native SDLC integrations. 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

SoapUI

  • Open source edition has no data-driven testing or native SDLC integrations
  • Test refactoring and result comparison are manual in the open source edition
  • Security, performance and virtualisation testing require the paid ReadyAPI edition
  • ReadyAPI prices are not listed on the vendor pages, so cost needs a quote or cart visit

How much do Percy and SoapUI cost?

Percy is free to use; SoapUI is free to use. Plan by plan below, from each vendor's own pricing page.

Percy

Free
  • FreeFree
    • 5,000 screenshots a month
    • Unlimited users and projects
    • 30-day build history
  • PercyOn request
    • 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

SoapUI

Free

No published plan breakdown. See the SoapUI review.

Which should you pick?

Choose Percy if

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

Choose SoapUI if

  • You need rest, soap, graphql and jms api testing.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want groovy and javascript scripting.

Questions people ask

Is Percy or SoapUI better?
Neither clearly leads. Percy starts at Free and SoapUI at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Percy or SoapUI?
Percy starts at Free and SoapUI at Free.
Does Percy or SoapUI run on more platforms?
Percy runs on Web. SoapUI runs on Windows, macOS, 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 SoapUI is typically brought in for.
What can Percy do that SoapUI cannot?
Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow. SoapUI covers REST, SOAP, GraphQL and JMS API testing, Groovy and JavaScript scripting, Functional test suites with assertions, Open source edition under the EUPL.

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.

SoapUI: Is SoapUI free?

The open source edition is free and licensed under the European Union Public License. The commercial ReadyAPI edition is paid, and the vendor offers a 14-day free trial.

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

SoapUI: What protocols does it support?

The open source edition supports REST, SOAP, GraphQL and JMS. ReadyAPI adds XML-RPC, MQTT and other protocols.

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

SoapUI: Who makes SoapUI?

SmartBear Software develops it. The project was first released on SourceForge in 2005 and SmartBear acquired its developer Eviware in 2011.

Source
SoapUI: Which operating systems does it run on?

It is written in Java and Groovy, so it runs across operating systems that support Java. It also has plugins for the IntelliJ IDEA, Eclipse and NetBeans IDEs.

Source
Share

Related pages

Other head to heads