BrowserStack Screenshots Concurrency Limits and Queue Behavior

Direct answer: BrowserStack Support documents a limit of 25 browser/device combinations per Screenshots session. That is a per-session combinations limit. The cited Screenshots documentation does not specify an account-wide concurrent-session limit or describe what happens to excess Screenshots requests in a queue. Do not treat Automate queue rules as Screenshots policy.

What the Screenshots limit means

BrowserStack’s Screenshots FAQ answers “Is there a limit of browsers on generating screenshots?” with a limit of 25 browser/device combinations per session. The wording concerns combinations in a session; it does not establish how many screenshot sessions an account can run at once.

For example, if you are preparing one Screenshots session, plan for no more than 25 browser/device combinations in that session. If you need more coverage, divide the combinations across sessions and confirm the relevant behavior with BrowserStack Support. The available source does not explain whether multiple sessions run concurrently, wait, or are rejected.

BrowserStack Support: Screenshots browser limit

What BrowserStack has documented about queues elsewhere

BrowserStack documents queueing for other products. Those details are useful only when you are using the named product; they do not fill the documentation gap for Screenshots.

Product or area	Documented behavior	What not to infer
Screenshots	Up to 25 browser/device combinations per session.	No documented account-wide concurrent-session allowance, queue size, overflow behavior, or queue timeout in the cited FAQ.
Automate	Tests submitted beyond purchased parallel-test capacity can wait for available slots. BrowserStack documents queue allowances in relation to purchased parallels and a default 15-minute wait limit.	Do not apply these Automate rules to Screenshots.
Automate self-hosted Grid	New Grids have concurrency set to 50 by default. Grid concurrency and queue timeout can be configured.	This is a self-hosted Grid setting, not the Screenshots session cap.
App Automate	Its plan API exposes maximum allowed parallel sessions, running sessions, queued sessions, and maximum queue allowance.	This is App Automate monitoring, not a universal Screenshots capacity API.

Sources: Automate queueing, Automate parallel tests, self-hosted Grid configuration, and App Automate plan API.

How to diagnose waiting or capacity problems

Identify the product. Check whether the request uses Screenshots, Automate, App Automate, or a self-hosted Grid. Similar browser terminology does not mean the products share limits.
Identify the unit. For Screenshots, count browser/device combinations in each session. For Automate products, inspect parallel test or session capacity.
Check the relevant capacity surface. For App Automate, use its plan and current usage information to inspect allowed, running, and queued sessions. For Automate, check the account’s purchased parallel capacity and product documentation.
For a Screenshots queue question, ask Support specifically. Ask whether the 25-combination session cap is related to parallel requests, queue capacity, or account-level concurrency, and what happens to requests above any such limit.

BrowserStack lists hitting the parallel limit, high-demand browser/OS combinations, and region or pool constraints as possible reasons Automate work waits. It recommends checking parallel capacity and broadening selections where practical. These are Automate operational notes, not confirmed causes of Screenshots delays. Automate queue and performance guidance.

Practical planning and reliability

Keep each Screenshots session at or below the documented 25-combination limit.
Track session composition separately from concurrent sessions; the FAQ only establishes the former.
If splitting a large browser matrix, preserve the same target URL and capture settings across sessions so results remain comparable.
Do not promise a queue wait time or assume excess Screenshots work will be queued. The supplied Screenshots source does not document either behavior.
For automated test queues, use the capacity, queue, and timeout rules for the exact Automate product and plan in use.

No Screenshots-specific queue duration, concurrency figure, or overflow behavior is established by the sources cited here. If those details affect a release or batch schedule, get confirmation from BrowserStack Support rather than estimating from Automate figures.

Or skip the browser setup

If your goal is to capture website screenshots rather than test a BrowserStack browser matrix, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Its parameter names also work with those used by other screenshot APIs, which can make switching easier. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

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)

Node.js:

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', new Uint8Array(await res.arrayBuffer()));

Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Response headers identify the page verdict and billing status.
An MCP server gives AI agents tools to take screenshots, inspect page information, and capture PDFs.
The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Common questions

Is 25 the maximum number of simultaneous Screenshots jobs?

The source says 25 browser/device combinations per session. It does not call that a simultaneous-job limit.

Does BrowserStack Screenshots queue requests above the limit?

The cited Screenshots FAQ does not describe queue behavior. Automate has separate queue documentation, which should not be assumed to govern Screenshots.

Where can I see queued BrowserStack sessions?

The App Automate plan API documents running and queued session fields for App Automate. It is not a general Screenshots monitoring endpoint.

Can I change the Screenshots limit?

The cited FAQ does not say whether the per-session cap can be changed. Contact BrowserStack Support for account-specific guidance.