Practical uses of screenshot responses

You can select that your request is returned as a screenshot:

The most common use case is when you need to see particular information on the page and do not necessarily need to parse the full HTML. In reality, there are multiple ways you can use this function.

If you want to execute a particular JS scenario and it seems like nothing is working, try enabling the screenshot response to see how far along your JS scenario gets. Does it only click the first button or none at all? Does it fill in the information but fail to click the search option? Is the “more results” button clicked only twice instead of as many times as possible? The applications for troubleshooting are vast.

Another option is to use screenshots when you notice that not all the information is being loaded. Check what actually gets loaded or returned, and adjust your wait or scroll parameters accordingly.

We recommend using the full-page screenshot response when troubleshooting, since it allows you to see everything rather than just a specific part of the page. The default screenshot returns only the first part of the page, while the screenshot selector returns a screenshot of a specific element.

Updated on: 01/01/2026