> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/augmented-reality/low-poly-models.md).

# Low-Poly Models

Keep AR models light and quick to load on Apple devices. Learn when to use a low-poly model and how to add one to new or existing products.

## Why, when and how to use a low-poly model

Unlike our web configurator, which supports Draco-compressed models, USDZ files used by Apple devices in AR must be uncompressed.

These files are many times larger than the compressed ones. For this reason, we recommend adding an additional low-poly model specifically for AR purposes.

To facilitate this, we have provided a mechanism for you to add a low-poly model in the product administration panel.

{% hint style="info" %}
If no low-poly (lower quality) model is provided, we will still generate the AR model using the main HQ model. This is only a recommendation and an optional feature, not a requirement.
{% endhint %}

{% hint style="warning" %}
The low-poly model should contain exactly the same meshes and mesh names as the high-quality model.
{% endhint %}

***

## How to add a low-poly model

{% tabs %}
{% tab title="New products" %}

1. Under the **3D/AR** tab, click the **Bulk add** button.
2. Upload your GLB files – both high- and low-poly.
3. Use the **Low poly matcher** – define your match type (**prefix** or **suffix**) and its value.

![Low poly matcher with match type and value fields](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FpAvIulYlvpg6J0BWsufx%2Flow-poly_2gmlbx.png?alt=media)
{% endtab %}

{% tab title="Existing products" %}
If you already had the GLBs added to the product, you can manually assign the low-poly models to the existing GLBs:

1. Under the **3D/AR** tab, click the pencil icon for the particular GLB.
2. Assign the matching low-poly model.

![Manual assignment of a low-poly model to an existing GLB](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2Fms4wcLBoAO9qySxbGI1X%2Flow-poly-assignment_edxhp5.png?alt=media)
{% endtab %}
{% endtabs %}

***

## How low-poly matching works

Normally, a file with a different name would be considered a separate file, and its meshes would load additionally. When you use the **Low poly matcher**, low-poly meshes are matched in the background with the high-poly meshes, so you only have to define the latter.

If you need any help or have any questions, feel free to reach out to Mimeeq support.

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>AR-Only Materials</strong></td><td>Assign a simplified material for AR without compromising your browser-rendered model.</td><td><a href="/augmented-reality/ar-only-materials.md">AR-Only Materials</a></td></tr><tr><td><strong>Unsupported AR Parameters</strong></td><td>See which material parameters AR does not support and how to work around them.</td><td><a href="/augmented-reality/unsupported-parameters.md">Unsupported AR Parameters</a></td></tr></tbody></table>


---

# 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://help.mimeeq.com/augmented-reality/low-poly-models.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.