> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/adding-questions-and-content/content-reference/video-content.md).

# Video

A video shown to the responder

Using video content, you can add a video in your flow. This is commonly used for graphics or any other visual content to help explain concepts.

Click the "**+Add Image**" box under the **URL** toggle to open to modal. Here, you will have two options for displaying video: 

1. Upload a video file to the studio (.mp4 and .mov) 
2. Provide a URL to a publicly available resource (i.e. a server) that is hosting the video content 

{% hint style="info" %}
Video-sharing websites, such as Youtube and Vimeo, are not available as a URL option. These sites do not allow sharing the video file, rather they provide a link to the page of their site. You may want to consider creating a [iframe question](/adding-questions-and-content/question-reference/iframe-question.md), and embedding the web page there. 
{% endhint %}

{% hint style="info" %}
The maximum size for the video content is 10MB.
{% endhint %}

## Configuring your videos

You can ensure that your video starts playing as soon as the video content is loaded, by enabling **Auto-play?** option in the settings menu that appears when the question selected. 

Additionally, you can set the image that you would like the responder to see until your content is loaded with the **Loading image url** option.

You also have the option to run your video in repeat by enabling **Loop?** and letting the responder decide when to play and pause the video by enabling **Show controls to user?**


---

# 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.formsort.com/adding-questions-and-content/content-reference/video-content.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.