Render time calculator
Frames, minutes per frame and machines in, machine hours and clock hours for every pass out.
Send a brief- You enter
- Seconds of 3D, frame rate, minutes per frame
- Also
- Machines rendering at once and full passes
- You get
- Frames, machine hours and clock hours
- Example
- 264 frames x 3 passes = 19.8 clock hours

Calculator
A 3D shot is not finished when it is built. Every frame has to be rendered, often more than once, and a heavy frame can take minutes on one machine. Render time decides when a 3D shot can be reviewed and how many rounds of notes the schedule can hold. This calculator turns seconds of 3D footage into frames, machine hours and clock hours, so the render can be planned before it becomes the reason a delivery date slips.
How to use it
- Seconds of 3D footage. The total screen time of rendered shots. Count only the seconds that need rendering.
- Frame rate. The frames per second of the edit, such as 24.
- Render time per frame on one machine, in minutes. Render one test frame from the heaviest shot and use that time. A guess here makes the rest of the estimate a guess.
- Machines rendering at once. Workstations or render nodes working on the job in parallel.
- Full render passes. How many times the whole sequence is rendered. A first pass for review, a revision pass and a final pass is a common plan.
How the calculation works
- Frames per pass = seconds x frame rate, rounded up to a whole frame.
- Machine hours per pass = frames x minutes per frame / 60.
- Clock hours per pass = machine hours / machines.
- Clock hours for all passes = clock hours per pass x passes. Machine hours for all passes = machine hours per pass x passes.
Machine hours measure the total computing work. Clock hours measure how long you wait for it.
The worked example
Example (fictional). The Orlenna Ridge Bottle spot has 11 seconds of 3D: the exploded view of the bottle wall (5 seconds), the 3D bottle in the runner’s hand (3 seconds) and the packshot (3 seconds). At 24 fps that is 11 x 24 = 264 frames per pass.
At 6 minutes per frame on one machine, one pass is 264 x 6 / 60 = 26.4 machine hours. Spread across 4 machines, it takes 6.6 clock hours. Three passes take 19.8 clock hours and 79.2 machine hours.
Reading the result
Clock hours are the number for the schedule. In the example, 19.8 hours of rendering sits inside the animate and render window (weeks 4 to 6 of the 8-week plan) with room to spare, because renders can run overnight. The time that usually decides the schedule is the review between passes: a pass cannot start until the notes on the previous one are in.
Machine hours are the number for the budget when render time is bought or charged by the machine hour, and a check on whether the job fits the hardware available.
The per-frame time is the most sensitive input. Doubling it to 12 minutes doubles every result, and so does doubling the seconds of 3D. Adding machines shortens the clock hours but not the machine hours.
A common way to save passes is to approve animation and camera moves on a fast, untextured greycard or clay render before any full render. Changes found at that stage cost minutes instead of a full pass. The how we work page shows where that review sits in the Develop and Make stages.
Limits
- Frames are assumed to split evenly across machines, with no failed frames. In practice some frames fail or need re-rendering, so add a margin.
- Render time per frame varies across shots. An exploded view with glass and metal can take far longer than a simple packshot, so test each heavy shot rather than averaging.
- Separate compositing passes (shadows, reflections, mattes rendered as their own layers) add render time that is not counted unless you include it in the minutes per frame.
- Simulation, caching and the time to build the 3D model are not counted. The model is a separate line in the production budget worksheet.
- Re-renders after late notes, or for a new product color, are extra passes. Count them if the plan expects them.
Related decisions
The seconds of 3D come from the blend map, which decides which shots are rendered and why; see 3D and CGI and mixed-media work, where a rendered product sits inside filmed footage. The frame and timecode calculator converts between seconds, frames and timecode at other frame rates. The render plan also feeds the 3D line of the video budget calculator, and the full Orlenna schedule is on the example campaign page.
If your brief includes product renders, send a brief with the CAD or product drawings you have. The production plan returns a render plan with the passes and review points in the schedule.