Browserless Screenshot API Pricing: How Much Do Screenshots Cost?
Browserless charges for browser time in 30-second units, not per screenshot. See current plan allowances, overage rates and how to estimate your usage.
Browserless does not publish a fixed price per screenshot. Its cloud plans meter browser-session time in units: one unit for each 30 seconds or partial increment. Your screenshot cost depends on how long each browser session stays open, your plan allowance and overage rate, and any proxy traffic or successful CAPTCHA solves. A 31-second session uses two units; a 45-second session also uses two.
The prices below are the rates currently displayed on Browserless’s pricing page, accessed October 3, 2026. Paid rates are shown with annual billing; confirm the billing cycle and checkout total before choosing a plan. Browserless pricing.
Current Browserless cloud plan prices
| Plan | Displayed monthly price | Included units per month | Listed overage rate |
|---|---|---|---|
| Free | $0 | 1,000 | Not listed in the pricing information summarized here |
| Prototyping | $25/month, billed annually | 20,000 | $0.0020/unit |
| Starter | $140/month, billed annually | 180,000 | $0.0017/unit |
| Scale | $350/month, billed annually | 500,000 | $0.0015/unit |
| Enterprise | Custom | Custom | Custom |
These are plan prices and unit rates, not per-image prices. Browserless publishes no standard screenshot duration from which to derive a universal price per capture. Check the current pricing page for the selected billing cycle and any changes before budgeting.
How Browserless meters screenshot requests
Browser time is charged at one unit per 30 seconds per browser connection, rounding any partial interval up. The clock runs while the browser session remains open, including idle time. The model applies across Browserless REST APIs, BrowserQL and BaaS. See Browserless’s unit consumption documentation.
| Session time | Browser-time units |
|---|---|
| Up to 30 seconds | 1 |
| 31 to 60 seconds | 2 |
| 61 to 90 seconds | 3 |
| 91 to 120 seconds | 4 |
A screenshot request may also incur add-on units when you use Browserless’s built-in proxy or CAPTCHA solving:
- Residential proxy traffic: 6 units per MB.
- Datacenter proxy traffic: 2 units per MB.
- Successful CAPTCHA solve: 10 units per solve. A failed attempt that does not clear the challenge is not charged for the solve, according to the documentation.
Third-party proxies passed through a --proxy-server launch argument do not incur Browserless proxy units. Their provider may charge separately. If a capture fails after the browser starts, browser time already used and proxy bandwidth already transferred can still consume units. Requests rejected before a browser starts consume no units.
Estimate your monthly screenshot usage
Use measured session durations from your own workload when possible. Do not assume that every page takes the same time: redirects, client-side rendering, waits, slow resources and proxy use can change session length.
- Record how long a browser connection stays open for representative captures, including setup, navigation, waits and cleanup.
- Round each session duration up to a 30-second increment. For example, 45 seconds is 2 browser-time units.
- Multiply the rounded units per capture by your expected monthly capture count.
- Add built-in proxy traffic at the applicable per-MB unit rate and 10 units for each successful CAPTCHA solve.
- Compare the resulting monthly units with the plan allowance, then account for the listed overage rate if you expect to exceed it.
Formula: monthly units = sum of rounded-up browser-session units + residential proxy MB × 6 + datacenter proxy MB × 2 + successful CAPTCHA solves × 10.
This formula estimates metered units, not a guaranteed dollar bill. Apply the current plan’s allowance and overage terms, and check how the account handles any usage beyond the allowance. The summarized Free-plan information does not provide an overage rate.
What the Screenshot API includes
The current Browserless Screenshot REST API is a POST endpoint at /screenshot, authenticated with an API token. It can navigate to a URL or render inline HTML and return PNG, JPEG or WebP. Documented settings include full-page capture, output type and quality, viewport and clipping, device scale factor, and element-specific screenshots. These are capture options; the cited pricing pages do not list them as separate price tiers. See the current Screenshot API documentation.
Capture shape can affect how long a browser session takes in practice, but Browserless’s published model charges browser time and applicable add-ons, not a separate listed fee for image dimensions. Larger or full-page output should therefore be measured with your own pages rather than assigned an invented surcharge.
Choose a plan for your workload
Compare the monthly price with included units and the overage rate, then check the operational limits that matter to your capture job. Browserless’s pricing page also lists plan features such as concurrency, maximum session duration, log retention and support. Proxy requirements can increase unit demand, so include them in the estimate.
- Light or exploratory usage: the Free plan lists 1,000 units per month. Confirm current limits and what happens when you reach the allowance.
- Growing usage: compare Prototyping, Starter and Scale by total expected units and the cost of any overage, not by screenshot count alone.
- Enterprise needs: pricing is custom. Request a quote for the deployment and operational requirements you need; do not extrapolate a price from public tiers.
Version and billing cautions
Use the current REST API documentation for implementation details. Browserless marks its BaaS v1 screenshot page as deprecated and directs new users to updated BaaS v2 or BrowserQL documentation. The current Screenshot REST API is documented separately. See the legacy BaaS v1 page and deprecation notice.
Prices, allowances and billing-cycle displays can change. The figures in this guide reflect the official pricing information accessed October 3, 2026, and the paid prices shown on an annual-billing basis. Verify the live pricing page and selected billing cycle before committing to a plan.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. A single GET request returns an image or PDF, and its API accepts parameter names used by other screenshot APIs to make switching easier. Full code and options are in the ScreenshotNeo documentation.
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, newsletter popups and chat widgets before capture. Bot checks, blank pages and failed loads are never billed. Its MCP server lets AI agents use screenshot tools. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up free for 1,000 screenshots a month, with no card required.
Troubleshooting Browserless usage and billing
My screenshot cost more units than expected
Check the full browser-session duration, including idle time and time spent waiting for page readiness. A small increase past a 30-second boundary adds a whole unit. Also inspect built-in proxy usage and successful CAPTCHA solves.
A failed capture still used units
If the browser started, time consumed before failure and proxy traffic already transferred may be metered. A request rejected before browser startup consumes no units. Review session timing and the error stage against the unit billing rules.
My estimated per-screenshot price varies
There is no fixed published per-screenshot rate. Different pages and waits can yield different session lengths, and proxy or CAPTCHA usage adds units. Estimate with observed durations and add-ons, then apply the plan allowance and overage rate.
The docs show a different screenshot endpoint
You may be looking at the deprecated BaaS v1 page. Use the current Screenshot REST API documentation for current endpoint details.
FAQ
Does the /screenshot endpoint have its own fee?
The cited billing FAQ does not list a separate endpoint fee; cloud usage is described in browser-time units and applicable add-on units.
Are failed HTTP 5xx requests free?
It depends on whether a browser session started. Rejections before browser startup consume no units; work already performed in a started session can consume browser-time units and proxy units.
Does a full-page screenshot have a separate surcharge?
No separate full-page fee is listed in the cited pricing model. Browser session time and applicable add-ons remain the relevant meters.
Can I calculate an exact price from the number of images?
No. You need the session duration for your workload, applicable add-ons, plan allowance and overage terms to estimate cost.
Are Enterprise cloud prices public?
No. The listed Enterprise price and usage terms are custom.
