> 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/review-and-share/drafts.md).

# Drafts

Continue an unfinished screenshot, screen recording, or Instant Replay without uploading it immediately.

## Keep a capture for later

Choose **Close** in the capture review screen. Screendesk keeps the unfinished capture as a draft in your current browser profile.

Use **Delete** to discard a capture instead.

## Open a draft

1. Open the Screendesk extension.
2. Choose **Drafts** from the menu, or use the drafts button.
3. Select a capture to reopen its review screen.
4. Finish reviewing it and choose **Upload** to create a shareable workspace link.

Drafts stay local to that browser profile. They do not sync between devices and cannot be shared as workspace links before upload.

## Retention and deletion

Drafts are automatically deleted after **seven days**. Upload anything you want to keep before it expires.

To remove a draft yourself, use its delete control and confirm the deletion. Clearing extension storage or uninstalling the extension can also remove drafts.

See [Review and share](/screen-recorder/review-and-share.md) for the upload workflow.


---

# 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/review-and-share/drafts.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 `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.