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

# Frames, passes, and render settings

Set quality, resolution, frame ranges, output numbering, job names, and render passes.

These settings appear in [Create Job](/docs/web-app/create-a-job.md). When using individual settings, click the target name before editing its values.

## Quality and resolution

| Setting                           | What to enter                                                                                                                                                                          |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Number of Samples**             | The maximum samples per pixel. Higher values allow cleaner renders but take more rendering work. Enter a whole number from 100 to 80,000.                                              |
| **Error Threshold**, for Redshift | The noise threshold. Lower values allow cleaner renders but take more rendering work. Enter a value from 0.0001 to 1.                                                                  |
| **Resolution**                    | Width and height in pixels. Each must be at least 128; maximum width is 25,200 and maximum height is 20,160. Click **Use Original** to restore the selected target's saved resolution. |

## Choose frames

Each target starts with its saved frame range. If it has no saved range, it uses the scene's available frames.

{% tabs %}
{% tab title="One continuous range" %}
Under **Frame Range**, drag the ends of the range slider to choose the first and last frames. Select **All Frames** to use the full available range.
{% endtab %}

{% tab title="Intervals or separate ranges" %}
Turn on **Advanced** under **Frame Range**.

* Choose **Every** and an interval to render a spaced sequence across the available range.
* Enter ranges and individual frames separated by commas, such as `0-24, 50-74, 100`.
* Choose **All Frames** to return to the complete range.

Check **Total number of frames rendered** beneath the controls.
{% endtab %}
{% endtabs %}

For a still with only one available frame, the panel shows **1 Frame** and has no range controls.

{% hint style="info" %}
With shared settings, leaving the saved ranges untouched keeps each target's own range. A custom range applies to every selected target. Use individual settings if the targets need different frame selections.
{% endhint %}

## Start output numbering at a different frame

1. Under **Frame Range**, turn on **Advanced**.
2. Enable **Begin frame numbering at:** and enter a starting number of 0 or higher.
3. Check **New output frame range** below it.

This changes the numbers in the output filenames while retaining the source frames you selected. For example, source frames 0–24 can be numbered 1001–1025 in your files. Your [output filename pattern](/docs/web-app/outputs.md#name-the-output-files) must include **Frame Number** for this setting to appear in the filenames.

## Job name and frame rate

Expand **Advanced Options**.

* In **Job Name**, enter a name or use `$scene` and `$render_target` to include the scene and target names. For example, `$scene - $render_target - preview` gives each job a name based on its source.
* Leave **FPS** empty to retain the scene's frame rate, or enter a value from 1 to 1,000.

## Choose render passes

In **Advanced Options → Render Passes**, check the passes to render, or use **All**. **Beauty** remains selected when it is available. Other passes can start selected according to the saved scene settings.

Shared settings show only passes present in every selected target. Switch to individual settings to choose from each target's own passes.

If the pass you need is missing, set it up in the source application and upload the scene again. See [AOVs and render passes](/docs/prepare-your-scene/aovs.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/web-app/render-settings.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.