> 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/creating-large-productions-on-the-render-network/scene-packaging-and-optimization.md).

# Scene Packaging & Optimization

Tips for packaging and optimizing scenes for large-scale renders

#### 🔷 Cinema 4D (Octane or Redshift)

* Use the **C4D Wizard Plugin** (inside Cinema 4D):
* Checks for missing textures and non localized links
* Identifies uncached objects
* Flags unsupported plugins
* Preps ZIP file automatically
* Can publish files directly to the Manager App with API Access without the need to ZIP
* Drag the ZIP into the [**Manager App**](/getting-started/render-network-tutorials/lmi-houdini-tools-or-unlocking-octane-and-render-network-capabilities-with-andrey-lebrov.md) for seamless submission

{% embed url="<https://know.rendernetwork.com/getting-started/cinema-4d-on-render-network-guide/c4d-wizard-plug-in>" %}

<figure><img src="https://1286142079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKt2GmpnqwLIsi-Sh1Z%2Fuploads%2Fx7fjcC7H8oG5Ebw0EG7t%2Funknown.png?alt=media&amp;token=8ddd026e-0ab7-4d90-a784-39251d612d6f" alt="" width="563"><figcaption><p>The Render Network <a href="mailto:undefined">Cinema 4D Wizard</a></p></figcaption></figure>

***

#### 🔷 Octane Standalone

* Export your scene as an **ORBX file**.
* Submit via **Manager App, WebApp, or through Octane Standalone**.

Caution: ORBX files bake all geometry and animations into a single heavy package, similar to Alembic caches. For highly dynamic scenes, prefer C4D methods if possible.

***

#### 🔷 Blender (Cycles)

* Pack your Blender project into a ZIP.
* Submit via **WebApp ONLY**.
* Manager App currently does ***not support Blender***.

![](https://1286142079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKt2GmpnqwLIsi-Sh1Z%2Fuploads%2F2KypH3hihEy54TdwXdmA%2Funknown.png?alt=media\&token=59684b6d-721d-424d-b064-4cb1167590f4)

***

#### Scene Optimization Tips

* Reduce unnecessary geometry.
* Use optimized texture resolutions.
* Bake dynamics/particles when possible.
* Remove unused assets and hidden geometry.
* Set correct frame range and output format.
* Verify your render samples balance noise and efficiency.
* Do a test render of a few frames on the network


---

# 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/creating-large-productions-on-the-render-network/scene-packaging-and-optimization.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.