What’s New in the Percy Visual Testing Platform
Percy currently highlights Visual Scanner for URL-based visual monitoring. Here’s how it fits with Percy’s snapshot testing, reviews, integrations, and release history.
Percy’s current homepage highlights Visual Scanner, a URL-based way to detect and monitor visual changes across browsers and devices without code or installations. Percy also supports integrated snapshot testing in existing frameworks and CI suites. The two workflows serve different setup needs: URL-based scanning starts from pages you configure, while snapshot testing adds visual checks to a test suite. Percy is part of BrowserStack. Percy’s homepage currently calls Visual Scanner a new launch, but the reviewed sources do not establish a launch date or its plan availability. Source: Percy
1. What Percy is highlighting now
Visual Scanner is the current feature Percy’s public landing page emphasizes. Percy describes it as a way to set up URLs and monitor visual changes across browsers and devices, with no code or installation required. Treat “new” as current homepage messaging, rather than a dated launch announcement: the reviewed sources do not identify when it launched.
The homepage also presents Percy as an all-in-one visual review platform. That broader positioning includes workflows for reviewing changes, while the integrations page describes SDK-based use with application and test workflows. Percy’s exact current Visual Scanner availability by plan was not verifiable in the reviewed material; check directly before choosing a plan.
2. Visual Scanner and integrated snapshot testing
| Workflow | How it starts | Useful when |
|---|---|---|
| Visual Scanner | Configure URLs for scanning | You want URL-based monitoring without adding code or an installation, as described on Percy’s current homepage. |
| Integrated snapshot testing | Add Percy to an existing framework or CI test workflow | You want visual snapshots tied to application tests, pull or merge requests, and your review process. |
Percy’s integration overview says its SDKs support web apps, native apps, static sites, style guides, and component libraries. It also describes CI/CD integrations, test suites distributed across processes or machines, pull/merge request connections, Slack notifications, and webhooks. These are integration capabilities; confirm the SDK, framework, CI service, and workflow details that apply to your stack on the official integrations page.
For snapshot testing, the basic cycle is to integrate Percy with the test setup, run tests that produce snapshots, and review visual changes against a baseline. Percy’s blog discusses baseline-based comparison. Its pages also describe scheduled scans, authenticated pages, staging validation, and notifications as workflow entry points. Those should not be conflated with the homepage’s URL-based Visual Scanner setup: choose based on whether you need test-triggered snapshots, URL monitoring, or both. Percy’s visual testing overview
3. Review, collaboration, and documented changes
Visual comparison is only useful if a team can inspect changes and decide what to do with them. Percy’s integration page describes pull/merge request and notification workflows. Its changelog documents collaboration updates, including Visual Reviews 2.0 and threaded comments. The changelog presents these as historical product updates, not proof of the exact current interface or feature availability.
Examples of dated entries in Percy’s official changelog include:
- July 12, 2024 — Percy on Automate: Header and Footer-Free Screenshots. The entry describes mobile screenshots without the status-bar header and navigation-bar footer.
- May 16, 2024 — Email Integration. The entry announced email updates for BrowserStack Percy tests.
- November 9, 2023 — Layout Testing. The entry describes checking changes in positioning, styling, and content structure without focusing on content changes.
- October 31, 2023 — Storybook v7 Support and Percy + Automate. The latter described testing on real devices across more than 3,500 device/browser combinations at that time. This is a historical figure from the 2023 changelog entry, not a current coverage count.
- July 12, 2023 — Microsoft Teams integration. The entry described real-time test updates in Teams.
- June 29, 2023 — Visual Reviews 2.0. Percy described an update to visual review focused on context, speed, and flexibility.
- July 9, 2020 — Percy becomes part of BrowserStack. The changelog announced Percy’s place within BrowserStack.
The latest visible dated changelog entry in the reviewed material is July 12, 2024. That does not establish that the page is a complete feed of later development. Use the official changelog for dated historical context and Percy’s current product pages for present-day positioning.
4. How to decide whether the update matters to your team
- Start with setup. If adding SDKs or changing CI is difficult, investigate whether Visual Scanner’s URL setup covers your pages and required monitoring. If visual assertions need to run with application tests, evaluate the integrated snapshot workflow.
- Check what you need to cover. Percy’s integrations overview lists web and native apps, static sites, style guides, and component libraries. Verify your specific framework and application type against its current documentation.
- Map the review path. Identify where reviewers should see changes: pull/merge requests, Percy’s review flow, or notifications. Confirm the integrations your team actually uses.
- Decide how pages are reached. For pages behind authentication or dependent on staging data, validate the workflow for authenticated pages and staging that Percy describes. A URL list alone may not represent every state your test suite needs.
- Verify commercial details directly. Current pricing, quotas, and Visual Scanner plan availability were not readable in the reviewed official material. Confirm them with Percy before purchase.
5. Screenshot a page without setting up browser automation
For a one-off screenshot or a screenshot API workflow, ScreenshotNeo provides a GET endpoint that returns an image or PDF. The following example requests a WebP screenshot of a public page; replace the key and target URL. See the ScreenshotNeo API documentation for the request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo also offers Python and Node.js request examples:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);The Node.js example uses the built-in fetch API and Bun’s file writer to save the response. With Node.js, write the response bytes to a file using the built-in filesystem API:
import { writeFile } from 'node:fs/promises';
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));These API examples capture a URL directly; they do not reproduce Percy’s baseline review or CI snapshot workflow. ScreenshotNeo has additional controls for full-page capture, element capture, device and viewport settings, retina scale, dark mode, PDF output, custom CSS/JavaScript, waits, request blocking, headers, cookies, user agent, timezone, geolocation, caching, async jobs, and bulk requests. See the docs for parameter names and usage.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. Its capture can accept cookie/consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before taking the shot; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. AI agents can use its MCP server tools: take_screenshot, get_page_info, and capture_pdf.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; all features are on every plan. Create a free ScreenshotNeo account and get 1,000 screenshots a month with no card.
6. Troubleshooting visual monitoring and screenshot workflows
| Symptom | Likely cause | What to check |
|---|---|---|
| You cannot find a dated Visual Scanner release | The current homepage calls it new, but the reviewed sources do not establish a launch date. | Use current Percy product pages to verify availability and ask Percy for plan-specific details. |
| A URL scan does not represent a logged-in or staging state | The page may require authentication or data setup beyond a public URL. | Validate the authenticated-page or staging workflow that fits your requirements, and check Percy’s current docs for configuration. |
| CI snapshots are not connected to the expected review flow | SDK, CI, or pull/merge request integration may be missing or configured differently. | Confirm the supported integration and notification settings on Percy’s integrations page. |
| A screenshot API returns an error instead of an image | The access key, URL encoding, network response, or target page may be invalid or unavailable. | Check the HTTP status, credentials, URL, and API documentation; do not assume every response body is an image. |
| The page looks incomplete in a capture | Images or other content may load after the initial navigation. | Use an appropriate wait strategy or full-page capture option and check that the target page is reachable. |
7. Performance, reliability, and cost considerations
For visual testing, reliability depends on repeatable page state: consistent test data, stable staging environments, predictable authentication, and a review path that surfaces intended changes. Distributed CI suites can help fit larger test workflows, but the integration details and supported services should be checked for your stack. URL monitoring can lower setup effort for pages reachable through the configured URLs; it does not by itself prove that every user state or authenticated flow is covered.
For screenshot API calls, network and page load time affect response latency. Use explicit timeouts in clients, encode URLs safely, and choose wait behavior that matches the page rather than adding arbitrary long delays. Caching can avoid repeated captures when a previous image is acceptable; async jobs and bulk capture can fit larger workloads. ScreenshotNeo provides a usage API and response billing headers, which can help track consumption. Its pricing is stated as 1,000 free shots monthly, then plans from $5 for 3,000 through $249 for 1,000,000; yearly billing gives two months free. Only clean shots are billed under the supplied product terms. These are ScreenshotNeo plan facts and do not describe Percy pricing.
8. Frequently asked questions
Is Visual Scanner a dated Percy release?
Percy’s homepage currently calls it a new launch, but the reviewed official pages do not establish a launch date.
Does Visual Scanner replace Percy snapshot testing?
The documented setup models differ: Visual Scanner is presented as URL-based, while integrated snapshots connect visual checks to application frameworks and CI. The available sources do not say one replaces the other.
Is Percy part of BrowserStack?
Yes. Percy’s homepage says it is now part of BrowserStack, and the changelog includes a dated July 9, 2020 entry about that relationship.
Where can I confirm Percy pricing?
Check Percy directly. Current pricing and Visual Scanner plan availability were not verifiable from the reviewed material.
Can ScreenshotNeo replace visual regression review?
ScreenshotNeo can capture screenshots through an API or MCP server. The supplied product information does not describe baseline comparison or a pull-request visual review system, so treat it as a screenshot capture option rather than a claim of equivalent Percy workflow.
Sources
- Percy product homepage — current Visual Scanner positioning and BrowserStack relationship.
- Percy integrations — SDK coverage, CI/CD, and workflow integrations.
- Percy changelog — dated historical updates.
- Percy visual testing overview — baseline comparisons and scanning workflow context.
- ScreenshotNeo API documentation — API options and parameters.
