> For the complete documentation index, see [llms.txt](https://help.visuary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.visuary.com/guide-visuary-en/visualization/renderings.md).
# Renderings
Create a Render:
1. Start by **saving your project** to make sure all your changes are saved.
2. Click the "**Renders**"
3. Click on "**Render**"
4. By clicking the "**Image**" you can choose between **making a static Render or a panorama**.
5. Position the camera in the room and adjust the desired viewing angle with your mouse
6. Click on "**Start a Render**"
{% hint style="success" icon="lightbulb" %}
Depending on the desired Render type (static or panoramic), camera placement on the plan is key:
* **For a static Render: place yourself in a corner** of the room to get as much distance as possible.
* **For a panoramic Render: place yourself in the center** of the room so the photo can be properly taken in 360°.
{% endhint %}
{% hint style="warning" %}
Renders are **only available with an Intégral or Enterprise subscription**.
{% endhint %}
Download a Render
After a few minutes, your Render is ready! You can download it by selecting it, then clicking the download icon.
{% embed url="" %}
{% hint style="warning" %}
If after 5 minutes your Render is still not available, we invite you to **reload your page** and it should appear.
{% endhint %}
Include Render outputs in the PDF report
**With an Intégral subscription**, renders can be included in the Commercial file to help your client visualise the result even more.
{% embed url="" %}
{% hint style="info" %}
Click [**here**](/guide-visuary-en/sharing-and-export/pdf-report.md) to learn more about the PDF report, available only with a subscription.
{% 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.visuary.com/guide-visuary-en/visualization/renderings.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.
