Batch Screenshot

A batch screenshot run captures many images from a list of inputs in one job, instead of one capture at a time. The inputs are usually URLs, but they can also be pages, screens or app states.

A batch tool applies shared settings to every item: viewport size, capture area, wait condition, file format and quality. It tracks a status for each item, reports failures, and writes the results to one folder or archive with predictable file names.

Running several browsers in parallel shortens the run. More parallel browsers also use more memory and network bandwidth, and some sites slow down or block many requests from one address.

Batch vs single capture

A single capture is quick for one page. Each capture is a separate set of manual steps, so settings drift: a different window size, a missed scroll, another file name pattern. A batch run applies the same settings to every item and produces a set that can be compared item by item.

Where batch screenshots are used

• Release checks across 40 landing pages at desktop and mobile sizes.
• Archiving the public pages of a site before a redesign.
• Building image sets for documentation or design review.
• Recording pages for compliance or support records.

How batch capture works

1. Collect the input list, one URL per line.
2. Choose shared settings: device size, viewport or full page, wait condition, format.
3. Load several pages in parallel and capture each one when the wait condition is met.
4. Record a status per item and retry or report failures.

In Temposhot, Website Capture follows these steps. Paste a list with Bulk insert, choose a Device (Desktop 1920×1080, Tablet 768×1024 or Mobile 390×844) and an Area, then select Start Capture. Concurrent browsers runs 1 to 10 browsers, with 4 as the default.

Common mistakes with batch screenshots

• Capturing at Load on pages that keep loading images afterwards. Try Network idle or a delay.
• Setting parallelism too high for a slow site, which causes timeouts.
• Ignoring failed rows. A session with failures is marked Partial in Temposhot.
• Leaving cookie banners on every image. Temposhot has Reject banners, Accept minimal and Hide only options (best effort).

Taking the same screenshots again and again?

Save the URL list once and rerun it in website screenshot automation whenever the pages change.

Common questions

How many URLs can one run hold?

Temposhot does not publish a fixed limit. Very long lists take longer and use more disk space.

Do batch captures run in the cloud?

Not in Temposhot. It loads each URL in managed local browsers on your Mac.

Sources

• Batch processing (Wikipedia)

Related resources

• Website Capture quick start: set up a first run.
• Runs and results: row states and retries.
• Batch capture multiple web pages on Mac: a worked example.