# Screen capturing

### Quick overview

**BetterBugs.io** enables you to take instant or [delayed screenshots](/product-features/screen-capturing/delayed-screenshot.md) of any bug or issue. Along with the screenshot, it captures and auto-attaches technical details of the issue, such as:

* System info
* Console logs
* Network requests
* Backend (event logs from Sentry)
* Steps (Page navigation steps)
* Metadata (Custom)
* Application State

You can also use the "**AI**" toggle to get add quick summary and steps to reproduce the issue while creating the report session. 

The [auto-attached technical information](/product-features/developer-tools.md) (along with the visual proof of the issue) helps you run the **manual RCA** with all the info and context you need and debug significantly faster. 

For debugging purposes with BetterBugs.io bug reports, you can do it using:

* Manual methods (using the [auto-attached developer tools info](/product-features/developer-tools.md) paired with the visual proof)
* [AI Debugger](/debug-a-report/ai-debugger.md)
* [MCP (Model Context Protocol) Server](/debug-a-report/mcp.md)

### **How it Works**

1. Capture the screen.
2. BetterBugs.io automatically adds all relevant details and information.
3. Upload the screenshot to create report session with all the details.
4. Share the report link with others for debugging.

### Available Modes for Screenshot Capturing in BetterBugs.io

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Cropped screenshot</strong></td><td>Take a screenshot by dragging and selecting screen area.</td><td><a href="/files/70nY0nTA2LeAYlkJO7E5">/files/70nY0nTA2LeAYlkJO7E5</a></td><td><a href="/pages/kHe6xLJKnpu5RkYd9g4L">/pages/kHe6xLJKnpu5RkYd9g4L</a></td></tr><tr><td><strong>Visible screen capture</strong></td><td>Capture the complete screen as a screenshot with one click.</td><td><a href="/files/JrO2Z8Hy0KHFqaGGTHlE">/files/JrO2Z8Hy0KHFqaGGTHlE</a></td><td><a href="/pages/QQbvCUNzfk8kusqHXbJ0">/pages/QQbvCUNzfk8kusqHXbJ0</a></td></tr><tr><td><strong>Full web page screenshot</strong></td><td>Capture the entire web page to get a scrollable screenshot</td><td><a href="/files/gCI6k4ccQOZXsjZgvV1F">/files/gCI6k4ccQOZXsjZgvV1F</a></td><td><a href="/pages/qtHaE8eFUjoOEqpkuqg5">/pages/qtHaE8eFUjoOEqpkuqg5</a></td></tr></tbody></table>

### **BetterBugs.io Bug Report: Key Features for Screen Capturing**

* Visual proof
* Auto-attached technical details
* Context-specific
* User-friendly
* Shareable as links

Not only QA engineers and developers but also project managers and support teams can easily generate, share, and understand these reports.

When you capture a screenshot with BetterBugs.io, developer-friendly details are auto-captured and tagged with it. You don't have to worry about adding anything manually. QA can send these comprehensive reports to the development team within minutes, making the bug-reporting workflow frictionless.


---

# Agent Instructions: 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.betterbugs.io/product-features/screen-capturing.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.