Website Capture runs and results

During a Website Capture run, each URL moves through its own states. This page explains the states, single-page cancel and retry, stopping the batch, and reviewing the results.

Cancel and retry one page

Every row shows its own state while the rest of the batch continues.

Row states

State	Meaning
Capture pending	Waiting for a free browser slot
Capturing	The page is loading or being captured
Cancel requested	Cancel was selected and the page is shutting down
Capture cancelled	The page stopped without a screenshot
Retry pending	A failed or cancelled page is queued again
Capture complete	The screenshot was saved
Capture failed	The page did not produce a screenshot

A failed row can show a specific error message in place of Capture failed.

The number of pages in Capturing at one time is limited by Concurrent browsers (1 to 10, default 4).

Cancel or retry a row

1. Cancel a page

   Select Cancel on a row that is pending or capturing. The other rows keep running.

2. Retry a page

   Select Retry on a failed or cancelled row once the control appears. The row goes back to Retry pending without waiting for the rest of the batch.

Stop the batch

Select Stop Capture to end all remaining work. Screenshots that already finished are kept. The URL list, row options and Concurrent browsers unlock after the run settles.

Review results

Finished screenshots appear in the screenshot pane and in a session in Capture History.

• Select frames and use the export buttons, such as ZIP, Images or PDF.
• Select Create Document to build a Document from every frame in the session.

Session status	When it appears
Partial	Some URLs finished and others failed
Cancelled	The batch was stopped; finished screenshots remain available

See Export formats for format details.

Common causes of failure

Cause	What to change before retrying
The URL is invalid or not HTTP or HTTPS	Correct the URL in the row
The page did not reach the wait condition in time	Switch Wait until to Load or DOM content loaded, or add a short Delay
The site blocked automated browsing or did not render	Turn off Block ads or Block trackers for that row, or try again later
The Mac ran short of memory	Lower Concurrent browsers

Next: Capture History.