> For the complete documentation index, see [llms.txt](https://docs.viverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.viverse.com/playcanvas-toolkit/building-with-the-playcanvas-toolkit-legacy-v3/no-code-tools/media/video.md).

# Video

***

### Media Video

#### Adding Video And Extending Video Functionality

| <img src="/files/Y3FzVRscfS7Xg4104D0W" alt="" data-size="original">     | <img src="/files/hre4NQJF1BR9mgvv1uut" alt="" data-size="original"> |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------- |
| The user uses the mouse to hover over the video to access the controls. | The video is playing.                                               |

{% stepper %}
{% step %}

#### Setup video

A. Create a new entity

B. Resize the video using the **Scale**.

C. Click the **Edit Viverse Extension** button.

<figure><img src="/files/2gE4mLXre2UERFrTlrI1" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Add the video module

A. In the VIVERSE extension, select the **Media** plugin for the **Select plugins** dropdown.

B. Select the **Video** module and add it, then select either "Asset" for files contained in your PlayCanvas project, or "URL" for a video to stream, such as a YouTube URL (but please note: YouTube or other embeds are run inside iframe elements, which do not render in VR). For this example, choose "Asset."

C. Add the video to the **Asset** field by selecting it within your project.

D. Uncheck the **auto play** property to prevent the video from starting when the avatar enters the environment.

<figure><img src="/files/A7xUOmjG4Sh0yALiPOxs" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.viverse.com/playcanvas-toolkit/building-with-the-playcanvas-toolkit-legacy-v3/no-code-tools/media/video.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.