> 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

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

![](/files/InabE04hMXvEHb5vOtdl)

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bugbug.io/debugging-tests/screenshots.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.