> 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/prepare-your-scene/differential-uploads.md).

# Differential uploads

Reuse uploaded assets when sending revised scenes through the Render Network Manager.

Differential uploads reuse files already available on the network. For example, changing a camera can require only the updated scene file, while unchanged textures and geometry are reused.

## Set up the Manager

In the [Render Network Manager](/docs/tools-and-api/manager-app.md), open **Settings** using the gear button.

1. Under **Uploads**, enable **Differential scene upload**.
2. For ORBX files, go to **Scenes** and set **Path to Octane Standalone** to your local Octane application. The Manager uses it to unpack the ORBX before uploading.
3. Make sure the drive selected for **Cache Folder** has room for the scene's unpacked files.

## Choose what to send

| Scene                                 | Send to the Manager                                                                                                             |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Octane Standalone or an Octane export | The `.orbx` file.                                                                                                               |
| An Octane scene with separate assets  | The `.ocs` file, with its referenced files still accessible. This route does not require setting **Path to Octane Standalone**. |
| Blender                               | A collected folder containing the `.blend` file and its external assets.                                                        |
| Cinema 4D                             | A collected folder containing the `.c4d` file and its assets, or use the [Cinema 4D Wizard](/docs/tools-and-api/c4d-wizard.md). |

Drag the file or collected folder into the Manager. A folder upload must contain exactly one `.c4d`, `.blend`, or `.ocs` file at its top level. Keep referenced scene files in subfolders and update their links before uploading.

After editing, save the scene and submit it again. The Manager prepares the files and sends those the network still needs. It may spend time preparing a large scene even when little needs uploading.

{% hint style="info" %}
A ZIP archive is uploaded as one file. A loose `.blend` file is also compressed and uploaded as one file. To reuse individual Blender assets, use a collected folder and keep large textures and caches outside the `.blend` file. Assets packed inside it are sent again whenever that file changes.
{% endhint %}

Uploading a version through the browser uses the full file. See [Scene details and versions](/docs/web-app/scenes-and-versions.md) for that workflow.


---

# 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/prepare-your-scene/differential-uploads.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.