Percy vs Visual Regression Tracker

Percy is a visual testing tool that captures DOM snapshots and assets, renders them, and checks them against earlier snapshots to identify visual changes. It can render pages across browsers and platforms, including desktop and mobile, and compare responsive layouts at configurable widths. Percy groups visual changes while filtering noise and freezes animations and other dynamic elements to reduce false positives. Snapshots from tests running on different processes or machines can be grouped into a single build. Its review workflow includes status updates, notifications, comments, baseline management, branch logic, and approval carryforwards. Percy supports web applications, component libraries, end-to-end testing frameworks, static sites, custom SDK integrations, and native mobile applications. The CLI can capture and upload snapshots without an automation script. A free plan includes 5,000 screenshots per month; paid plans have fixed screenshot allocations, with extra screenshots charged at an overage rate. Desktop costs $199 a month billed annually, and Desktop & Mobile costs $599 a month billed annually.

Visual Regression Tracker compares submitted screenshots with accepted baselines to flag unexpected visual changes. It keeps baseline history and lets teams exclude image regions from comparisons. Projects can choose among Pixelmatch, Looks-Same, Odiff, and a VLM comparison provider. The review dashboard supports side-by-side, diff, scrubber, and onion-skin views, with one-click approval. Feature branches inherit the main branch baseline until a change is approved, and builds can post commit status to GitHub or GitLab. The project lists agents for Playwright, Cypress, CodeceptJS, and Robot Framework, plus JavaScript, Java, Python, and .NET SDKs; its REST API supports other languages. A standalone JAR can compare PDFs as well as images. Deployment is self-hosted using Docker images, and the project says this keeps data inside the user's intranet. The documented screenshot upload payload limit is 20 MB. Each project has one owner; members can view snapshots and approve changes, while some actions are owner-only. It is open source under Apache-2.0.