> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/editready/getting-started.md).

# Getting Started

Clips can be added to EditReady by selecting `Open` under the `File` menu, or by dragging clips into the EditReady window. Your clips will appear with thumbnails in the EditReady window. You may toggle between `List View` and `Thumbnail` view using the selector in the toolbar.

If you'd like to convert all of your clips, simply click the `Convert All` button on the right. If you'd only like to convert some clips, you can select them by clicking the `flag` icon (or selecting `Flag Clip` from the `Clip` menu). Then click `Convert Flagged`.

EditReady includes a variety of presets for popular editing formats like ProRes and DNxHD. You can customize these further by creating custom presets.

Regardless of the preset you select, you have the option of adjusting the destination folder and destination file name. See `Naming your Files` for details.

### Multiple Windows

You can open multiple windows by selecting `New Window` from the `File` menu. This allows you to easily queue different batches, with different settings.

### Monitoring Progress

After starting a batch, the sidebar will toggle to the `Progress` tab, which will show you progress information for each clip. The top of the EditReady window will show you progress information for the overall batch (or batches).


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hedge.video/editready/getting-started.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 `automate deployments from our CI pipeline` 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.
