A 3D render time calculator works out how long a set of frames takes to render, how long each frame may take to meet a deadline, or how many machines you need. Choose what to find, enter the known values and press Calculate.
How to use the 3d render time calculator
- Choose what to find.
- Enter the time per frame, the number of frames and the machines, or the deadline, as the boxes show.
- Add the frames per second if you want the length of the film.
- Press Calculate.
The main formula
The total render time is the time per frame times the number of frames, divided by the number of machines. This is our own working, and it rests on one fact about rendering: frames can be calculated independently of each other [1], so a farm can hand different frames to different machines. If one machine renders every frame, the machines factor is 1. Adding machines divides the time, if the work can be shared perfectly. The total time can also be written as a finish time minus a start time.
A worked example
Take a time per frame of 15 minutes and 50 frames on one machine. This example is our own. The total is 15 × 50 = 750 minutes, which is 12.5 hours, or about 0.52 days. The calculator shows the time in minutes, hours and days, so that you can read it in the unit that suits you. With two machines, the same job takes 375 minutes, or 6.25 hours.
The time allowed per frame
If you have a deadline, you may want to know how long each frame can take. With 50 frames, 2 machines and 8 hours, the answer is 19.2 minutes per frame. The rearranged formula is the maximum time per frame, equal to the total time times the machines, divided by the frames. The rearrangement is our own working.
The machines needed
To find the number of machines, divide the total work, the time per frame times the frames, by the time available, and round up. This is our own rearrangement of the main formula. It assumes that the machines run around the clock and have equal power. For 15 minutes, 50 frames and 8 hours, the work is 750 minutes against 480 minutes, which is 1.56, so you need 2 machines.
A film-sized example
A large job shows the same rules at scale. Suppose a film-sized job has 114,240 frames, 117 machines and 1,084 days of rendering. Convert 1,084 days to 26,016 hours, choose the time allowed per frame, and the calculator gives 1,598.67 minutes, which is 26.6445 hours per frame. These figures are an illustration of our own, and we do not claim that they describe any real film. The point is that a long render is mostly a matter of many frames and long frame times, not of one slow step.
Rendering a film or an animation
The length of the film is the number of frames divided by the frames per second, where the frame rate is the rate at which consecutive images are displayed [2]. A rate of 24 frames per second became standard for 35 mm sound film [2]. At 24 frames per second, the 50 frames of the first example last about 2.08 seconds, so even a short clip needs many frames. Fill in the optional frames-per-second box to see the length of the film in the results. The division itself is our own working.
The assumptions
The calculator assumes that all the machines have the same power and run all day. A real render farm uses queue software that distributes the work to many processors [1], and it does not model the time that it takes to share the frames, to load the scene or to join the results. If some machines are slower, the real time is longer than the one shown. Treat the result as the best case, and add a margin to a deadline that matters.
What changes the time per frame
The time per frame is the value that you must estimate yourself. Wikipedia notes that total rendering time and cost are hard to predict [1]. In practice, the scene, the resolution and the number of samples all matter, and a lower quality setting lowers the time per frame. A test render of a few frames gives the best figure to use. The calculator then scales that figure to the whole job.
Checking a plan
Use the three modes together. Start with the total time on your present machines. If it is too long, switch to the machines needed for your deadline. Then check the time that each frame may take, and ask whether a simpler scene or a lower setting would fit. A quick change in one box shows how sensitive the plan is to each value.
Limits
The formulas are simple divisions and are exact for the stated assumptions. They are not a prediction for a particular program or a render farm. The calculator has no electricity cost field, because we have no formula for it. The deadline must be in hours, and the number of frames and of machines must be whole numbers.
Planning with a test render
The best way to get the time per frame is to render a few typical frames, including the hardest ones, and average their times. Enter that average in the calculator and the result will be much closer to the real job than a guess. This advice is our own. Remember to test the final settings, since a draft setting gives a time that is far too short.
Common mistakes
- Entering the time per frame in hours. Use minutes.
- Using the deadline in days. Convert it to hours.
- Forgetting to round the machines up. Half a machine does not exist.
- Assuming perfect sharing. Real machines lose some time.
What next
Use this often? Add 3d Render Ti to your Home screen.
Frequently asked questions
What is a 3D render time calculator?
A tool that finds the total time to render a set of frames, the time allowed per frame or the machines needed.
What is the render time formula?
Total time equals the time per frame times the frames, divided by the machines.
How do you find the machines needed?
Divide the total work by the time available and round up.
Does it assume the machines run all day?
Yes, and that they are equally fast. Real machines can differ, so treat the result as a best case.
Can it give the length of the film?
Yes. Enter the frames per second, and it divides the frames by it.
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.