> 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/ground-plane.md).
# Ground plane
The [Ground plane](/documentation/design-process/ground-plane.md) is a useful feature for grounding objects and receiving shadows, but it can also impact performance — especially when using dynamic mode.
#### Tips & recommendations
* **Limit the size of the ground plane** – In dynamic mode, a large ground plane increases the area where real-time shadows are calculated. Keep it as small as necessary for better performance.
* **Use baked shadows when possible** – The [**Baked Ground plane**](/documentation/design-process/ground-plane.md#baked-shadow) is a more efficient alternative to dynamic shadows and often produces a more realistic result. In dynamic mode, shadows on the ground plane are calculated in real time, which can slightly affect performance.
{% hint style="success" %}
When baking the ground plane, a shadow texture is generated. Its resolution is selected during the baking process but can later be reduced in **Preview mode.**
{% endhint %}
---
# 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/ground-plane.md?ask=&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.
