> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/record-and-capture/screenshot.md).
# Screenshot
Capture screenshots with technical diagnostics and share one link.
Capture a screenshot with Screendesk and share a single link.
Screendesk attaches the technical context engineers need to debug quickly.
Start with **Capture Screenshot** in the extension. After capture, review it and choose **Upload** to get a shareable workspace link. Choose **Close** to keep it as a [local draft](/screen-recorder/review-and-share/drafts.md).
### Technical diagnostics included
When you capture a screenshot, Screendesk auto-includes:
| Included data | Helps with |
| ------------------------------------------- | -------------------------------------------------- |
| Console logs | Spotting runtime errors and warnings. |
| Network requests | Debugging failed APIs, status codes, and payloads. |
| URL | Jumping to the exact page state. |
| Timestamp and timezone | Correlating with deploys and incidents. |
| Device, OS, browser | Reproducing environment-specific bugs. |
| Viewport size | Diagnosing responsive layout issues. |
| Network speed | Identifying latency and throttling-related bugs. |
| Full-page context (for cropped screenshots) | Seeing what surrounds the cropped area. |
You get one link to share with an engineer or paste into a ticket.
### Capture a full screenshot
Click once on the page to capture the visible viewport.
Example:
### Capture a cropped screenshot
Click and drag to crop an area of the screen.
For cropped captures, Screendesk can also include a full screenshot.
It shows next to the crop in the shared link. This gives engineers the surrounding context.
If you don’t want the full screenshot included, turn it off in the capture draft before you select **Upload**.
### Annotations
After capture, add annotations like drawings, shapes, arrows, and text.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.screendesk.io/screen-recorder/record-and-capture/screenshot.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
