Connect & Get help from fellow developers on our Discord community.
Ask the Community
Ask the Community
Percy integration options
Learn the different Percy integration options, including SDK-based, script-based or scriptless setups, browser management, and compatibility.
Percy offers multiple onboarding paths based on how you structure your tests and where you want to integrate visual testing. Use the table below to identify the best flow for your project. Each option links to its detailed setup guide.
| Category | Option | When to choose / Ideal for | Details |
|---|---|---|---|
| Integration | With automation (Script / SDK) | Choose this when you have an existing automation setup, prefer framework-level integration, or want to integrate snapshots directly in your test scripts. Ideal for established CI pipelines and frameworks like Selenium, Cypress, Playwright, Appium, etc. | Integrate Percy directly into your automation workflow: - Percy integration guides |
| Â | Without automation (No script / CLI) | Choose this for a quick start with minimal setup, static sites, unsupported frameworks, or manual/ad-hoc snapshot workflows. Ideal for evaluations, small projects, and standalone builds. | Start visual testing without writing automation code: - Percy without script |
| Manage browsers | With BrowserStack Automate | Choose this when you want to run your tests across a wide range of real browsers provided by BrowserStack Automate. Ideal for full cross-browser coverage. | Execute tests on multiple desktop and mobile browsers in Automate: - Set up Percy with BrowserStack Automate - Available Cross browsers for visual testing |
|  | Use Percy defaults | Choose this when relying on Percy’s predefined browser environments. Ideal for lightweight or isolated testing. | Execute snapshots using default Percy browser settings: - Set up Percy Web - Available Cross browsers for visual testing |
| Compatibility | Supported frameworks, SDKs, and Tools | Choose this when you want to verify environment support. Applies to all projects. | Check support across frameworks and environments: - SDK framework coverage - Percy on Automate framework coverage |
| SDK | Percy SDK | Choose this when you want direct access to Percy’s visual testing capabilities inside your test scripts, including DOM transformations, responsive snapshots, and advanced configuration. Ideal when you want full control through Percy’s native SDKs. | Add visual testing directly in your test framework using Percy SDKs. |
|  | BrowserStack SDK | Choose this when you want a unified setup for functional and visual testing using a single configuration file, with built-in support for Automate, and Percy. Ideal for teams standardizing on BrowserStack’s unified SDK workflow. | Configure functional and visual testing through a single unified SDK. |
Identify your preferred flow and follow the linked setup guide to integrate Percy into your workflow.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!