# Using Differential Uploading with Blender Cycles

#### **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: 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:

```
GET https://know.rendernetwork.com/getting-started/using-blender-cycles-on-the-render-network/using-differential-uploading-with-blender-cycles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.