The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To capture hundreds of URLs with a screenshot API, send a list of URLs to its batch or bulk endpoint, save the returned job or batch ID, then track completion and retrieve the results using that provider’s documented workflow. “One request” does not mean unlimited URLs or a single quota unit: check the batch maximum, plan eligibility, per-URL usage, rate limits, and concurrency first. If your list exceeds the documented maximum, divide it into batches.
What “one request” means for batch screenshots
A bulk request is one submission containing multiple capture jobs, not necessarily one synchronous response containing all finished images. Providers may return pending screenshot objects, a batch ID, or another job reference. You then poll for status or use an event mechanism such as a webhook or server-sent events (SSE), and retrieve the completed captures as that provider specifies.
Batch submission reduces the work of issuing individual capture requests, but it does not automatically reduce quota consumption or avoid request limits. Treat each URL as a possible unit of usage until the provider’s terms say otherwise. A batch can also share ordinary request or concurrency capacity with other jobs.
Free tools Windows power users keep installed
One-click scans. No signup required.
Compare the documented batch workflows
The providers below document different submission and completion patterns. Their published limits are provider-specific, not general limits for screenshot APIs.
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
| Provider | Submission and completion | Documented limits and operational notes |
|---|---|---|
| ScreenshotNeo | Bulk capture supports up to 100 URLs per call; asynchronous jobs and signed webhooks are available. See the ScreenshotNeo documentation. | Every feature is available on every plan. Check the current documentation for request details and account usage. |
| ScreenshotRun | POST /v1/screenshots/batch returns pending screenshot objects. Poll individual screenshots or configure webhooks. |
Up to 100 URLs per batch; Pro or above is required. Each URL counts toward monthly quota, and rate limits apply per URL. ScreenshotRun batch documentation. |
| Screenshot API | POST /api/v1/screenshot/batch returns a batch ID; track it by polling the batch endpoint or streaming updates with SSE. |
The reviewed documentation does not state a numeric batch maximum. It lists free-plan limits of 60 requests per minute and 500 screenshots per month; confirm current terms. Screenshot API documentation. |
| ScreenshotOne | POST /bulk accepts a URL list as HTML or Markdown. |
The reviewed documentation does not state a numeric batch maximum. Bulk calls share the regular screenshot request bucket, and the docs advise checking remaining concurrency before submitting a large queue. ScreenshotOne bulk screenshots documentation. |
ScreenshotNeo is a practical first choice when clean captures and predictable billing matter: it removes known consent banners, newsletter popups, and chat widgets before capture, and does not bill bot checks, blank pages, timeouts, failed loads, or cache hits. Its response includes page-verdict and billing headers. See ScreenshotNeo.
Plan the batch before submitting it
- Count and validate the URLs. Check that each URL is well-formed and points to the intended page. If a provider’s documented maximum is lower than your list size, split the list into batches. ScreenshotRun documents a maximum of 100 URLs per batch; the reviewed Screenshot API and ScreenshotOne pages do not specify a numeric maximum.
- Choose the capture settings. Determine whether all URLs can share options such as viewport, output format, or wait condition. Confirm that the selected provider supports the settings your pages require.
- Check eligibility and capacity. Verify any plan gate, remaining quota, per-URL rate limits, request bucket, and concurrency capacity. A large submission can still be constrained by ordinary API limits.
- Keep credentials private. Authenticate using the provider’s documented method. Store API keys in environment variables or a secrets manager, not in public source code or logs.
- Record identifiers and outcomes. Save the batch or job ID and a mapping from each URL to its capture status and output. That makes it possible to identify failures and retry only the affected URLs.
Submit and track the batch using the provider’s own flow
There is no universal batch request body or status endpoint. Follow the selected provider’s documentation rather than adapting another provider’s endpoint names. The documented patterns in the comparison table illustrate why: ScreenshotRun returns pending screenshot objects, Screenshot API returns a batch ID with polling or SSE tracking, and ScreenshotOne accepts a bulk URL list.
- Construct the request using the provider’s required method, endpoint, authentication, URL-list format, and shared capture options.
- Submit the batch and persist the response, including any batch ID or per-URL identifiers.
- Track progress through the documented polling endpoint, webhook, or event stream. Respect any polling interval or rate limits in the provider’s docs.
- Retrieve completed images or PDFs using the provider’s specified response or download mechanism.
- Record successful and failed items separately. Retry only failed captures, and follow the provider’s guidance on retry behavior and quota accounting.
Common errors and how to recover
- The list is too large: the provider rejects the submission or processes only part of it. Confirm its maximum and split the list into smaller batches; do not assume a provider without a stated maximum accepts an unlimited list.
- A URL fails validation or capture: identify the failing item, correct its scheme or address, and resubmit only that URL after checking the provider’s error details. A malformed item can disrupt the batch, depending on the API.
- The batch stays pending: continue tracking it through the documented status mechanism. Avoid creating duplicate batches while a valid job is still running.
- Rate-limit or capacity errors occur: reduce submission pace or batch size as appropriate, and check per-URL limits, shared request buckets, and concurrency. For ScreenshotOne, bulk work consumes the same one-minute request bucket as regular requests; ScreenshotRun applies rate limits per URL.
- Quota runs out sooner than expected: calculate usage per URL, not per batch request. ScreenshotRun explicitly counts each URL toward its monthly screenshot quota.
- Some outputs are missing: compare the submitted URL list with per-item completion statuses and retrieve successful items using the provider’s documented method. Retry selectively rather than resubmitting every successful capture.
- Authentication fails: verify that the key is active, sent in the correct location, and associated with a plan that permits the batch operation. Remove secrets from exposed logs or repositories and rotate compromised keys.
Performance, reliability, and cost considerations
Completion time and throughput
A single batch submission does not guarantee simultaneous completion. Capture times depend on the provider’s processing and concurrency rules as well as the target pages. Check concurrency before sending a large queue, and use the provider’s status mechanism instead of assuming that submission means every screenshot is ready.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- Includes Pre-Loaded 32GB EVO+ Micro SD Card (Class 10), USB MicroSD Card Reader
- CanaKit Premium High-Gloss Raspberry Pi 4 Case with Integrated Fan Mount, CanaKit Low Noise Bearing System Fan
- CanaKit 3.5A USB-C Raspberry Pi 4 Power Supply (US Plug) with Noise Filter, Set of Heat Sinks, Display Cable - 6 foot (Supports up to 4K60p)
- CanaKit USB-C PiSwitch (On/Off Power Switch for Raspberry Pi 4)
Quota and rate limits
Model a batch of N URLs as potentially consuming N screenshot units. ScreenshotRun explicitly uses that accounting and applies rate limits per URL. Screenshot API’s reviewed docs list 60 requests per minute and 500 screenshots per month for its free plan, but those are provider-specific figures; verify the current plan page before relying on them. ScreenshotOne’s bulk requests share the regular request bucket.
Retries and dependable results
Keep a durable record of the requested URLs, batch identifiers, individual statuses, and output locations. Retry only failed items, and use the provider’s documented retry and idempotency behavior. A webhook or event stream can reduce the need for frequent polling where supported, but it does not replace storing and reconciling per-URL outcomes.
Or skip the browser setup
ScreenshotNeo accepts a URL in one GET request and returns an image or PDF. The call below captures a page as WebP; for a large list, use its documented bulk capture option, which supports up to 100 URLs per call. See the API documentation for request parameters and response handling.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie banners, newsletter popups, and chat widgets 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. Sign up for free.
Frequently Asked Questions
Can one batch request capture more than 100 URLs?
It depends on the provider. ScreenshotRun and ScreenshotNeo document batches of up to 100 URLs per call; the reviewed Screenshot API and ScreenshotOne documentation does not state a numeric maximum.
Rank #4
- Broadcom BCM2711, quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1. 5GHz
- 2. 4 GHz and 5. 0 GHz IEEE 802. 11b/g/n/ac wireless LAN, Bluetooth 5. 0, BLE
- 2 × USB 3. 0 ports, 2 x USB 2. 0 Ports
- 2 × micro HDMI ports supproting up to 4Kp60 video resolution
- Micro SD card slot for loading operating system and data storage
Does a bulk request count as one screenshot against my quota?
Not necessarily. ScreenshotRun explicitly counts each URL in a batch as one screenshot toward monthly quota. Check the chosen provider’s usage rules.
Do all screenshot APIs return finished images immediately?
No. Batch workflows commonly run asynchronously and may return pending items or a job ID that you track before retrieving results.
Quick Recap
Best Value
- Includes Raspberry Pi 5 16GB with 2.4Ghz 64-bit quad-core CPU (16GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
