> 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/tools-and-api/c4d-wizard.md).

# Cinema 4D Wizard

Install the Cinema 4D Wizard, check a scene, and package it or send it to Render Network Manager.

## Install the plug-in

1. Download the ZIP from the [Render Network Wizard releases](https://github.com/rendernetwork/c4d-plugin/releases/latest).
2. Close Cinema 4D and extract the ZIP.
3. Copy the extracted plug-in into Cinema 4D's `plugins` folder. Create the folder if it does not exist.
4. Start Cinema 4D and open **Extensions → Render Network Wizard**.

The Wizard is available for Windows and macOS. Its [installation guide](https://renderfoundation.com/c4d-wizard) lists Cinema 4D 2022 onward; check [supported software](/docs/get-started/supported-software.md) separately for versions available to render on the network.

## Check and package a scene

{% stepper %}
{% step %}

## Review the scene

Open the scene in Cinema 4D, then open the Wizard. Check the detected renderer, active take and camera, frame range, and resolution.

The native Cinema 4D workflow supports scenes prepared with [Octane](/docs/prepare-your-scene/cinema-4d-octane.md) or [Redshift](/docs/prepare-your-scene/cinema-4d-redshift.md).
{% endstep %}

{% step %}

## Run the checks

Click **Check Project**. Resolve missing assets, uncached simulations, and other warnings before exporting. Use [Cinema 4D scene preparation](/docs/prepare-your-scene/cinema-4d.md) for asset collection and caching guidance.
{% endstep %}

{% step %}

## Choose how to send it

* For a browser upload, enable **Pack Scene into .zip for the Render Network** and run the check and packaging process. Upload the resulting ZIP using [Upload Scenes](/docs/web-app/upload-scenes.md).
* To collect the project without a ZIP, use **Collect**. The Wizard saves the collected project in its export folder.
* To send the project to the desktop app, follow the Manager workflow below.

Set backup and export locations in **General Settings**.
{% endstep %}
{% endstepper %}

## Use it with the Manager

Install [Render Network Manager](/docs/tools-and-api/manager-app.md), open it, and sign in before sending a scene from Cinema 4D.

In the Wizard's **Manager App** tab:

1. Enable **Upload Only** to upload the scene and choose render settings in the Manager later. Disable it if you want **Render Scene** to submit the render as well.
2. Review the job settings. If you want automatic local downloads, set the download folder.
3. Click **Render Scene** and follow progress in the Manager's **Activity** panel.

For repeated scene revisions, see [Differential uploads](/docs/prepare-your-scene/differential-uploads.md).

## Split a long Octane export

The **ORBX Export** tab can split an animation into shorter sections. Choose the number of frames per section. If motion blur needs frames before or after a section, include those extra frames, also called handles.

Check each exported section in Octane Standalone before uploading, particularly its first and last frames. See [Cinema 4D with Octane](/docs/prepare-your-scene/cinema-4d-octane.md) for the ORBX 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/tools-and-api/c4d-wizard.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.
