Optimize Screenshot Captures with Wait Delay

Enhance the accuracy of your screenshots by adding a customizable wait delay. This feature ensures that all elements of a web page are fully loaded before capturing the screenshot, which is crucial for capturing dynamic content and complete page renders.

For capturing full-page screenshots, incorporating a scroll wait functionality helps simulate user interaction by scrolling and waiting for content to load dynamically.

Default Wait Behavior and Customization

By default, a screenshot is taken when the network connection is idle for 500 milliseconds, suggesting that all major images and dynamic content have finished loading. This setting helps in capturing a static snapshot of the page.

The default wait duration is set to 0 milliseconds, allowing for immediate screenshot captures right after the page loads. You can adjust this delay to better suit your needs, with maximum durations depending on your subscription plan:

• Free Plan: 5000 milliseconds (5 seconds)
• Start Plan: 10000 milliseconds (10 seconds)
• Pro Plan: 30000 milliseconds (30 seconds)
• Enterprise Plan: 60000 milliseconds (60 seconds)

Handling Incomplete Content Loading

Some websites load additional content dynamically after the initial page load, such as high-resolution images or interactive elements. For example, a page may initially display low-resolution images and then load high-quality versions after a short delay.

By adding a wait delay, you ensure that such content is fully rendered before capturing the screenshot. This method avoids issues with missing or incomplete elements in your captures.

The screenshot example below illustrates a page where additional content loads after an initial idle period of 500 milliseconds:

Setting a Wait Duration for Optimal Captures

To capture a screenshot with an added wait duration of 5000 milliseconds (5 seconds) to ensure complete page load, use the following API request example:

Your API key can be found on the API Keys page. Need an API Key? Sign up to get started.
For internal applications, replace YOUR_API_KEY with your own unique API Key.
For public facing websites or hotlinks, generate a signed URL.