> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/capture-a-guideflow/how-to-capture-a-guideflow/screen-capture/video-capture-editor.md).

# Video capture editor

### How to edit video capture

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/zkjzzn8her>" %}

* Select a step to edit.
* The video icon indicates that the step is a video recording and can be edited.
* Open the video play bar.
* Drag the handles to trim the video.
* Adjust the playback speed by clicking the speed control to the right of the play bar.
* Select the speed (the options are 1×, 2×, 3×, and 4×).
* The video is now trimmed and has adjusted speed.

***

#### Video Transition

When a video is automatically captured during a screen recording flow (e.g. scrolling, typing, or drag and drop), you can choose to display that step as a static screen instead of playing it as a video.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/gkyz52nhdr>" %}

* Select the video step in the editor.
* Open **Step information** in the right panel.
* Toggle off **Video Transition** to display the step as a static screen.
* Toggle it back on at any time to restore the video playback.

{% hint style="info" %}
Video capture editor is not available for video step (manual type of recording).
{% endhint %}


---

# 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.guideflow.com/help/capture-a-guideflow/how-to-capture-a-guideflow/screen-capture/video-capture-editor.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.