> 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/sharing-exporting-embedding/optimizing-a-shared-project/light-and-shadows.md).

# Light and shadows

[Local lights](/documentation/design-process/design-mode/light-sources.md) can enhance realism and atmosphere, but they can also significantly impact performance — especially when shadows are enabled.

#### Tips & recommendations

* **Try HDRI adjustments first** – if a scene lacks lighting, start by trying different [**HDRI environments**](/documentation/design-process/environment.md). And make sure to fine-tune HDRI parameters for optimal lighting results. \
  Note that **Environment Intensity** can be set above 100% by manually entering the value.\ <br>
* **Be mindful with shadows** – by default, local lights have shadows disabled. Enable them only when necessary, and only on the specific lights where shadows add a clear visual benefit.\ <br>
* **Prefer directional or spotlight sources** – these light types are generally more efficient in terms of shadow rendering and performance.\ <br>
* **Limit shadow-heavy light types** – avoid using more than one **Point** or **Rectangle** light with shadows enabled in a scene. These types of lights are more taxing on performance.


---

# 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/sharing-exporting-embedding/optimizing-a-shared-project/light-and-shadows.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.