> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/workflow-concepts/workflow-steps/image-and-video/screenshot-from-url.md).

# Screenshot from URL

The "Screenshot from URL" step allows you to capture a screenshot of a webpage directly within your workflow. This is useful for creating visual references, analyzing website designs, or including webpage captures in your content.

### How to Configure the Screenshot from URL Step

Configuring the step requires setting the parameters shown below:

* **URL**: Enter the complete URL of the webpage you want to capture. Make sure to include the protocol (http\:// or https\://).
* **Capture Mode**:
  * Full Page - Captures the full height (scrolls down the bottom of the page) and width of the page
  * Viewport - Captures the height of the original viewport (without scroll) and full width

### Output Format

The Screenshot from URL step returns an image URL.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/actions/workflow-concepts/workflow-steps/image-and-video/screenshot-from-url.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.