> ## Documentation Index
> Fetch the complete documentation index at: https://docs.altoura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Import Content

> This topic covers best practices for creating 3d content for Altoura

<Warning>
  ### We follow the guidelines that Microsoft has published for AR/VR creation:

  [https://docs.microsoft.com/en-us/dynamics365/mixed-reality/product-visualize/optimize-models](https://docs.microsoft.com/en-us/dynamics365/mixed-reality/product-visualize/optimize-models)
</Warning>

## 3D model optimization

In order to maintain performance, your 3d models might need to be optimized before importing into Altoura. The following table lists some general polycount and draw-call limits for a range of hardware

| Device                 | Polycounts | Draw-call Batches |
| ---------------------- | ---------- | ----------------- |
| PC (with discrete GPU) | 10M        | 2000              |
| Mobile                 | 2M         | 200               |
| HMD                    | 500K       | 50                |

## Supported model file formats

Since Altoura uses Unity engine, we support all the 3d formats that Unity can read.

The native formats are -.fbx -.dae(Collada) -.dxf -.obj

When exporting your model for Altoura, these formats are the easiest for Unity to read. If you have other proprietary formats, please convert them into .fbx format before importing.