ScreenshotMachine Wait and Delay Options Explained for Dynamic Web Pages

Direct answer: ScreenshotMachine’s API delay parameter makes its capture engine wait a fixed amount of time before creating a screenshot. The documented API default is 200 ms, and its listed values run from 0 to 10,000 ms in specified increments. A delay can give late images or animations more time to appear, but it does not mean “wait until the page is ready.” The documentation does not describe it as waiting for a particular element, network idle, or an application event. ScreenshotMachine API documentation.

1. What the wait and delay options do

A screenshot service loads the target page and captures it. Dynamic pages may continue rendering after the initial document appears: JavaScript can fetch data, images can load later, and animations can progress. ScreenshotMachine’s API delay adds a fixed pause before the screenshot is created. It is a timer, not a readiness detector.

That distinction matters: increasing the delay may help when content appears after the default wait, but it cannot guarantee that an API request, client-side render, or third-party resource will finish within that time. The reviewed documentation does not specify framework-specific behavior or a universal delay for JavaScript-heavy sites.

2. ScreenshotMachine API delay values and default

The API guide lists these accepted delay values in milliseconds:

Delay	When to consider it
0 ms	Use when you want no additional fixed wait.
200 ms	Documented API default.
400, 600, 800, or 1,000 ms	Try a modest increase if content is consistently late.
2,000–10,000 ms	Longer waits; the guide suggests considering 2,000 ms or more for some full-page captures.

The complete documented list is 0, 200, 400, 600, 800, 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000. Use a listed value rather than assuming arbitrary values are accepted. ScreenshotMachine notes that long full-page captures may include more images or animations, so a longer delay may be worth considering for those pages. This is guidance to inspect the result, not a promise that a given value will work on every site.

3. API delay versus the online generator

Keep the two interfaces separate. ScreenshotMachine’s API guide gives a 200 ms default and expresses the parameter in milliseconds. Its online generator describes the delay control in seconds and states a two-second default. These are statements about different interfaces; do not use the generator’s default as the API default. ScreenshotMachine online generator.

4. How to choose a delay for a dynamic page

1. Start with the API default of 200 ms if you have no evidence that the page needs more time.
2. Inspect the screenshot for the specific missing content: for example, an image, an animation frame, or data rendered after a request.
3. If it appears later in a normal browser, increase the delay to another documented value and capture again. Change one setting at a time so you can see whether the longer timer affects the result.
4. For a long full-page capture, consider the guide’s example of 2000 ms or more, then inspect the output across the relevant page sections.
5. If content still does not appear at the maximum listed delay, investigate whether the site requires interaction, authentication, a particular viewport, or a resource that fails in the capture environment. A longer fixed timer cannot repair those conditions by itself.

There is no source-backed “best delay” for all pages. The right choice depends on the target page’s behavior, and should be confirmed by inspecting that page’s output.

5. Related capture options: click, hide, and selector

ScreenshotMachine also documents options that affect interaction or capture scope. They solve different problems from a readiness event:

Option	Purpose	What it does not establish
click	Click a page element before capture, which can be useful when a page needs an interaction.	The documentation does not say this waits for the resulting content to finish loading.
hide	Hide matching elements in the capture.	It does not make other content load sooner.
selector	Capture a single DOM element.	It does not document waiting for that element or its contents to become ready.

Use these options for their documented purpose. If an interaction triggers asynchronous content, a fixed delay may still be relevant, but neither the interaction nor selecting an element should be treated as a documented wait-until-ready condition. Refer to the vendor’s API guide for exact parameter syntax and constraints.

6. Common problems and fixes

Symptom	Likely explanation	What to try
Dynamic text or an image is missing	The content appeared after the capture, or did not load in the capture environment.	Try a higher documented delay and inspect the result. If it remains missing at longer waits, check the page’s own loading conditions rather than continuing to increase the timer.
A full-page image is incomplete	Some content lower on a long page may load later; the guide specifically calls out images and animations as reasons to consider a longer delay.	Try 2000 ms or more from the accepted list and inspect the whole capture.
The requested delay is rejected or has no expected effect	The value may not be among the API’s documented choices, or the request may be using the generator’s seconds-based control as if it were the API parameter.	Use an API value from the documented list, in milliseconds, and keep the generator’s seconds-based UI distinct.
A click happens but the resulting content is absent	click is an interaction option, not a documented guarantee that subsequent asynchronous work has finished.	Check whether the interaction is correct, then try a suitable fixed delay and inspect the capture.
The selected element is absent or incomplete	selector narrows the capture to a DOM element; it does not document waiting for that element’s content.	Verify the selector against the page and consider whether the content is rendered later. Use delay as a timer, not as a selector wait.

7. Performance, reliability, and cost considerations

A longer fixed delay necessarily asks the capture process to wait longer before creating the image. Use the shortest documented value that yields the content you need on the target page. For many URLs, even small per-capture waits add up to a slower workflow.

Reliability comes from treating each delay as page-specific configuration and checking representative outputs. A fixed timer cannot promise that unstable or failing third-party requests will complete, and the reviewed documentation provides no universal timing guarantee or independent performance measurements.

ScreenshotMachine’s pricing and fresh-capture allowances can change. Check its current official pricing page before estimating costs. Its pricing page says cached screenshots can be loaded without billing; confirm the current terms there. The research reviewed no independent cost benchmark.

8. Or skip the browser setup

If you need screenshots without managing capture-browser timing yourself, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF; its options include waiting for a selector, a delay, or network idle. 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.webp

import 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}`);

ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads 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.

Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

9. FAQ

Does ScreenshotMachine delay wait until JavaScript finishes?

The reviewed API documentation describes a fixed timer before capture. It does not document waiting for JavaScript completion or an application-specific readiness signal.

Should I set delay to 2 seconds?

Two seconds is an example the API guide suggests considering for some full-page captures, and the generator UI states a two-second default. The API default is 200 ms. Choose based on the particular page and inspect the result.

Can I use delay with click or selector?

The options address different tasks: click interacts with an element, selector captures an element, and delay adds a fixed wait. The documentation does not say click or selector guarantees content readiness.

What is the maximum documented API delay?

The listed maximum is 10,000 ms (10 seconds).

Sources

• ScreenshotMachine API documentation — delay values, API default, full-page guidance, and click, hide, and selector options.
• ScreenshotMachine online generator — generator delay control and its stated default.
• ScreenshotMachine pricing — current plan and caching details; check for updates before relying on pricing.