BrowserStack Screenshots Pricing for Teams and Parallel Tests
Compare Percy’s screenshot allowances, overage rates, and parallel testing. Learn how to estimate usage and what to confirm for a team quote.
BrowserStack’s Percy pricing is based on monthly screenshot volume, with the displayed plan also varying by desktop or desktop-and-mobile coverage. The pricing page captured on October 3, 2026 showed Percy Desktop at $199 per month billed annually for 10,000 screenshots, then $0.036 per additional screenshot. Desktop & Mobile was $599 per month billed annually for 25,000 screenshots, then $0.048 per additional screenshot. BrowserStack also documents a free Percy plan with 5,000 monthly screenshots, unlimited users, and unlimited projects. These are vendor prices and allowances, not a quote; confirm the live selector for your configuration before buying.
For teams, estimate screenshots from rendered combinations first, then evaluate how many parallel tests you need to meet your completion-time target. A team member is not the same thing as a parallel test. The available Percy sources do not establish a universal team-seat price or exact team-specific parallel allocation.
Pricing at a glance
| Percy plan shown | Price and billing | Included screenshots | Overage shown |
|---|---|---|---|
| Free | Free | 5,000 per month | Paid plan details apply after selecting a plan; check current terms |
| Percy Desktop | $199/month, billed annually | 10,000 per month | $0.036 per additional screenshot |
| Percy Desktop & Mobile | $599/month, billed annually | 25,000 per month | $0.048 per additional screenshot |
The paid prices and volume figures above were displayed on BrowserStack’s pricing page on October 3, 2026. The page offers selectors for volume and configuration, and the captured content did not expose a complete matrix for every team size or parallel allocation. Treat these figures as a starting point and verify your selected configuration directly in the BrowserStack pricing selector. Percy billing documentation explains the free plan and that paid plans have screenshot allowances with charges for usage beyond those units. Read BrowserStack’s Percy billing documentation.
How Percy counts screenshots
Percy counts a screenshot for an individual browser and responsive-width combination. A snapshot can contain several such screenshots, so the number of snapshots in the interface is not necessarily the billable screenshot count.
For example, two pages rendered across two browsers and three responsive widths produce:
2 pages × 2 browsers × 3 widths = 12 screenshotsFor planning, count the actual page or component renderings and multiply by every browser and width combination. Add mobile coverage only if your selected configuration and test matrix include those renderings. Include repeat runs where they consume screenshot units under your workflow, then compare the total with the monthly allowance.
Estimate a month of usage
- List each page or component your suite captures.
- Count browser and responsive-width combinations for each item.
- Multiply the item count by those combinations to estimate screenshot volume per run.
- Multiply by expected runs per billing month, including scheduled and pull-request runs.
- Compare the result with 5,000 free, 10,000 Desktop, or 25,000 Desktop & Mobile screenshots as applicable.
- Estimate overage only after confirming the selected plan and live rate; account for seasonal or release-driven spikes.
As a simple illustration, 800 page captures across 2 browsers and 3 widths would be 4,800 screenshots per run. Two such runs would be 9,600 screenshots, before any other captures. It would fit within the displayed 10,000 Desktop allowance only if those combinations are included in the plan’s coverage and no other work uses the same allowance.
What is a parallel test?
BrowserStack Support defines parallel tests as automated tests that can run simultaneously, with each test running on one browser-OS combination at a time. More parallel tests can reduce the time needed to complete a test suite. See BrowserStack Support’s parallel testing definition.
Parallel capacity affects elapsed test time; screenshot volume affects usage and possible overage. They are related planning concerns, but they are different quantities. Running the same suite with more concurrency does not, by itself, mean fewer browser-and-width renderings are needed.
The Percy pricing page describes parallel allocation in relation to screenshot usage and says higher allocation leads to faster tests. The captured pricing content did not show exact team-specific parallel quantities or a complete price for each allocation. Check the live selector or request a quote for the precise configuration.
What are the plans for multi-user teams?
Percy’s documented free plan includes unlimited users and unlimited projects. The cited public pricing information does not establish a general per-user charge or a complete set of team-specific paid prices for Percy. Ask BrowserStack to confirm user access, roles, organization setup, screenshot allowance, overage, and concurrency together for the plan you are considering.
Do not apply licensing rules for other BrowserStack products to Percy without confirmation. BrowserStack’s FAQ says Live and App Live require a license per team member, while Automate and App Automate include unlimited users but have plan-limited parallels. Those rules refer to those products, not Percy. See the BrowserStack FAQ and confirm Percy’s terms separately.
Choosing a plan for a team
| Decision | What to check |
|---|---|
| Desktop or mobile coverage | Whether your required browser and responsive-width matrix needs the Desktop & Mobile configuration |
| Monthly volume | Rendered combinations, repeat runs, and the included screenshot allowance |
| Overage exposure | Current per-screenshot rate and what happens when the allowance is exceeded |
| Suite completion time | Parallel allocation available for the plan and expected duration at that concurrency |
| Team access | Percy-specific user, role, and organization rules |
| Billing commitment | Annual billing terms and the current selected configuration price |
A useful buying request to BrowserStack should specify monthly screenshot estimates, the browser and width matrix, desired suite completion time, number of users, projects or teams, and whether mobile coverage is required. Ask for the exact included volume, overage rate, parallel allocation, user licensing, and billing commitment in the quote.
Monitor usage and avoid surprises
BrowserStack says Percy usage can be checked in the account’s Usage dashboard. The dashboard shows current billing-period consumption and may allow filtering by team or organization depending on account role and type. Compare actual usage with your estimate during the billing period, especially after changing browser coverage or adding responsive widths.
- Keep a record of the render matrix so a change in screenshot counts is explainable.
- Review usage after adding a browser, width, or project to CI.
- Check the selected configuration and billing period before interpreting an overage.
- Ask for the current quote when team size or parallel allocation is a deciding factor.
Performance, reliability, and cost considerations
More parallel tests can shorten suite completion time, but the exact improvement depends on the suite and available allocation; no fixed speedup follows from the public figures here. Parallelism is useful when test duration is costly, but it does not replace estimating billable screenshot combinations.
For reliability, use the Percy usage view to reconcile actual consumption with the expected matrix. Plan for high-volume release periods and changes to responsive coverage. The public material cited here does not specify a universal overage cap, throttling behavior, or team-specific concurrency quantity, so confirm those terms for your account instead of assuming them.
Cost planning should include the annual billing commitment shown for the paid prices, expected screenshot overage, and any configuration selected for mobile or parallel allocation. The listed $0.036 and $0.048 rates make each extra screenshot a predictable unit in the captured pricing, but monthly cost still depends on actual usage and the current vendor configuration.
Common pricing and planning mistakes
Counting snapshots instead of screenshots
Cause: A snapshot can bundle several browser and responsive-width renderings. Fix: Calculate the product of pages or components, browsers, and widths.
Assuming more parallels reduce screenshot charges
Cause: Concurrency controls simultaneous work and suite duration, while screenshot usage counts rendered combinations. Fix: Estimate volume and completion time independently.
Assuming team-seat rules from another BrowserStack product apply to Percy
Cause: BrowserStack’s product FAQ describes different licensing rules for Live and Automate products. Fix: Ask for Percy-specific user and organization terms.
Using a captured price as a guaranteed team quote
Cause: The pricing page uses configuration selectors, and the captured page did not show all team and parallel combinations. Fix: Recheck the live selector and confirm the chosen configuration with BrowserStack.
Forgetting responsive widths or mobile coverage
Cause: Each browser and width combination counts as an individual screenshot. Fix: Include the full matrix in the estimate and verify which configuration covers it.
ScreenshotNeo: an alternative to try first
If the goal is to capture clean website screenshots through an API, ScreenshotNeo is the alternative to try first: cookie banners, newsletter popups, and chat widgets are removed before capture, and only clean shots are billed. It is a website screenshot API and MCP server from ScreenshotNeo. It complements Percy’s visual testing workflow rather than changing Percy’s pricing or screenshot accounting.
One GET request returns an image or PDF. See the ScreenshotNeo API documentation for parameters and options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
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}`);ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed; its MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. Sign up for ScreenshotNeo’s free 1,000 screenshots per month, with no card required.
FAQ
Does Percy’s free plan support multiple users?
BrowserStack’s Percy billing documentation lists unlimited users and unlimited projects on the free plan.
Does Desktop & Mobile mean unlimited mobile screenshots?
No. The displayed plan has a monthly screenshot allowance; browser and responsive-width combinations contribute to screenshot usage.
Can I calculate the exact runtime from the parallel count?
Not from the public definition alone. The number indicates simultaneous tests, but actual suite duration depends on the test workload and configuration.
Are the listed paid prices current for every team?
They are the public prices captured on October 3, 2026 for the named displayed plans, billed annually. Confirm the current selector or obtain a quote for team and parallel details.
