> 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/getting-started/how-to-get-started/select-rndr-tier.md). # Select Render Tier Picking the settings that are right for you Render Network's pricing is structured in a multi-tier format, based on three criteria: rendering speed, security, and price. To learn more about how the multi-tier pricing came about, read our in-depth breakdown (note that the article describes the original tier structure; the names, prices and limits on this page are the current ones): ### Available tiers Three tiers are currently available: **Economy**, **Standard** and **Performance**. **Enterprise** is planned for a future release. | Tier | Previously | Price per 400 OBh | OctaneBench range | Node requirements | Max nodes per job\* | | ----------- | ------------------------ | ----------------- | ----------------- | -------------------------------------------------------------------------------------- | ------------------- | | Economy | Tier 3: Economy | €0.60 | Up to 600 OB | Maxwell and Pascal GPUs excluded; minimum node VRAM selectable up to 11 GB | 25 | | Standard | Tier 2: Priority | €1.20 | 601 to 6,000 OB | 8 GB+ VRAM (12 GB+ above 2,000 OB), 32 GB+ RAM | 50 | | Performance | New | €2.40 | 6,001+ OB | 16 GB+ VRAM (24 GB+ above 16,000 OB), 64 GB+ RAM, up to 14 GPUs per machine for Octane | 100 | | Enterprise | Tier 1: Trusted Partners | €4.00 | – | To be released | – | \*For scenes under 2 GB. See "Node limits per tier" below. OBh stands for OctaneBench hours. 400 OBh is roughly one RTX 5060 (416 OB) running for an hour. To determine which tier is best for your job, factor in three criteria: *rendering speed, security, and price.* * **Performance** gives you the strongest nodes on the network, for extreme jobs: 8K, very high resolutions, domes, immersive formats, and heavy scenes. It is priced at €2.40 per 400 OBh. * **Standard** is the workhorse for most production jobs, including Redshift. A tighter hardware spec means more consistent node performance and more predictable costs. It is priced at €1.20 per 400 OBh. * **Economy** is the most affordable way to render, for jobs that aren't time sensitive. Economy nodes now score up to 600 OB, twice the previous ceiling (300 OB), so the fastest Economy nodes are about twice as fast as before. It is priced at €0.60 per 400 OBh. We recommend not using Economy for work on a tight deadline, as queue priority and node power are not guaranteed. > **Coming from the old tier names?** Tier 3 (Economy) is now **Economy**, and Tier 2 (Priority) is now **Standard**. Performance is a new tier above Standard. ### Selecting a tier Once you've determined which tier you would like to render your job on, simply: 1. Select the tier from the right side menu 2. Select the payment method 3. Select preferred frame approval method ### Node limits per tier The number of nodes a job can be sent to depends on the tier and the size of your project. Smaller scenes can use more nodes. From 2 GB upwards, the limit drops as the scene gets larger, so that nodes are distributed fairly across many jobs. These are maximum values; the number of nodes your job actually receives depends on network availability. | Project size | Economy | Standard | Performance | | ------------ | ------- | -------- | ----------- | | Up to 1 GB | 25 | 50 | 100 | | 2 GB | 25 | 50 | 50 | | 3 GB | 25 | 33 | 33 | | 4 GB | 25 | 25 | 25 | | 5 GB | 20 | 20 | 20 | For scenes larger than 5 GB, all tiers follow the same curve and the node limit continues to decrease as project size grows. Limits apply to users with normal reputation values; higher reputation users have higher ceilings. ### Bandwidth charging In addition to the render cost, a bandwidth charge covers the cost of transferring your scene assets to render nodes. * **Rate:** 0.09 credits per GB of scene assets transferred to nodes * **Applies in every tier** * **Charged only for successfully rendered frames** The amount of data transferred depends on your project size and on how many nodes your job is sent to, which is set by the tier and project size (see "Node limits per tier" above). **Estimated bandwidth cost = project size (GB) × number of nodes × 0.09 credits** The examples below assume the job is sent to the full node limit for its tier and project size. | Example | Tier | Project size | Nodes | Data transferred | Bandwidth cost | | ------- | ----------- | ------------ | ----- | ---------------- | ---------------------------- | | A | Economy | 120 MB | 25 | 3 GB | 3 × 0.09 = **0.27 credits** | | B | Standard | 500 MB | 50 | 25 GB | 25 × 0.09 = **2.25 credits** | | C | Performance | 1 GB | 100 | 100 GB | 100 × 0.09 = **9 credits** | Keep in mind that bandwidth costs will mostly appear at the start of the job and should only slightly increase with job progression, since nodes will re-use the already cached assets. --- # 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/getting-started/how-to-get-started/select-rndr-tier.md?ask=&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.