# Video Data

### Video Data

<figure><img src="/files/Ny2jxNuzkNE97BIBKVeP" alt="_images/vid_folder_structure.png" width="375"><figcaption><p><strong>Example structure of video data.</strong></p></figcaption></figure>

‍

{% hint style="danger" %}
Video names must not contain accents, as these can cause errors during the Organize Videos process. Use only alphanumeric characters with space, hyphen (-), underscore (\_), or period (.) as delimiters. Avoid using commas (,) or semicolons (;).
{% endhint %}

The video data for a single trial must be contained in its own folder, and each video file must be in its own subfolder. The name of each subfolder must be the ID of the corresponding camera. There are no requirements on the structure of the names of the video files, but the names must be unique and videos must be .avi or .mp4 format. For example, the figure above shows video data for a walking trial collected using four cameras with IDs 21375, 21379, 21380, and 21381.

Organizing your videos in this format can be achieved using the [Organize Videos](/axiom-v2025/theia3d-documentation/theia3d-dropdown-menus/tools-menu/organize-videos.md) tool.

It is also best practice to keep the associated extrinsic calibration file nested within the trial folder and beside the camera ID folders. This can be achieved using the [Assign Calibration Files](/axiom-v2025/theia3d-documentation/theia3d-dropdown-menus/tools-menu/assign-calibration-files.md) tool.


---

# Agent Instructions: 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:

```
GET https://docs.theiamarkerless.com/axiom-v2025/theia3d-documentation/data-formats/video-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
