> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/virtual-photographer/create-renders.md).

# Create Renders

## Introduction

Within the Threekit Platform, creating Virtual Photographs requires just a few simple clicks.

Creating Virtual Photos of your products is quick and easy:

Start by navigating to the Item you wish to render, create a [**New render job**](/learn/training/self-led-training/basic-renders.md)

![](/files/AZXhX6pUETPEtcBBNZH1)

## Creating New Renders

On the Create Render Job interface, the Item from which you hit the button should appear by default in the Select Item field. Select a Stage, then provide a meaningful name. Feel free to limit the renders by hitting the **Limit Configurations** button. Select the desired Render Type and Resolution, then hit **Render**.

![](/files/g5Yt7p1OLzhJLYeniXuJ)

Upon hitting render, the user is re-directed to a page specific to the render job. The user may filter based on Status as well as access information on each of the individual renders.

![](/files/QKpwxp0HDBMgsArDXE5F)

The Renders will take a few minutes to process. Once the job has completed, View your Virtual Photos

## Render Job Times

For planning purposes, the following throughput is considered typical when it comes to Vray renders. Actual rendering times vary based on concurrent activity.

**1k resolution - 30 min / 1000 renders**

**2k resolution - 60 min / 1000 renders**

**4k resolution - 120 min / 1000 renders**

{% hint style="info" %}
For additional fees, it is possible to dedicate more rendering resources short-term and reduce the rendering times. If you are interested in this, please reach out to <rendering@threekit.com>.
{% 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 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://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/virtual-photographer/create-renders.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.