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

# Video

### Section overview

The Video section displays a video that can be set to autoplay or play on click, with optional supporting content such as heading, text, and a call-to-action button.

#### Common Use Cases

* Product demonstrations or tutorials
* Brand storytelling and promotional content
* Background ambiance for landing pages
* Showcasing customer testimonials

#### Usage Tips

* Use a background image from the video as a placeholder for better performance
* Keep videos short (under 30 seconds) for better engagement
* Consider mobile data usage when enabling autoplay
* Ensure your video has appropriate contrast with text overlays for readability

### Section Settings

| Setting               | Description                                                               |
| --------------------- | ------------------------------------------------------------------------- |
| Image                 | Background image to display before the video plays                        |
| Video                 | The video file to be displayed in this section                            |
| Enable video autoplay | When enabled, the video will start playing automatically                  |
| Heading               | Main title text displayed in the section                                  |
| Content               | Descriptive text content to accompany the video                           |
| Button label          | Text to display on the call-to-action button                              |
| Button url            | URL the button links to when clicked                                      |
| Spacing top           | Controls the amount of space above the section (0-300px)                  |
| Spacing bottom        | Controls the amount of space below the section (0-300px)                  |
| Background            | Background color of the section                                           |
| Text color            | Controls the text color scheme (default, light, or dark)                  |
| Border color          | Color of the section border (subtle or strong)                            |
| Button color          | Color scheme for the section's button                                     |
| Border position       | Controls where borders appear on the section (none, top, bottom, or both) |
| X alignment           | Horizontal alignment of section content (left, center, or right)          |
| Visibility            | Controls section visibility on different device sizes                     |

### Block Settings

This section does not contain any blocks.


---

# 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://help.brickspacelab.com/paper/sections/content-and-media/video.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.
