Skip to content
Omnikalc

Render time calculator: how long and how much will your animation take to render?

Enter the animation length, frame rate, time per frame and number of machines to get the total render time, the energy used and the cost.

Updated on
Your inputs
s

Value out of range

Value out of range

min

Value out of range

Value out of range

%

Value out of range

W

Value out of range

$ /kWh

Value out of range

$

Value out of range

Results

Time until the render is finished

17:36:00

Frames to render
720
Machine-hours of rendering
52.8 h
Energy used
23.8 kWh
Electricity cost on your own machines
$3.56
Cost on a cloud render farm
$47.52

Animations and architectural walk-throughs can take hours or days to render, and the cost is easy to underestimate. The render time calculator takes the animation length, the frame rate, the time per frame, the number of machines, an extra percentage, the power draw, the electricity price and a cloud price, and gives the frames, the machine-hours, the time until finished, the energy used, the electricity cost and the cloud cost.

How the calculation works

  • Enter the length of the animation in seconds and the frames per second to get the number of frames.
  • Enter the render time per frame on one machine, from a test render, and the number of machines or GPUs working in parallel.
  • Add an extra percentage for test renders, re-renders and fixes, which are almost always needed.
  • Enter the power draw and the electricity price for your own machines, and the hourly price of a cloud farm to compare.

Example

A 30 s animation at 24 fps has 720 frames. At 4 min per frame that is 48 machine-hours, and 10 % extra makes 52.8 machine-hours. On 3 machines the render is done in 17.6 hours. At 450 W each, it uses 23.8 kWh, which costs $3.56 of electricity at $0.15 per kWh. A cloud farm at $0.90 per machine-hour would cost $47.52.

Why it matters

Knowing the render time before you start lets you plan a schedule, choose between lowering the quality and adding machines, and compare your own hardware with a cloud farm. Small changes to the frame rate or the time per frame change the total by hours.

Good to know

The estimate is linear: it multiplies frames by the average time per frame and does not include the time to load the scene, to transfer files or to queue on a shared farm. It ignores the purchase price of your hardware and the cooling of the room. Treat it as a planning figure.

The computer energy cost calculator estimates the power bill of a machine, the frame time calculator relates FPS to milliseconds, and the video file size calculator sizes the final output.

Frequently asked questions

How do I estimate the render time per frame?

Render a few representative frames at the final resolution and quality settings, including the heaviest ones, and average their times. Frames with heavy lighting, volumetric effects or many reflections take much longer than simple ones, so a single test frame can mislead.

Why add an extra percentage?

Almost every project needs test renders, corrections, or a re-render after a mistake. Ten to thirty percent is typical, and more for complex scenes or when the client changes the brief. It is better to plan for it than to be surprised close to the deadline.

Does rendering on more machines scale perfectly?

For frame-by-frame rendering of animation, nearly, because each frame is independent, so ten machines take about a tenth of the time. A few seconds per frame are lost loading scenes and textures. A single huge frame does not scale in the same way unless the renderer can split it into tiles.

Is a cloud render farm cheaper than my own machines?

For a one-off project it often is, because you pay only for the time you use and get many machines at once. For frequent heavy rendering, owning hardware can be cheaper once you include the purchase price, which this calculator does not. It also ignores cooling, which adds to the electricity of your own machines.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.