We created a special Megacalculator to help you figure out the approximate cost of rendering your project.
This is the only reliable way to predict the cost of rendering an image or an animation. The cost is calculated based solely on the rendering time. Each project is unique, so we can’t provide a price range for questions like “Image with 2000 pixels on the wide side” or “the scene contains 2 million polygons”.
To make the calculation, we take the data from your computer and compare it to our servers. For this, we need to know the name of your CPU/GPU (depending on which is used for rendering), the number of images, and how long each frame will render on your computer.
If you are rendering animation, render several frames throughout the whole sequence (for example, each 50th or 100th frame) to calculate the average time of rendering per frame. Rendering frames from different parts of the animation may differ dramatically. If you use Time Limit on your computer, our calculator won’t show the correct result; you’ll have to run tests on the farm to approximate the cost.
If you are rendering a static frame, then use the time predicted by the rendering engine. Make sure you use the same resolution and rendering limits as you’re going to use on the render farm. If your computer is not powerful enough to start rendering your scene, you’ll be able to calculate the final cost only after launching the task on the farm.
To find out the model; of your CPU/GPU, press Ctrl + Shift + Esc and go to the Performance tab. We need the model of your CPU/GPU only to compare its performance with our servers, it will not be used during rendering.
Pick the model of your CPU/GPU in the calculator. Note that desktop and laptop CPUs are sorted into different categories. If your CPU is not on the list, use a Cinebench score instead. For GPU, use Octanebench.
The final calculation will show the approximate cost of rendering your project at the render farm. This value can change because the projected rendering time often differs from the final one. For static images, the difference is minimal, and for animations it directly depends on the difference between separate frames of the sequence.