> For the complete documentation index, see [llms.txt](https://guide.swiftxr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.swiftxr.io/3d-content-creation/specifications/web3d-cheat-sheet.md).

# Web3D Cheat Sheet

<table data-header-hidden><thead><tr><th width="54"></th><th width="139"></th><th></th><th width="258.5"></th></tr></thead><tbody><tr><td><br></td><td>Item</td><td>Count</td><td>Description</td></tr><tr><td>1</td><td>Tris Count</td><td>&#x3C; 200,000 </td><td>Lower triangle count generally improves performance.</td></tr><tr><td>2</td><td>Number of Mesh Parts </td><td>&#x3C; 15 </td><td>Fewer mesh parts can lead to fewer draw calls, improving performance.</td></tr><tr><td>3</td><td>Number of Materials</td><td>&#x3C; 20</td><td>Aim to use texture maps over complex node setups.</td></tr><tr><td>4</td><td>File Size</td><td>&#x3C; 30 MB</td><td>Strive for smaller file sizes for faster upload times and performance.</td></tr><tr><td>5</td><td>Recommended Modelling Tools</td><td><p>Blender, Maya, etc.</p><p><br></p></td><td>Choose software that supports efficient modelling and GLB/glTF export.</td></tr><tr><td>6</td><td>Modelling Best Practices</td><td>Efficient &#x26; Clean</td><td>Keep geometry clean and delete unseen geometry. </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 dynamically by asking a question.

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

```
GET https://guide.swiftxr.io/3d-content-creation/specifications/web3d-cheat-sheet.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.