> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/scenes-and-versions.md).

# Scene details and versions

View scene details, upload another version, find jobs by version, and rename a scene.

Use versions to keep revised uploads of the same scene together.

## Open a scene

Double-click a scene in **All Scenes** or in a [project](/docs/web-app/projects.md) to open its jobs page.

The scene's details appear in the panel on the left. If it is closed, click the scene name beside the gear icon at the top, or **Open attributes panel** at the bottom of the jobs list.

## Choose a version

Open **Versions** in the left panel. Uploaded versions are listed by date, with the latest marked **CURRENT**.

| Selection                             | Scene details                    | Jobs shown                            |
| ------------------------------------- | -------------------------------- | ------------------------------------- |
| **All Versions**, selected by default | The current version's properties | Jobs from every version of this scene |
| A dated version                       | That version's properties        | Only jobs created from that version   |

Switch to **Attributes** to inspect the selected version's properties, including its application and renderer.

{% hint style="info" %}
**Create Job** uses the selected version. With **All Versions** selected, it uses the version marked **CURRENT**. A version must be ready to render for this action to be available.
{% endhint %}

## Upload another version

{% stepper %}
{% step %}

## Choose the scene

Open a scene marked **Ready** and click **Upload Snapshot** in its top bar or left panel.

You can also use **Upload Snapshot** on a scene's card or table row, in its right-click menu, or in the action bar after selecting one scene in **All Scenes** or a project.
{% endstep %}

{% step %}

## Choose the updated file

Select the file from your computer. Follow [Upload Scenes](/docs/web-app/upload-scenes.md) for file requirements, ZIP choices, and progress.

Before stopping a version upload, read [Cancel an upload](/docs/web-app/upload-scenes.md#cancel-an-upload).
{% endstep %}

{% step %}

## Check the version

After uploading and processing finish, open **Versions**. The added version appears alongside the earlier versions and is marked **CURRENT**.
{% endstep %}
{% endstepper %}

## Rename a scene

1. In the scene's left panel, select **All Versions** or the version marked **CURRENT**.
2. Click the pencil beside the scene name.
3. Enter the name, then click the check button or press Enter.

Renaming changes the current version's name, which also appears in scene lists. Earlier versions keep their names.


---

# 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://know.rendernetwork.com/docs/web-app/scenes-and-versions.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.