# Geometry

Geometry - meaning the number of objects and polygons in a scene - is one of the main factors affecting both project size and real-time performance.

Reducing polygon count wherever possible is always a good practice. While scenes with up to **500,000 polygons** generally perform well, performance may degrade beyond that. The recommended target is **under 100,000 polygons** for the best experience. 

For **AR projects**, keeping polygon count below **100,000** is recommended.

#### Tips for reducing geometry

1. **Simplify modifier** – use the [Simplify modifier](/documentation/design-process/design-mode/deformers/simplify.md) to reduce polygon count while maintaining the overall shape of the object. Note that very high-polygon models may cause the browser tab to become unresponsive.\ <br>
2. **Use linked duplicates (instances)** – for repeating objects, use **linked duplicates** instead of full copies. Use **`Ctrl+Shift+D`** or the right-click context menu to create an instance. Instances share geometry, meaning they do not increase polygon count. Changes made to one instance update all linked ones. This same principle applies to [Array modifiers](/documentation/design-process/design-mode/modifiers.md#list-of-modifiers).\ <br>
3. **Simplify distant or hidden objects** – for objects that are far away or barely visible in the scene, consider reducing their detail or simplifying their geometry.\ <br>
4. **Remove internal or hidden geometry** – some models may contain internal geometry or objects that are not visible. These should be removed or hidden to reduce complexity.\ <br>
5. **Weld disconnected parts** – in geometry [Edit mode](/documentation/design-process/edit-mode.md), use the [Weld tool](/documentation/design-process/edit-mode/mesh-tools.md) to merge disconnected parts into a single mesh. This helps simplify and optimize the model.  &#x20;


---

# Agent Instructions: 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:

```
GET https://help.vectary.com/documentation/sharing-exporting-embedding/optimizing-a-shared-project/geometry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.