> 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/upload-scenes.md).

# Upload Scenes

Upload scene files, choose how to interpret ZIP archives, and follow their progress until they are ready to render.

{% hint style="info" %}
Uploads require at least **5 Render Credits**. Accepted files are `.orbx` and `.zip`, up to **100 GB** each. Package Cinema 4D and Blender scenes as ZIP archives.
{% endhint %}

{% stepper %}
{% step %}

## Choose your files

Open **All Scenes** in the sidebar, or open the [project](/docs/web-app/projects.md) you want the scenes added to. Click **Upload scene** at the top, then choose one or more files from your computer.

You can also drag files from your computer into the app window and drop them when **Drop Scene files** appears. This works from any page in the app.

<details>

<summary>Other places to start an upload</summary>

* In a scene list, click the **Upload Scene** card when it is shown, or the upload button when the list is empty.
* In an open project, use the upload button in its **Attributes** panel.
* On **Projects**, use the upload action on a project's card or table row, in its right-click menu, or in the action bar after selecting it. An empty **Projects** page also offers **Upload Scene**.

Selecting a project in the **Projects** list does not make it the upload destination.

</details>
{% endstep %}

{% step %}

## Confirm any ZIP archives

ORBX files start uploading immediately, even when ZIP archives from the same selection are waiting for confirmation. If you selected only ORBX files, skip to [Follow the upload](#follow-the-upload).

For ZIP archives, **Interpret Uploads** opens:

1. Choose **ORBX**, **Cinema 4D**, or **Blender** to match the scene inside the archive.
2. If **Assign to project** appears, select a project or leave it empty. This field is hidden when uploading from an open project.
3. For several archives, these choices apply to all of them. Open **Individual Selections** to choose a different scene type or project for each file.
4. Click **Confirm** to start the ZIP uploads. The button is available once every archive has a scene type selected.

To create a project in this window, open **Assign to project**, click **Create new project**, enter a name, and press Enter. The project is created and selected for the upload.
{% endstep %}

{% step %}

## Follow the upload

The **Activity** panel opens on the right when uploading starts. Look under **Uploads** to follow progress. If the panel is closed, click **Open activity panel** at the top right of the app.

Your scenes also appear in **All Scenes** and, if assigned, in their project. After the file has uploaded, the scene may show **Queued Processing** or **Processing** while it is prepared for rendering.

{% hint style="warning" %}
Keep this browser tab open while files are uploading or waiting to upload. Reloading the page or closing the tab interrupts those uploads. You can move between pages within the app while uploads continue.
{% endhint %}

When a scene shows **Ready**, open it and click **Create Job** at the top to choose your render settings. See [Scene details and versions](/docs/web-app/scenes-and-versions.md) to inspect the scene or upload a revised version.
{% endstep %}
{% endstepper %}

## Cancel an upload

To stop one upload, use **Cancel Upload** on its entry in **Activity**. Other uploads continue. You can also use this action on the scene's card or table row, in its right-click menu, in the action bar after selecting it, or in the open scene's top bar or **Attributes** panel.

{% hint style="warning" %}
Cancelling removes the scene from the app. If you are uploading another version with **Upload Snapshot**, this also removes the scene's earlier versions.
{% endhint %}

To stop all current uploads, click **Cancel All Activity** at the bottom of **Activity** and review the confirmation. This action also affects active renders and downloads, so check what is listed before confirming. The same control is available in the floating **Activity** window.

{% hint style="info" %}
**Cancel** in **Interpret Uploads** discards the ZIP files waiting in that window. It does not stop ORBX files that have already started uploading.
{% endhint %}

## If an upload does not work

<details>

<summary>Upload scene is unavailable</summary>

Use the credit balance button at the top of the app to add credits, then try again.

</details>

<details>

<summary>A file is rejected</summary>

Read the message beside the file under **Invalid files** or in **Upload Error**. If you dropped a folder, select the scene files inside it instead.

If you selected several files, the rejected files do not prevent valid ORBX files from uploading or valid ZIP archives from being confirmed.

</details>

<details>

<summary>A scene shows Upload Failed</summary>

Read the upload error in **Activity** or the error notification. If the browser tab was closed or reloaded, select the file again to restart the upload.

</details>

<details>

<summary>A scene shows Failed or Requires Review after uploading</summary>

**Failed** means the scene could not be prepared for rendering. **Requires Review** means it needs a check by the Render Network team before it can be rendered. Use **Help & Feedback** in the sidebar if you need help with the scene.

</details>


---

# 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/upload-scenes.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.