> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/getting-started-subscribers-viewers/rad-tv-for-ps5-ps-vr2/file-naming-conventions.md).

# File Naming Conventions

There are specific naming conventions to which videos must adhere for the app to automatically recognize the type of video it needs to render. By default, the app will attempt to render a **Rectangle** with a **Monoscopic** projection, therefore, it is not necessary to explicitly append any tags to the file name.

## Content Type <a href="#psvrsideloadinstructions-en-fixedframevideos" id="psvrsideloadinstructions-en-fixedframevideos"></a>

* #### Rectangle
  * This refers to the 'Rectangle' content type setting in the video player settings submenu.
  * This is the default content layout setting in the video player settings submenu, so there is no need to include any tags in the file name for this particular setting.
  * Currently stereoscopic rectangle (think 3D movie) content is not supported.
* #### Spherical 180°
  * This refers to the 'Spherical 180°' content type setting in the video player settings submenu.
  * File name needs to contain "180"
* #### Spherical 360°
  * This refers to the 'Spherical 360°' content type setting in the video player settings submenu.
  * File name needs to contain "360"

## Content Layout

* #### Monoscopic
  * This refers to the 'Monoscopic' content layout setting in the video player settings submenu.
  * This is the default content layout setting in the video player settings submenu, so there is no need to include any tags in the file name for this particular setting.
* #### Stereoscopic Top-Bottom
  * This refers to the 'Stereoscopic Top-Bottom' layout type setting in the video player settings submenu.
  * File name needs to contain either "tb", "bt", or "ou".
* #### Stereoscopic Side-by-Side
  * This refers to the 'Stereoscopic Side-by-Side' layout type setting in the video player settings submenu.
  * File name needs to contain either "sbs", "lr" or "rl".

## Examples

* myvideo.mp4
* myvideo\_180.mp4
* myvideo\_180\_ou.mp4
* myvideo\_180\_tb.mp4
* myvideo\_180\_bt.mp4
* myvideo\_180\_sbs.mp4
* myvideo\_180\_lr.mp4
* myvideo\_180\_rl.mp4
* myvideo\_360.mp4
* myvideo\_360\_ou.mp4
* myvideo\_360\_tb.mp4
* myvideo\_360\_bt.mp4
* myvideo\_360\_sbs.mp4
* myvideo\_360\_lr.mp4
* myvideo\_360\_rl.mp4


---

# 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.rad.live/rad/getting-started-subscribers-viewers/rad-tv-for-ps5-ps-vr2/file-naming-conventions.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.