Is Browserless Affordable for an Indian Agency Taking Bulk Website Screenshots?
Browserless cost depends on browser time, concurrency, proxies, and your workload. Learn how an Indian agency can estimate the bill before choosing a plan.
Short answer: Browserless can be affordable for an Indian agency taking bulk website screenshots when sessions are short, monthly usage fits the unit allowance, and plan concurrency can finish batches on time. It can cost more than a simple per-screenshot estimate suggests: browser time is billed in 30-second units rounded up, idle sessions still consume units, and proxy traffic or successful CAPTCHA solves use additional units. Without your session durations, monthly volume, and peak concurrency, there is no reliable universal verdict.
The published prices below were checked on October 3, 2026. Paid prices are displayed as billed annually; they should not be read as verified month-to-month prices. Confirm current terms, concurrency entitlements, and billing options with Browserless before purchasing.
1. Browserless pricing and plan limits
| Plan | Displayed price | Included units/month | Listed concurrency | Overage | Maximum session |
|---|---|---|---|---|---|
| Free | $0/month | 1,000 | 2 | Not listed | 2 minutes |
| Prototyping | $25/month, billed annually | 20,000 | 10 + 5 | $0.0020/unit | 15 minutes |
| Starter | $140/month, billed annually | 180,000 | 40 + 10 | $0.0017/unit | 30 minutes |
| Scale | $350/month, billed annually | 500,000 | 100 + 20 | $0.0015/unit | 60 minutes |
| Enterprise | Custom | Millions of units consumed, per vendor description | Hundreds or thousands, per vendor description | Custom terms | Confirm with vendor |
The pricing page uses a “+” in its concurrency figures. The exact entitlement represented by that notation is not clear from the published figures alone, so confirm it with Browserless when evaluating a plan. The vendor also shows a monthly/yearly billing selector; the figures above are the annual-billed rates presented in the research. Browserless pricing.
2. How Browserless units translate to screenshot jobs
A unit represents up to 30 seconds of browser connection time. Browserless rounds partial units up: a 31-second connection consumes two units. Browser time continues to count while a session is idle, so a page left open while your code waits can consume units too. Browserless documentation on unit consumption.
Estimate session units separately for each new browser connection:
units_per_session = ceil(connection_seconds / 30)
monthly_session_units = sum(units_per_session for each connection)Then add applicable proxy and CAPTCHA usage. The published pricing information says residential proxy traffic uses 6 units/MB, datacenter proxy traffic uses 2 units/MB, and a successful CAPTCHA solve uses 10 units. Check the current pricing page for terms before relying on these rates.
| Connection duration | Units consumed |
|---|---|
| 1–30 seconds | 1 |
| 31–60 seconds | 2 |
| 61–90 seconds | 3 |
| 45 seconds | 2 |
For example, 20,000 units could cover at most 10,000 sessions of 30 seconds each before proxy or CAPTCHA use and other session activity. That is a unit calculation, not a promise of 10,000 completed screenshots: real page loads, waits, scrolling, and browser work can extend each session.
3. Estimate your agency’s monthly bill
- Count browser connections. Count each new connection used for a capture workflow, rather than assuming every URL maps to one unit.
- Measure durations. Record typical and long-tail session time, including navigation, waits, full-page scrolling, and cleanup.
- Round each session up. Convert each duration to 30-second blocks individually, then sum the units.
- Add special usage. Include proxy bandwidth and successful CAPTCHA solves where applicable.
- Compare usage and concurrency separately. The monthly quota controls included activity; concurrency controls how many sessions can run at once and affects batch completion time.
- Model overages and billing terms. Check whether your estimate exceeds the allowance, and account for the annual commitment or billing cycle you actually choose.
- Check local accounting treatment. Confirm payment conversion costs and transaction-specific tax treatment with your finance adviser.
A useful worksheet is:
monthly_units = sum(ceil(session_seconds / 30) for each connection)
+ proxy_units
+ successful_captcha_unitsFor a batch of jobs, also estimate the peak simultaneous sessions. A workload can fit the monthly allowance but still take too long if its required parallelism exceeds the plan’s concurrency. Browserless documents independent parallel REST screenshot requests and notes that the plan must support the desired concurrency. The available sources do not establish a universal requests-per-second rate or page-specific capture time.
4. What the prices mean in Indian rupees
As a dated illustration only, the RBI page surfaced in the research lists ₹95.3129 per US dollar at 1:00 p.m. on July 10, 2026, sourced from FBIL. Applying that rate gives approximate conversions of $25 = ₹2,383, $140 = ₹13,344, and $350 = ₹33,360. These are calculations using a July 10 rate, not October 3 exchange quotes. Your card or bank may use a different conversion rate and add fees. RBI reference page.
Do not infer an agency’s GST liability, registration requirements, or input-tax-credit treatment from the subscription price. The GST Portal’s GSTR-5A FAQ describes OIDAR supplies by non-resident providers and reverse-charge treatment for supplies to registered persons in the context it covers; it does not determine Browserless’s classification or your agency’s specific treatment. Confirm the transaction with a qualified tax or accounting adviser. GST Portal.
5. Screenshot API capabilities and constraints
Browserless’s REST /screenshot endpoint accepts a URL or raw HTML and can return PNG, JPEG, or WebP. Documented controls include full-page screenshots, viewport and device scale factor, image quality, clipping, selector-based element capture, wait behavior, request rejection, and scrolling to trigger lazy-loaded content before a full-page capture. The REST interface lets an agency request captures without managing a local browser library. Browserless screenshot API documentation.
Some sites block automation or return incomplete results. Browserless notes that a blank image, CAPTCHA page, 403/access-denied response, or missing content can indicate blocking. Its documentation points to the /unblock route and residential proxies for some cases, but access is not guaranteed; proxy usage can also add units. Validate the actual target-site mix and include any added usage in your estimate.
6. When Browserless is likely to be affordable
- Potentially a fit: your jobs are usually short, do not need substantial proxy or CAPTCHA usage, and your measured monthly units and required concurrency fit a published plan.
- Needs careful modeling: page loads vary widely, the workflow waits for network idle or long delays, you capture long pages, or a significant portion of the target sites blocks automation.
- Could be a poor fit: sessions often exceed the allowance, concurrency is too low for your batch deadline, or overages and annual billing do not match your budget and cash flow.
For a trial or low-volume evaluation, the free allowance can help measure target-site behavior and session duration. For production, use observed usage from representative pages rather than URL count alone. If usage is steady beyond published caps, request an Enterprise quote and confirm the precise concurrency terms.
7. Browserless versus self-hosting
A self-hosted deployment may change the vendor bill, but the research does not provide a like-for-like cost comparison. Include deployment, patching, monitoring, capacity planning, and support effort in the total cost; compare those costs with the managed service and the staff time your agency can actually allocate. Browserless documents Docker/Kubernetes self-hosting and private deployments, but no specific infrastructure cost or performance benchmark is established by the available sources. Browserless deployment documentation.
8. Or skip the browser setup
For a website screenshot API that takes one GET request, ScreenshotNeo is the alternative to try first: cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed; an 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. 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.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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));ScreenshotNeo also supports full-page capture with lazy images loaded, selector capture, dark mode, device presets and custom viewports, retina scale, PDF settings, HTML/CSS-to-image, custom CSS and JavaScript, pre-capture clicks, selector hiding, wait conditions, request and resource blocking, custom headers/cookies/user agent/Authorization, timezone and geolocation, transparent backgrounds, resizing, TTL caching, signed image links, async jobs with signed webhooks, batches of up to 100 URLs per call, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work to ease migration. These features are available on every plan. ScreenshotNeo is a website screenshot API and MCP server by Yorker Media. Visit ScreenshotNeo to review the service. Sign up for 1,000 free screenshots a month with no card.
9. Troubleshooting Browserless cost and capture issues
| Symptom | Likely cause | What to check |
|---|---|---|
| Usage is higher than screenshot count | Units measure browser connection time, not returned image count; sessions can round up and idle time counts. | Log connection start/end times, close sessions promptly, and set timeouts. |
| Batch completes slowly despite quota remaining | Plan concurrency may be below the number of simultaneous jobs requested. | Compare peak parallel sessions with the plan’s confirmed concurrency; use bounded parallelism. |
| Screenshot is blank or shows a CAPTCHA/403 | The target may be blocking browser automation or returning an access-denied page. | Inspect the returned image and target response. Evaluate documented unblock/proxy options for those targets and include their usage cost. |
| Lazy content is missing | Images or page sections may load only after scrolling or waiting. | Use the documented full-page scrolling and wait controls, then account for the added session time. |
| Overage appears unexpectedly | Rounded session units, proxies, CAPTCHA solves, or concurrent work may have pushed usage past the allowance. | Reconcile usage by connection, proxy MB, CAPTCHA solve, and billing period; confirm current overage terms. |
| INR debit differs from the illustration | The reference conversion is dated and the payment provider may apply another rate or fees. | Check the posted card/bank conversion and fees for the transaction date. |
| Tax treatment is unclear | Pricing information alone does not determine your agency’s transaction-specific obligations. | Ask your accountant to review the provider, registration status, invoice, and transaction context. |
10. Reliability, performance, and cost checklist
- Measure representative pages, including slow and long-tail cases; do not treat a vendor unit as a fixed screenshot count.
- Set explicit waits and timeouts, close sessions when finished, and avoid waiting longer than the capture requires.
- Use bounded parallel requests and confirm plan concurrency before promising a batch completion time.
- Test sites that use bot checks, consent flows, or heavy lazy loading. No plan guarantees successful capture of every site.
- Track monthly units and proxy/CAPTCHA consumption against the allowance and overage rate.
- Refresh pricing, billing cycle, and concurrency details at purchase time; calculate local currency using the actual payment date and provider terms.
- Compare managed-service charges with the full operating cost of self-hosting, including staff time.
11. FAQ
How many screenshots does 20,000 Browserless units buy?
There is no fixed conversion. At most, it covers 10,000 sessions of exactly one 30-second unit each before additional usage; longer sessions and proxy or CAPTCHA use reduce that count.
Which Browserless plan should an Indian agency choose?
Choose from measured monthly units and required concurrency, then account for billing commitment, overages, currency conversion, and your tax advice. The information available here cannot determine a plan without the agency’s workload.
Does Browserless guarantee that every target website can be captured?
No. A site can block automation or return a CAPTCHA, blank page, 403, or incomplete content. Test your target sites and validate any unblock or proxy approach.
Are the INR amounts the current Browserless prices in India?
No. They are illustrative conversions using a July 10, 2026 reference rate and annual-billed USD prices reported for October 3, 2026. Actual payment conversion and fees can differ.
Is self-hosting automatically cheaper?
The available research does not establish that. Include infrastructure and ongoing engineering operations when comparing it with a managed plan.
