> For the complete documentation index, see [llms.txt](https://docs.inferix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inferix.io/inferix-whitepaper/decentralized-visual-computing/decentralized-storage-and-data-security/multi-level-3d-polygon-data.md). # Multi-level 3D polygon data In the stored data on Inferix, aside from images and videos, the geometry data of 3D models consumes the most storage space. Each time a render is performed, the Worker Node must download this data locally so that the render engines can execute the task. This process can consume significant bandwidth and time. To save bandwidth and reduce download times, 3D models are converted into two levels of detail, known as high-poly and low-poly, and are pre-stored on the Inferix network. The existence of multiple levels of 3D data is referred to as *multi-level 3D polygon data*. --- # 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://docs.inferix.io/inferix-whitepaper/decentralized-visual-computing/decentralized-storage-and-data-security/multi-level-3d-polygon-data.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.