> For the complete documentation index, see [llms.txt](https://docs.arcware.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcware.cloud/unreal-engine-setup/set-up-pixel-streaming-in-your-own-project/optional-settings/playing-media-files.md).

# Playing Media files

Set up Pixel Streaming in your own project - Optional Settings

In Unreal Engine 5.1 the quickist way to get your media/video files playing is:\
\
\- Import your video into a **'File Media Source'** asset in the Content Browser (with file path to video in ''Game...''/Content/Movies/) \
\
\- Drag the **'File Media Source'** asset into the viewport, this will automatically create a **'Media Plate'** actor. \
\
\- The **'Media Plate'** actor can be controlled via blueprints. Using this actor removes the need to \
create individual 'Media Player/textures/materials' for each unique video imported. The actor makes audio playback easier as well, as the audio component is already implemented in the BP. \
\
\- Done

{% hint style="warning" %}
Warning: Only **AVI** and **H.264** file formats are supported, with Audio embedded as **AAC (ISO/IEC 14496-3)** 
{% endhint %}

{% hint style="info" %}
Note: If you find that your Media files still do not play properly, please alternately try with the 'Electra' media player plugin (available by default. 
{% 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.arcware.cloud/unreal-engine-setup/set-up-pixel-streaming-in-your-own-project/optional-settings/playing-media-files.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.