> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/edit-mode/normals.md).

# Normals

Normals define the direction in which a surface faces, affecting shading, lighting, and rendering. By default, normals are rendered on one side of a face unless the **double-sided material** option is enabled. Properly configured normals help ensure accurate light reflections and prevent visual artifacts in rendering.

The **Normals** toolset provides options for adjusting the direction and smoothness of surface shading in a mesh.<br>

* **Flip Normals** — Reverses the direction of selected faces' normals. Useful for correcting incorrect shading or fixing inward-facing geometry.
* **Unify Normals** — Aligns all selected normals to face the same direction. Helps resolve inconsistencies in surface orientation for uniform shading.
* **Smooth Threshold** — Controls the angle at which normals are blended for smooth shading. Lower values maintain hard edges, while higher values create a smoother appearance between connected faces.

{% embed url="<https://vimeo.com/736558289>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.vectary.com/documentation/design-process/edit-mode/normals.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.