> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/debugging-tests/screenshots.md).

# Screenshots

Discover BugBug's powerful debugging tests screenshots feature. Streamline bug identification and resolution with clear visual evidence. Try it now!

You can use screenshots to debug your tests and understand what was the reason for the failure.

When a test step is executed, **BugBug automatically takes screenshots**:

* of the whole window
* of the individual element

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FrZjlWLhBgovJ7MVa2Yol%2Fimage.png?alt=media\&token=89bef946-142a-4c2d-b862-2cfb9bc6206a)

Click the screenshots to see the full preview.

BugBug also keeps the screenshots history, so that you can also compare screenshots from previous runs. Just go to the ["Runs history" tab](/debugging-tests/runs-history.md).

{% hint style="info" %}
**How long screenshots are kept?** It depends on your subscription plan, learn more in [pricing](https://bugbug.io/pricing/).
{% endhint %}


---

# 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.bugbug.io/debugging-tests/screenshots.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.