> For the complete documentation index, see [llms.txt](https://learn.shapesxr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.shapesxr.com/getting-started/performance-limitations.md).
# Performance limitations
### **Multiplayer**
We recommend up to 8 people in the same space creating and communicating. There’s no hard limit on the maximum number of people in space, but you may see a drop in performance or have audio issues starting at about 12 people in space with you.
### **Space complexity**
It's up to you how complex your spaces are. We don't limit. The frame rate will go below 70 (and become unpleasant) if you have too many objects or the objects are too high-poly.
To ensure the performance is fine, we recommend having no more than 100 unique objects per scene, 300 unique objects per space, and up to 3000 objects total per space including duplicates.
In our projects (from examples to prototypes), we aim to have no more than 300,000 polygons per scene. If, for instance, an imported object has 10,000 polygons, we keep no more than 30 of its copies in a scene. The same applies to strokes (something you can draw), the longest, most complex stroke (where it stops drawing automatically) will be around 10,000 polygons—so it’s better to have no more than 30 of them per scene.
### Importing files
Learn about import and its limitations [here](/import/limits-and-recommendations.md).
---
# 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://learn.shapesxr.com/getting-started/performance-limitations.md?ask=&goal=
```
`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.