> 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-tiers.md).

# Render tiers and node requirements

Select a render tier and set the GPU and memory requirements for a job.

In [Create Job](/docs/web-app/create-a-job.md), add an output, then open **Network Settings**.

## Select a tier

Tiers are rendering options with different prices and GPU and memory limits. Choose from the tiers shown for your account.

| Choice in the app            | How to use it                                                                                               |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Tier 1: Trusted Partners** | Click **Contact Us** to discuss the job. This tier cannot be selected directly in the form.                 |
| **Tier 2: Priority**         | Select this tier when you need its wider range of GPU and memory choices.                                   |
| **Tier 3: Economy**          | Select this tier for jobs that fit its GPU and memory limits, then compare its cost estimate with Priority. |

The tier cards show their advertised render capacity and credit rate. Use the [Cost Calculator](/docs/web-app/cost-calculator.md) or the estimate beside the job form to compare the estimated cost of your own scene. A tier's displayed capacity does not give a completion time for an individual job.

## Set node requirements

A node is a computer on the network that renders your frames. Under **Node Requirements**:

* **Maximum number of GPUs per node** limits how many GPUs a rendering machine may have. Leave **Any number** selected if you do not want to set a limit.
* **Minimum Node VRAM** requests machines with at least the chosen amount of GPU memory. Leave **Assign to any available node** selected if you do not want to request a minimum.

The form offers these explicit choices:

| Tier         | Maximum GPUs per node           | Minimum VRAM choices          |
| ------------ | ------------------------------- | ----------------------------- |
| **Priority** | 1–8; Redshift is limited to 1–4 | 3, 6, 8, 11, 16, 24, or 32 GB |
| **Economy**  | 1–4                             | 3, 6, 8, or 11 GB             |

{% hint style="warning" %}
Check the memory needed by your scene before submitting. The form does not confirm that it will fit in the selected VRAM, and insufficient memory can cause frames to fail.
{% endhint %}

If you change tiers after choosing node requirements, check the fields again. A value above the selected tier's limits remains highlighted as an error and must be corrected before creating the job.


---

# 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-tiers.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.