1. How to estimate the price of the project

For a quick estimate, use our ‘Cost Calculator‘. Please note that all projects vary depending on the complexity of your files, and the estimate is approximate and intended for reference purposes only. This calculator is specifically designed for animations.

To get a more accurate estimation, we highly recommend running a test job with a few typical frames using Incremental Step*

For example:

If you fill in 1 in the incremental step box, frames 0, 1, 2, 3, 4,…etc will be rendered.

If you fill in 100 in the incremental step box, frames 0, 100, 200, etc will be rendered.

Also, there are significant differences between **SuperRendersFarm **and local rendering that you should be aware of.

* On your local farm

When you look at the frame render time on your local machine and see that it takes 5 minutes, for example, it might be different once you render the same frame here.

• On Superrenders Farm

Our system needs to load your scene first, open the scene, render, save the results,… All of those are accountable for rendering time, which may add the total time up.

Especially if you have a messy file or many large scene assets, such as large texture files, the actual time can rise, and you may feel your estimated price seems to be too low.

2. “Frame per node” is a way to save the loading, opening time

Normally, our system assigns one machine to render each of your frames. This can potentially lead to issues with opening file times.

To reduce the total rendering time, you can also refer to the ‘Frame per node‘ option on our ‘Add New Render Job‘ form

With the ‘frames per node‘ option, if you set it to 5, one node will open your scene once and render all five frames in a single turn, saving both the opening time and the rendering cost.

Please note that the speed, when you choose one frame per node, is faster overall and makes it easier to monitor the progress.

It’s up to you to choose between speed and low cost, or the best of both.

Updated on: 24/09/2026