> 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/screenshot-hover-state.md).
# Screenshot hover state
Capture hover-only UI (tooltips, menus, dropdowns) with a delayed Screendesk screenshot.
Capture tooltips, menus, and other hover-only UI using Screendeskâs capture delay.
{% stepper %}
{% step %}
### Open capture options
Open the Screendesk browser extension.
Click the chevron next to **Capture screenshot** to see more options.
{% endstep %}
{% step %}
### Pick a delay
Select a **3-second** or **6-second** delay.
{% endstep %}
{% step %}
### Start the capture
* For a cropped screenshot, click and drag to select an area.
* For a full screenshot, click once on the page.
When you release the mouse, the countdown starts.
{% endstep %}
{% step %}
### Set the hover state
During the countdown, hover the element you want to capture.
Keep the cursor in place until the timer ends.
{% endstep %}
{% step %}
### Annotate and share
After capture, add annotations if needed.
Select **Upload** to generate a shareable link with the screenshot and diagnostics.
{% endstep %}
{% endstepper %}
---
# 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/screenshot-hover-state.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.
