> For the complete documentation index, see [llms.txt](https://docs.altava.com/creator-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altava.com/creator-guide/modeling-guidelines/polygon-two-sides.md).
# Polygon two sides
{% hint style="info" %}
**Two sides** refer to the common practice in 3D modeling where only one side of the model's surface is rendered. This is typically the side visually displayed. However, when rendering both sides, the system needs to perform double the graphic work, which can affect performance.
{% endhint %}
Some platforms discourage the use of Two sides to maintain optimal performance. In addition, there are instances where using Two sides can be a reason for rejection during evaluation.
1. Only ensure that the backside of the polygon is not visible.
2. For simple cases, as shown in the picture, the most efficient way to save on polygon count is to block the holes.
After the work, please organize the mesh's UVs and textures.
For further details, please refer to the \[topology guidelines].
---
# 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.altava.com/creator-guide/modeling-guidelines/polygon-two-sides.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.