> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/tutorials/intermediate-fire-extinguisher-training/electrical-fire/upload-3d-models-to-cloud-file-manager.md).

# Upload 3D models to Cloud File Manager

You can create your own 3D models in a 3D modelling application, such as 3D Studio Max, Maya, or Blender. Alternatively, you can obtain 3D models from a third-party site, such as Sketchfab or TurboSquid.

{% hint style="warning" %}
Ensure that any 3D models that you use are appropriate are appropriate for use in a real-time application. They should be as small in files size as possible. We recommend that you use .glb files.
{% endhint %}

If you have access to the Cloud File Manager, complete the following steps to upload

1. Go to <https://app.engagevr.io/login>, and then log in.
2. From the menu on the left, select **Files**.
3. On the **Files** page, select the **Browse** tab, and then select the **3D Models** folder.
4. Select **UPLOAD**.
5. In the **Upload File** panel, select **SELECT FILE**.
6. Browse to and select the 3D model.
7. Select **UPLOAD**.
8. Repeat from Step 4 for each file.


---

# 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.engagevr.io/engage/experience-editor/tutorials/intermediate-fire-extinguisher-training/electrical-fire/upload-3d-models-to-cloud-file-manager.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.