> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/mcp/editing-demos/adding-and-editing-guided-steps/adding-and-editing-video-steps.md).

# Adding and Editing Video Steps

👉  Video steps can only be added to existing screenshot demos, allowing users to add and edit video steps right in Storylane.

### **🎥 Adding video steps**

We support a couple of ways to add video steps:

1. Upload mp4 files from device
2. Add video clips from the current & other demos
3. Capture new video clips from the extension

{% @storylane/embed subdomain="app" linkValue="hgh7nntxdvwu" url="<https://app.storylane.io/share/hgh7nntxdvwu>" %}

### :scissors: Editing Video Steps

The video editor now comes with an updated play bar at the bottom of the editor — giving you more control over your video steps. You can trim clips to the exact moment you need, add in guides between segments, and control playback speed. Mute, adjust timing, and fine-tune every detail without leaving the editor.

{% @storylane/embed subdomain="app" linkValue="0chwcm3j0bif" url="<https://app.storylane.io/demo/0chwcm3j0bif>" %}


---

# 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.storylane.io/mcp/editing-demos/adding-and-editing-guided-steps/adding-and-editing-video-steps.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.