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

# Blender with Cycles

Pack a Blender Cycles scene, include external sequences and caches, and prepare its ZIP archive.

{% stepper %}
{% step %}

## Save the scene in its upload folder

In Blender, set **Render Engine** to **Cycles** and save the `.blend` in a dedicated folder. If the file contains several Blender scenes, check each scene's camera, resolution, frame range, and samples.

The web app lists the Blender scenes as separate choices during [job creation](/docs/web-app/create-a-job.md). Their saved settings provide the starting values for each job.
{% endstep %}

{% step %}

## Pack images and collect external files

Choose **File > External Data > Pack Resources**, then save the `.blend` again. For linked Blender libraries, **Pack Linked Libraries** is a separate command in the same menu. See [Blender's packed data guide](https://docs.blender.org/manual/en/latest/files/blend/packed_data.html).

Keep files that remain external in subfolders alongside the `.blend`, including image sequences, Alembic files, volume sequences, and [simulation caches](/docs/prepare-your-scene/caching-simulations.md). Preserve their folder structure when creating the ZIP.

For external references, use **File > External Data > Make Paths Relative**. Some Blender versions label this **Make All Paths Relative**. Then run **Report Missing Files** from the same menu, fix any missing references, and save. Blender's [External Data commands](https://docs.blender.org/manual/en/latest/interface/window_system/topbar.html#external-data) explain the path options.

{% hint style="info" %}
A relative path can still point outside the upload folder. Check that the files themselves are inside the folder you are going to zip.
{% endhint %}
{% endstep %}

{% step %}

## Check the copy and create the ZIP

Run the [packaged-copy check](/docs/prepare-your-scene/overview.md#test-the-packaged-copy). For example, your upload folder might contain:

```
ProductShot/
  ProductShot.blend
  textures/
  image-sequence/
  volumes/
  caches/
```

Use only the folders your scene needs. Compress the complete folder as a `.zip`, then follow [Upload Scenes](/docs/web-app/upload-scenes.md) and choose **Blender** for the archive.
{% endstep %}
{% endstepper %}

## Check image sequences

Keep all frames of a texture or background sequence together and preserve their numbered filenames. Load it as an **Image Sequence** in Blender and check its start frame, length, and offset against the scene's timeline. For a sequence used in a material, make those checks on the image texture node. See [Blender's image texture controls](https://docs.blender.org/manual/en/latest/render/shader_nodes/textures/image.html).

Set up [render passes](/docs/prepare-your-scene/aovs.md) before saving. The web app lets you review the detected passes, resolution, samples, and frame range in [render settings](/docs/web-app/render-settings.md).


---

# 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/blender-cycles.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.