> 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/getting-started/using-blender-cycles-on-the-render-network/using-differential-uploading-with-blender-cycles.md).

# Using Differential Uploading with Blender Cycles

Accelerate your Workflow with Differential Uploading

#### **Blender Differential Upload – How It Works**

The Render Network Manager supports differential uploads for Blender scenes by tracking file-level changes between render jobs.

**Key behavior:**

* Each uploaded file is hashed and cached
* On subsequent renders, only files with detected changes are uploaded
* Unchanged files are reused automatically<br>

**Blender-specific notes:**

* External assets (textures, caches, linked files) benefit fully from differential upload
* When assets are packed into a .blend, the entire .blend file is treated as a single unit
* Any modification to packed data requires re-uploading the .blend file<br>

**Recommended workflow:**

* Keep heavy assets external when iterating
* Use packed assets for portability when needed, understanding the tradeoff<br>

This enables significantly faster Blender iteration on the Render Network, especially for lighting, camera, and animation passes.<br>

**Full release notes and improvements:**

<https://github.com/nordskill/render-network-manager-app/releases>

\
**Try Today** at <https://render.x.io/>

<br>


---

# 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/getting-started/using-blender-cycles-on-the-render-network/using-differential-uploading-with-blender-cycles.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.