Website Screenshot API Pricing in India: Pay Per Capture or Monthly Plan?
Compare screenshot API plans for Indian teams, including INR pricing, overages, quotas, credit rules, and the questions to check before choosing.
Short answer: If your capture volume is steady and predictable, a monthly plan with enough included captures is usually the simplest way to budget. If volume varies, compare the plan’s overage cost—or the consequence of a hard cap—with your expected monthly usage. For Indian buyers, SnapshotAPI publishes INR plans with explicit per-capture overages, while ANEARST publishes INR credit plans with different credit weights for stills, PDFs, and video previews. “Pay per capture” can mean an overage after a monthly allowance; the sources here do not establish that pure pay-as-you-go pricing is universally available.
Prices and billing terms below are vendor-published and can change. Confirm the current checkout total, taxes, payment method, renewal behavior, and quota rules before purchase.
1. What “pay per capture” and “monthly plan” mean
Screenshot API pricing usually combines some or all of these pieces:
- Monthly fee: the fixed amount paid for a billing period.
- Included allowance: captures or credits bundled with that fee.
- Overage: a per-unit price once the allowance is used.
- Hard cap or throttle: requests stop or slow when the allowance is reached.
- Separate storage: retained images may have a distinct capacity limit.
So a monthly subscription can still charge per capture at the margin. Conversely, a plan without overage may be unsuitable for a production workflow if it rejects requests at quota. Compare the effective monthly bill and the service behavior at the limit, not just the headline price divided by the advertised quota.
2. India-relevant pricing: INR plans
SnapshotAPI
SnapshotAPI lists the following INR monthly plans and overages on its pricing page:
| Plan | Monthly price | Included screenshots | Overage per screenshot | Other listed details |
|---|---|---|---|---|
| Free | ₹0 | 10 | Not listed | 1 request/minute |
| Starter | ₹499 | 1,000 | ₹0.60 | 10 requests/minute; 7-day data retention |
| Professional | ₹999 | 5,000 | ₹0.25 | 60 requests/minute; 30-day retention; up to 3 API keys; webhooks and PDF generation listed |
| Business | ₹1,999 | 10,000 | ₹0.12 | 120 requests/minute; 90-day retention; 5 users; unlimited API keys and advanced analytics listed |
For a rough estimate, the vendor-published tiers imply an allowance cost of ₹0.499 per included screenshot on Starter, about ₹0.200 on Professional, and about ₹0.200 on Business before overages. This is not a like-for-like quality or feature comparison: it excludes taxes and any other checkout charges, and assumes the entire allowance is used. SnapshotAPI also describes a seven-day paid-plan trial, a 14-day money-back guarantee, plan changes, and annual billing with “2 months free.” Treat all of those as vendor terms and verify them at checkout. The pricing page checked here did not clearly settle GST treatment or payment methods. SnapshotAPI pricing.
ANEARST
ANEARST prices usage in successful credits, not a uniform “one screenshot equals one unit” measure:
| Plan | Price/month | Successful credits/month | MP4 scroll previews/month | Listed rate limit |
|---|---|---|---|---|
| Free | ₹0 | 150 | 8 | 10 requests/minute |
| Starter | ₹1,499 | 3,000 | 40 | 30 requests/minute |
| Pro | ₹4,499 | 15,000 | 150 | 60 requests/minute |
| Business | ₹11,499 | 50,000 | 400 | 120 requests/minute |
The pricing page says a successful still costs 1 credit, a successful PDF costs 2 credits, and a successful MP4 scroll preview costs 5 credits plus one monthly video slot. Failed captures consume neither credits nor video slots. It says Indian customers pay the listed INR catalog price through Razorpay, that listed Indian prices include GST, and that each charge covers one month without automatic renewal. It lists no yearly billing. Compare the credit mix your workflow will use, because 3,000 credits do not necessarily mean 3,000 PDFs or video previews. ANEARST pricing.
3. International plans: useful benchmarks, not India checkout totals
These providers publish USD prices. The figures are useful for comparing published plan structures, but they are not verified Indian checkout totals. Currency conversion, taxes, and bank or foreign-exchange charges may change what an Indian buyer pays.
| Provider | Published plans | Quota behavior / notes |
|---|---|---|
| Site-Shot | X-Lite $5/month for 2,000; Lite $15 for 10,000; Optimal $50 for 50,000; Professional $500 for 625,000 | Lists tiered per-capture overages from $0.0025 down to $0.0008. API and scheduled captures count toward allowance; stored-image capacity is separate. |
| ScreenURL | $9/month for 1,000; $29 for 5,000; free tier of 100/month; custom Enterprise | Says failed requests and cached responses do not count; no automatic overage; requests return HTTP 429 at the monthly limit. Stripe card processing is listed; Enterprise bank-transfer invoicing is listed. |
Site-Shot lists annual choices and says annual billing is limited to Enterprise for ScreenURL. Check current vendor pages for exact terms. APIScreenshot pricing text appeared in search results during research, but its pricing page could not be opened to confirm the details; it is omitted from the exact-price comparison. Sources: Site-Shot pricing and ScreenURL pricing.
4. Calculate the cost at your expected volume
- Estimate successful monthly captures. Count scheduled runs, retries, and each viewport or device variant separately. One URL captured at desktop and mobile may be two billable units.
- Map outputs to billing units. Check whether PDFs, video previews, cached responses, failed loads, and scheduled captures count differently.
- Apply the provider’s quota rule. For an overage plan, calculate
monthly fee + max(0, usage − allowance) × overage rate. For a hard cap, decide what it costs your workflow when requests stop. - Account for rate limits. A generous monthly quota does not help a burst job if the API limit is too low. Estimate how quickly your batch must finish.
- Compare storage separately. Fresh capture allowance and retained-image capacity are different things. Site-Shot says saved screenshot storage is separate from its capture allowance.
- Confirm the India payment total. Verify INR versus USD, GST inclusion or addition, payment method, renewal, and any bank or FX charges.
Example using SnapshotAPI’s listed Starter terms: 1,200 screenshots in a month would be ₹499 + (200 × ₹0.60) = ₹619 before any unconfirmed checkout adjustments. At 5,000 screenshots, the listed Professional base is ₹999, while Starter would be ₹499 + (4,000 × ₹0.60) = ₹2,899. This arithmetic uses the page’s published rates and assumes overage works exactly as listed; confirm billing behavior before relying on it.
Example using ANEARST: 1,000 successful stills use 1,000 credits, while 500 successful PDFs use 1,000 credits. A workload containing 100 MP4 previews uses 500 credits plus 100 video slots. Compare each plan against your expected output mix and the separate preview allowance.
5. Which pricing model fits your workload?
| Workload | What to prioritize | Pricing risk to check |
|---|---|---|
| Small prototype or occasional manual use | Free quota, setup time, and whether the free plan allows your required format | Low free limit or low request rate can make a trial impractical |
| Steady production volume | Included monthly quota and predictable unit cost | Overage rate and whether scheduled captures share the quota |
| Highly variable batch jobs | Overage flexibility, burst rate limit, and retry behavior | Hard caps can stop a batch; uncapped overage can exceed budget |
| PDF-heavy reporting | PDF availability, credit weight, page controls, and retention | Some vendors may count a PDF as multiple units |
| Visual monitoring | Scheduling, webhooks, history, and storage allowance | Stored images may use a separate capacity from monthly captures |
Choose a monthly plan when the included allowance covers normal usage and the next tier’s cost is clear. Prefer an overage plan when variable demand is worth paying for and excess usage is predictable. A hard cap can work for noncritical jobs that can wait until the quota resets; it is a poor fit for jobs that must complete on demand unless you have an upgrade or fallback path.
6. ScreenshotNeo: an alternative to compare first
ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. Its plans are in USD: Free includes 1,000 screenshots per month with no card; Starter is $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. These are published ScreenshotNeo plan facts, not INR checkout terms.
Its billing distinction is useful when evaluating a quota: only clean shots are billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Before capture, it can accept consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. It also offers an MCP server with take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.
To compare a workflow, make one GET request with a target URL. See the ScreenshotNeo API documentation for configuration and response details.
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}`);For an Indian budget, compare the USD plan against your actual checkout total and local bank charges, and verify how your workload maps to billable clean shots. ScreenshotNeo also supports full-page capture with lazy images loaded, element capture by CSS selector, dark mode, device presets and custom viewports, retina scale, PDF settings, HTML/CSS-to-image, custom CSS and JavaScript, click-before-capture, hidden selectors, selector/delay/network-idle waits, request and resource blocking, custom headers/cookies/user agent/Authorization, timezone and geolocation, transparent backgrounds, resizing, configurable caching, signed public image links, asynchronous jobs with signed webhooks, bulk capture of 100 URLs per call, usage API, and OpenAPI specification. Parameter names used by other screenshot APIs also work to make migration easier.
7. Reliability, speed, and budget controls
- Use realistic timeouts. A slow target site can fail even when your own client is healthy. Set a client timeout that accommodates the vendor’s documented request behavior and handle timeout retries with a limit.
- Retry selectively. Retry transient network errors and rate-limit responses with exponential backoff and jitter. Do not retry a permanent invalid URL or authentication error unchanged.
- Bound concurrency. Stay within the plan’s requests-per-minute limit, and avoid launching a large batch that triggers throttling.
- Track actual units. Log request volume, successful output type, credits or overage, and failed/cached responses where the provider exposes them. Alert before quota exhaustion.
- Protect spend. For plans with overage, set internal usage alerts and a maximum batch size. For hard caps, alert early enough to upgrade or defer nonurgent work.
- Reduce redundant captures. Use caching when a fresh render is not needed for every request. Confirm whether cache hits consume quota; policies differ by provider.
- Measure the whole job. Rate limits, page load wait conditions, output size, and retries affect completion time. Avoid treating the advertised monthly allowance as throughput capacity.
Pricing pages do not establish comparative uptime, capture quality, or latency. No provider load testing or checkout purchase is represented here; evaluate your own target sites and usage pattern before committing.
8. Troubleshooting pricing surprises
The monthly bill is higher than the plan price
Likely cause: usage exceeded the included quota, taxes or currency costs were added, or a different billing period was selected. Fix: inspect usage units and invoice line items, compare to the overage schedule, then confirm checkout currency, tax treatment, and annual/monthly selection.
Requests stop partway through a batch
Likely cause: a hard cap, rate limit, or concurrency restriction. ScreenURL says requests receive HTTP 429 at the monthly cap; other vendors may have different responses. Fix: distinguish quota exhaustion from rate limiting, slow the batch, and upgrade or wait for reset if the quota is spent.
Usage counts do not match the number of URLs
Likely cause: retries, device variants, scheduled captures, PDF/video credit weights, or separate slots. Fix: reconcile requests by output and billing unit. On ANEARST, a successful PDF is two credits and an MP4 preview is five credits plus a video slot.
A failed capture appears to affect quota
Likely cause: the provider’s policy may bill attempted requests or retries differently. Fix: check the exact failed-request and cache policy for your tier; do not assume one vendor’s exclusion applies to another.
The INR and USD options seem difficult to compare
Likely cause: international list prices omit your individual conversion, tax, and payment charges. Fix: compare final checkout totals and renewal behavior. The INR pages for SnapshotAPI and ANEARST are clearer about local catalog pricing than the international USD sources reviewed here, though SnapshotAPI’s tax and payment details were not confirmed.
9. Frequently asked questions
Is pay-per-capture always cheaper for low usage?
Not necessarily. A monthly minimum can be cheaper if its included quota is inexpensive and your usage approaches it. Compare the actual bill at your expected volume, including any minimum fee.
Are these Indian prices inclusive of GST?
ANEARST says its listed Indian INR prices include GST. SnapshotAPI’s checked pricing text did not clearly settle tax treatment. Confirm current checkout details for either service.
Does “1,000 screenshots” mean 1,000 outputs of every type?
No universal rule applies. Some vendors count credits or reserve separate slots for certain output types; check the plan’s billing unit and examples.
Can I treat USD list prices as the price I will pay in India?
No. The USD sources here do not establish India-specific tax, FX, or payment totals. Use checkout to compare the amount charged to your payment method.
Or skip the browser setup
With ScreenshotNeo, one API request returns an image or PDF. Cookie banners, newsletter popups, and chat widgets are removed before the shot; bot checks, blank pages, timeouts, failed loads, and cache hits are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpRead the API docs and sign up free for 1,000 screenshots a month with no card.
