This estimate consists of only render time. It does not include scene loading times, assets loading or any pre-cache for objects

Since your frames may vary from one to another, the estimation isn’t always accurate. However, it should give you a solid idea of what the price would be.

  1. Render a few frames of your scene on your computer
  2. Fill out the info about your CPU
  3. Get average time of the frames you have rendered on your computer and fill it out in the calculator along with the number of frames

Frequently asked questions

Q: What frame time should I put in?
Render a few frames on your PC and get an average of them. That’s the frame time you should put in the calculator.

Q: How to calculate cost for still images?
The calculator works with animations only. To get the cost estimation for a still, do as follows:
First, render a test image with a 1/4 or 1/8 resolution.
Then, multiply the render cost you get by 16 or 64 to get the full resolution cost.

Q: What if my CPU isn’t on the list?
This shouldn’t happen. Try looking through the list again as some models might be placed in a different category (i.e. mobile, server et.c) If your model isn’t on the list, select the one nearest to it. 

For Mac computers, check out this article that will help you find your CPU model How to Find Your Mac’s Exact CPU Model

Q: Is the quote given in the calculator binding by any means?
The estimates generated in the calculator are only there to give you a rough idea of your scene’s cost. However, you should render a few test frames beforehand to get a more accurate cost estimation.

Q: If the calculator says my scene will render 10h, is it the actual render time?
The calculator shows farm render time in a scenario where either 20, 40 or 80 nodes are used in your render job, however, that number may vary. Also, it only shows the time of the nodes when they are rendering. It doesn’t include the farm queue waiting time or the scene loading time.