> 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/cinema-4d.md).

# Cinema 4D: prepare a scene

Collect Cinema 4D assets, check takes and XRefs, and package a project for rendering.

For a native Cinema 4D upload, package the `.c4d` file and its assets together in a ZIP.

## Check your takes

In Cinema 4D's **Take Manager**, give each take a recognisable name and check its camera and render settings. A take can inherit these from its parent, so check the result with that take active. See [Maxon's Take Manager guide](https://help.maxon.net/c4d/en-us/Content/html/54507.html).

After processing, the web app lists the available takes when you [create a job](/docs/web-app/create-a-job.md). Each selected take becomes a separate job. Its saved resolution, frame range, and renderer quality settings provide the starting values for the job form.

## Collect the project

Complete any [simulation caching](/docs/prepare-your-scene/caching-simulations.md) before collecting files.

{% stepper %}
{% step %}

## Save a copy with its assets

Use **File > Save Project with Assets** and choose a dedicated folder. Continue working with this collected copy.

This collects external files alongside the `.c4d`; an ordinary save leaves them in their original locations. See [Maxon's file saving guide](https://help.maxon.net/c4d/en-us/Content/html/5595.html).
{% endstep %}

{% step %}

## Resolve missing or misplaced files

Open **Project Asset Inspector**. Fix entries with a red cross or warning symbol before packaging.

* For missing files, select the entries and use **Assets > Relink Assets** to point to the folder containing them.
* For files still outside the collected folder, use **Assets > Consolidate Assets**.
* Check the saved **Path**, rather than **Absolute Path**, to see whether a reference still names a location on your computer. For collected assets that need it, use **Assets > Localize Filenames**.

Save after fixing the references. Maxon's [Project Asset Inspector guide](https://help.maxon.net/c4d/en-us/Content/html/68600.html) explains the status symbols and path controls.
{% endstep %}

{% step %}

## Check and zip the folder

Run the [packaged-copy check](/docs/prepare-your-scene/overview.md#test-the-packaged-copy), then compress the complete project folder as a `.zip`.

Keep the main file easy to identify, for example `ProductShot/ProductShot.c4d`, with textures and caches in their collected subfolders. Keep referenced `.c4d` files under different names.

Follow [Upload Scenes](/docs/web-app/upload-scenes.md), choosing **Cinema 4D** for this archive.
{% endstep %}
{% endstepper %}

## If you use XRefs

Include the referenced `.c4d` files and check the file path on each **XRef** object. Use **Relative to Project** so the reference can follow the collected project folder.

{% hint style="warning" %}
**Save Project with Assets** does not automatically gather dependencies inside referenced scenes. Check the textures, caches, and further XRefs used by each referenced file, and include those too. See [Maxon's XRef file handling](https://help.maxon.net/c4d/2023/en-us/Content/html/46972.html).
{% endhint %}

For renderer-specific checks, continue with [Octane](/docs/prepare-your-scene/cinema-4d-octane.md) or [Redshift](/docs/prepare-your-scene/cinema-4d-redshift.md). The [Cinema 4D Wizard](/docs/tools-and-api/c4d-wizard.md) provides another way to check and package a project.


---

# 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/cinema-4d.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.