> For the complete documentation index, see [llms.txt](https://mywebar.gitbook.io/mywebar-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mywebar.gitbook.io/mywebar-knowledge-base/creating-webar-projects/optimizing-and-preparing-3d-models-for-loading.md).

# Optimizing And Preparing 3D Models For Loading

Before uploading 3D models to the MyWebAR editor, you need to do several operations and check some conditions.

## **Model size correction**

The editor has a file upload limit of 50 MB.

{% hint style="warning" %}
On the Web, it is good practice to use models no larger than 20-30 MB (best is 10 MB), otherwise the user will wait forever for the scene to load.
{% endhint %}

### **How to reduce the size of an object?**

1. The easiest way is to reduce the resolution (size) of the texture. For the Web, 1024px is enough in .jpg format. A larger size will not have a big impact on the quality of the scene, but it will crucially decrease the loading speed in AR.
2. Reduce the number of polygons. This will lead to a reduction in size.
3. Another way to reduce the size is to reduce the number of keyframes.

## **Correcting errors and warnings in the model**

3D models in a web browser may work slightly differently in comparison with the software that is specially designed for them.

That’s why it’s necessary to check the models for errors before uploading them.

You may use babylonjs.com for testing your models.

![](/files/FxOi30ZjaqoPfCjyw1wj)

This site allows you to check for errors and deal with them. If there are no errors, the model is considered suitable for use on the Internet.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mywebar.gitbook.io/mywebar-knowledge-base/creating-webar-projects/optimizing-and-preparing-3d-models-for-loading.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.