Comparisons

Applitools vs Percy

Applitools (Visual AI testing) and Percy (Visual AI testing) differ on 6 documented facts below. Each cell shows its evidence level, source and verification date. This page does not rank or rate either tool.

Oldest fact on this page:

Facts side by side

Applitools and Percy, fact by fact, with evidence per cell
FactApplitoolsPercy
Category
Visual AI testing (also Agentic end-to-end testing, Natural-language test authoring)
DocumentedSource
Visual AI testing
DocumentedSource
Status
Active
DocumentedSource
Acquired
DocumentedSource
Test creation
Prompt to test, Natural language, Recording, Autonomous from URL, Code generation
DocumentedSource
Not documented
Not documented
Test output
Mixed
DocumentedSource
Not documented
Not documented
Surfaces
Web, Mobile native
DocumentedSource
Web, Mobile native
DocumentedSource
Hosting
Cloud, Self-hosted
DocumentedSource
Cloud
DocumentedSource
Pricing model
Flat tier, Enterprise quote
DocumentedSource
Free tier, Flat tier, Enterprise quote
DocumentedSource
Published prices
Starter: $667 / mo (paid annually)
DocumentedSource
Free: $ 0 / month (5000 free monthly screenshots); Desktop: $ 199 / month (billed annually; each additional screenshot at $0.036); Desktop & Mobile: $ 599 / month (billed annually; each additional screenshot at $0.048)
DocumentedSource
Free tier
No
DocumentedSource
Yes
DocumentedSource
CI integrations
GitHub Actions, Jenkins, CircleCI, GitLab, Azure DevOps, Other
DocumentedSource
GitHub Actions, GitLab, CircleCI, Jenkins, Azure DevOps, Other
DocumentedSource
Self-healing
Documented
DocumentedSource
Not documented
Not documented
Agent integration
Applitools MCP Server (Eyes): connects AI assistants such as Cursor, GitHub Copilot, Cline and Claude Code to create, update, review and resolve visual tests
DocumentedSource
BrowserStack MCP server (browserstack/mcp-server) with Percy tools such as percyVisualTestIntegrationAgent, addPercySnapshotCommands, runPercyScan, fetchPercyChanges and managePercyBuildApproval
DocumentedSource
Open source
Not documented
Not documented
Not documented
Not documented

Documented differences

Listed only where both tools document the fact, or where one documents it and the other's documentation does not mention it. Vendor-stated values appear in the table but do not create a difference here.

  • Status: active for Applitools; acquired for Percy. [1][2]
  • Test creation: prompts, natural-language steps, recording, autonomous exploration from a URL and generated code for Applitools; not documented for Percy. [1]
  • Test output: a vendor runner plus exportable framework code for Applitools; not documented for Percy. [1]
  • Hosting: cloud and self-hosted for Applitools; cloud for Percy. [1][2]
  • Free tier: none for Applitools; available for Percy. [1][2]
  • Self-healing: yes for Applitools; not documented for Percy. [1]

When each fits

Applitools

Fits a team that needs a vendor runner plus exportable framework code as test output. Documented for Applitools.

Sources: [1]

Percy

Fits a team that needs a free tier. Documented for Percy.

Sources: [1]

Drawn from documented scope only. Neither text compares the two tools on quality.

Sources

  1. applitools.com (Applitools: Category; Applitools: Status; Applitools: Hosting; Applitools: Pricing model; Applitools: Published prices; Applitools: Free tier)
  2. browserstack.com (Percy: Category)
  3. browserstack.com (Percy: Status)
  4. applitools.com (Applitools: Test creation)
  5. applitools.com (Applitools: Test output)
  6. applitools.com (Applitools: Surfaces)
  7. browserstack.com (Percy: Surfaces)
  8. browserstack.com (Percy: Hosting)
  9. browserstack.com (Percy: Pricing model; Percy: Published prices; Percy: Free tier)
  10. applitools.com (Applitools: CI integrations)
  11. browserstack.com (Percy: CI integrations)
  12. applitools.com (Applitools: Self-healing)
  13. applitools.com (Applitools: Agent integration)
  14. github.com (Percy: Agent integration)

Spotted an outdated or wrong fact about Applitools vs Percy? Send the source and we apply it at the next monthly update.

Report a change