> 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/cost-calculator.md).

# Estimate job costs

Estimate render costs from your computer's OctaneBench score and local render time.

## Use the Cost Calculator

1. Open **Cost Calculator** in the sidebar.
2. Choose **Octane/Cycles** or **Redshift** to match your renderer.
3. Enter **Your OB Score**, the OctaneBench score that measures your computer's rendering performance. Use the score for the computer where you measured the render time. If you do not know it, see [Find your OB score](#find-your-ob-score).
4. Enter the **Number of frames** you plan to render.
5. Enter **Render time per frame** and choose seconds, minutes, or hours.

Estimates appear automatically once all three values are positive. The OB score and frame count must be whole numbers; render time can include decimals. Changing a value updates the estimates.

Use a local render time measured at the quality and resolution you plan to submit. For an animation with varying render times, testing a heavier frame gives a more cautious estimate than using an unusually quick frame.

{% hint style="info" %}
The estimate is not a fixed quote. The final price depends on the actual render time.
{% endhint %}

## Find your OB score

Below the calculator inputs:

* **Find Estimate** opens the OctaneBench results page, where you can look for an approximate score for your GPU setup.
* **Download Benchmark** opens the OctaneBench download page so you can measure your own computer's score.

The score is also used by **Job Cost Estimate** and **Account → Settings → OctaneBench Reference** in the same browser. It affects cost estimates, not the render settings sent with your job.

## Read the estimates

The results compare [render tiers](/docs/web-app/render-tiers.md). Priced tiers show approximate costs in Render Credits. **Trusted Partners** offers **Contact Us** instead of a price.

An estimate above your available credit balance is highlighted. Click **Buy Credits** below the estimates to [add credits](/docs/web-app/render-credits.md).

If **Could not load estimates** appears, change an input to try again.

## Estimate while creating a job

In the **Job Cost Estimate** panel beside the [job creation form](/docs/web-app/create-a-job.md), enter **Your OB Score** and **Render time per frame**, including its unit. The frame count comes from the targets and frame ranges selected in the form.

The displayed frame and job counts help you check the size of a batch before submitting. For scenes with different render times or renderers, use the separate calculator to estimate each scene with its own measurements.


---

# 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/cost-calculator.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.