> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/guidelines-compatibility/guidelines/experience-optimizations/3d-model-optimizations.md).
# 3D Model Optimizations
* The model should be scaled to real life sizes and the origin point should be at the center of the model before exporting.
* For the model to be efficient, the poly count should be kept as low as possible. All the textures exported should go through a compression pass using online compressor tinypng.com or similar.
* Lower the size of the model, the better would be the loading speed.
* Ensure the number of vertices/triangles/polygons is as low as possible.
* Ensure textures are compressed
* Bake the textures into the model. Keep textures less than 4k resolution.
### 3D Model Details and File Size Recommendation​
| Element | Recommended Max Triangles Count | Recommended Max File Size |
| :--------------------: | :-----------------------------: | :-----------------------: |
| 3D Models - Cumulative | 50K | 50MB |
| Colliders - Cumulative | 5K | 5MB |
{% hint style="info" %}
The above recommendation is for the whole scene. This is, **less than 50k triangles, 50MB file size in total for a scene** (i.e. the sum of all triangles/file sizes for all 3D Models in a scene).
{% endhint %}
### Baking Textures into 3D Models
This is workflow we recommend.
#### **Steps:**
* Decide to combine all objects or do them as individual objects
* Texture your model correctly with properly unwrapped UVs - no overlaps
* Setup good lighting and test it in quick render modes
* Bake and export textures
#### Other Workflows:
*
*
---
# 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.gmetri.com/guidelines-compatibility/guidelines/experience-optimizations/3d-model-optimizations.md?ask=&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.