> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/apollo-v2024/troubleshooting/error-messages/input-directory-has-no-mp4-or-avi-files..md).

# Input directory has no mp4 or avi files.

<figure><img src="https://3784186061-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5NTeqxfMEXoI7Qj5TlH5%2Fuploads%2F3H5XzD4Jpm1OQHRKbqTc%2Fimage.png?alt=media&amp;token=c830223d-20c1-4bd1-a11e-7bd6700e6a82" alt=""><figcaption></figcaption></figure>

### Explanation

This error message arises when attempting to use the [Organize Videos Tool ](/apollo-v2024/theia3d-documentation/theia3d-dropdown-menus/tools-menu/organize-videos.md)to organize video files as required by Theia3D. Theia3D requires video data to be .mp4 or .avi file formats, so if the directory selected for organizing contains video files of a different format (e.g. .mkv, .mov, etc.) Theia3D will be unable to organize or load these videos.

### Possible Solutions

To ensure your video data can be organized, loaded, and processed by Theia3D, they should be in .mp4 or .avi file formats. If possible, re-export the original videos to the correct file format, or convert the existing video files&#x20;


---

# 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.theiamarkerless.com/apollo-v2024/troubleshooting/error-messages/input-directory-has-no-mp4-or-avi-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.