> For the complete documentation index, see [llms.txt](https://docs.v-nova.com/technologies/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v-nova.com/technologies/v-nova.presenz/v-nova-presenz-documentation/rendering-resolution.md).

# Rendering resolution

 **Rendering resolution**

Currently in our Authoring released Plugins, V-Nova PresenZ imposes some limits in the choice of resolutions and aspect ratios we can use to render.

* Our volumetric image format (.PRZ) is able to handle image resolution going from (6048,4032) to (288, 192). Usually we render at (3024,2016), which corresponds to around 4K to 6K, equivalent to a  360 image
* The PresenZ camera uses a cubeMap3x2 projection, which brings us to lock the aspect ratio to 1.5
* For technical reasons, mostly linked to the underscanning system, the resolution must be a multiple of 24.

To summarize, the rendering resolution must be a multiple of 3x24=72 in width and 2x24=48 in height, with a width-to-height ratio of 1.5, and must be within the range of (6048, 4032) to (288, 192). Here are some examples of supported resolutions:

| (288 ,192 ) Minimum       | 4 x(72) | 4 x(72x3/2) |
| ------------------------- | ------- | ----------- |
| (720 ,480 )               | 10x(72) | 10x(72x3/2) |
| (1512,1008) Good for Test | 21x(72) | 21x48       |
| (2160,1440)               | 30x(72) | 30x(72x3/2) |
| (3024,2016) Default       | 42x(72) | 42x(72x3/2) |
| (6048,4032)               | 84x(72) | 84x(72x3/2) |

{% hint style="info" %}
*Note: Through their graphical interface, our authoring plugins will help you to set a compatible resolution.*
{% endhint %}

<img src="/files/XjPvzdak6KiZ9Trur3Pf" alt="" data-size="original">\
\
\&#xNAN;***Warning:** Unless you really know what you are doing, we do not recommend going higher than the default: 3024 \* 2016*


---

# 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.v-nova.com/technologies/v-nova.presenz/v-nova-presenz-documentation/rendering-resolution.md?ask=<question>&goal=<endgoal>
```

`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.