Locate the timeout
An API TIMEOUT concerns the capture operation. A timeout from your SDK, reverse proxy, automation platform, or serverless runtime may occur before the API returns a result. Keep the original response or exception so the source can be identified.
Reduce unnecessary waiting
- Check that the target URL is publicly reachable.
- Verify any
waitForselector exists and becomes visible. - Try
waitUntil: "load"or"domcontentloaded"if"networkidle"never completes. - Remove unnecessary delay and page actions, then increase the capture timeout within the supported range if needed.
Use async for longer work
Async jobs allow your application to submit work and retrieve the result later. Retrying a synchronous request after your own client timed out may repeat a capture that is already running. Keep retries bounded and compare with a minimal request.
Documentation
Related support articles
Fix a blank or incomplete screenshot
Check page readiness, selectors, client-side rendering, and blocking options.
Fix a cut-off full-page capture
Check scrollable content, capture height, sticky elements, and full-page mode.
Fix missing images, fonts, or styles
Identify late-loading resources, blocked requests, and differences from your own browser.
Need help with this issue?
Email support with this article, your request or capture ID, and the result you expected. Remove credentials and private information first.
Email [email protected]