> 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/overview.md).

# Before you upload

Check assets, animation, and local renders before packaging your scene for upload.

## Choose the preparation guide

| Your scene                     | Guide                                                                                                                                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cinema 4D project              | [Collect assets and prepare takes](/docs/prepare-your-scene/cinema-4d.md), then check [Octane](/docs/prepare-your-scene/cinema-4d-octane.md) or [Redshift](/docs/prepare-your-scene/cinema-4d-redshift.md) |
| Blender with Cycles            | [Package a Blender scene](/docs/prepare-your-scene/blender-cycles.md)                                                                                                                                      |
| Blender with Octane            | [Export an ORBX](/docs/prepare-your-scene/blender-octane.md)                                                                                                                                               |
| Houdini or Solaris with Octane | [Houdini and Solaris](/docs/prepare-your-scene/houdini-and-solaris.md)                                                                                                                                     |
| Unreal Engine with Octane      | [Unreal Engine](/docs/prepare-your-scene/unreal-engine.md)                                                                                                                                                 |
| Octane Standalone              | [Octane Standalone and ORBX](/docs/prepare-your-scene/octane-standalone-and-orbx.md)                                                                                                                       |

Check [supported software and file formats](/docs/get-started/supported-software.md) before preparing a scene with a different application or renderer version.

## Keep the scene self-contained

Collect linked files into the folder you will package: textures, image sequences, referenced scenes, Alembic files, and volume or simulation caches. Keep each sequence complete, including any frames needed before the shot starts.

Use paths that point into this folder. A path that still points to your desktop, another drive, or a studio server will not travel with the archive. The application guides above explain how to collect and relink files.

For simulation-driven animation, follow [Cache simulations, particles and dynamics](/docs/prepare-your-scene/caching-simulations.md). Custom colour setups have a separate [OCIO guide](/docs/prepare-your-scene/ocio.md).

## Test the packaged copy

1. Reopen the collected scene, or the exported ORBX, rather than the working file it came from.
2. Check for missing-file warnings and render a representative frame. Include one with volumes, displacement, or other demanding effects if the shot uses them.
3. For animation, check the beginning, middle, and end. Jump directly to those frames to check that animation and caches still load correctly.
4. Compare the camera, materials, lighting, colour, and required [passes](/docs/prepare-your-scene/aovs.md) with your local reference render.

An extra check on another computer, or with the original asset locations unavailable, can reveal links that still lead outside the collected folder.

Once the files are ready, follow [Upload Scenes](/docs/web-app/upload-scenes.md). Start with a few representative frames before submitting the full sequence.


---

# 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/overview.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.