> 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/web-app/outputs.md).

# Output configurations

Choose image formats and output settings, name rendered files, and resolve conflicting outputs.

An output configuration tells the renderer how to save your frames, including the image format and bit depth.

## Add an output

In [Create Job](/docs/web-app/create-a-job.md), scroll to **Outputs** and click **Add Output**. Choose the image settings, then click **Save output** to collapse the editor. Click the output row to edit it again, or use **Remove output** inside the editor.

Some Cinema 4D scenes offer **Regular image** and **Multipass image** checkboxes instead. Select either or both, then edit their settings. **Multipass image** is offered when the selected targets contain passes.

| Scene shown in the form             | Output choices                                                               |
| ----------------------------------- | ---------------------------------------------------------------------------- |
| Octane Standalone                   | Several outputs with different image settings, or one **Deep Image** output. |
| Cinema 4D with Octane               | One output.                                                                  |
| Cinema 4D with Redshift or Physical | At most one **Regular image** and one **Multipass image**.                   |
| Blender                             | One output.                                                                  |

If you are configuring targets individually, each selected target needs at least one output.

## Choose image settings

The editor shows the controls available for the selected application, renderer, and format.

| Control         | Available choices                                                                                                                         |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Format**      | **PNG** or **EXR** for regular images. Physical multipass images use EXR.                                                                 |
| **Bit Depth**   | **8-bit** or **16-bit** for PNG; **16-bit** or **32-bit** for EXR.                                                                        |
| **Color Space** | For Octane Standalone and Cinema 4D with Octane, PNG uses **sRGB**. EXR offers **sRGB**, **Linear sRGB**, **ACEScg**, and **ACES2065-1**. |
| **Compression** | EXR compression choices, including **ZIP**, **PIZ**, **DWAA**, and **DWAB**.                                                              |
| **Multilayer**  | Available for Octane and Blender EXR outputs and for Cinema 4D multipass EXR. Physical multipass EXR always uses multiple layers.         |
| **Tonemapped**  | Available for Octane Standalone and Cinema 4D Octane outputs.                                                                             |
| **Metadata**    | Available for Octane Standalone outputs.                                                                                                  |

For choosing EXR settings for compositing, see [EXR output and DWA compression](/docs/prepare-your-scene/exr-and-dwa-compression.md). Select the passes to render in [Advanced Options](/docs/web-app/render-settings.md#choose-render-passes).

## Name the output files

Under **Output File Names**, edit the text between the labels. Click **Scene Name**, **Target Name**, **Pass**, **Frame Number**, or **Extension** above the pattern to insert that part of the filename.

You can mix these labels with text such as a shot name, underscores, or dots. **Target Name** uses the render target, Cinema 4D take, or Blender scene name. Use Backspace or Delete beside a label to remove it.

When the pattern includes **Frame Number**, **Frame padding** sets the number of digits, from 1 to 10. A padding of 4 displays frame 1 as `0001`. This is separate from [changing the starting frame number](/docs/web-app/render-settings.md#start-output-numbering-at-a-different-frame).

Check **Example** beneath the editor to see how the pattern fits together. Its sample names illustrate the pattern; they are not a preview of your scene's actual filenames.

## Deep Image and duplicate outputs

**Deep Image** is available for Octane Standalone. Choose it in **Format**. Controls such as bit depth and color space disappear because they do not apply to this output.

{% hint style="warning" %}
Deep Image must be the job's only output. Remove other outputs before creating the job.
{% endhint %}

If you add several regular outputs, give each a different combination of image settings. Changing only the filename pattern is not enough. If the app reports duplicate configurations, change an image setting or remove the duplicate.


---

# 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/web-app/outputs.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.