Free Tool, No Sign-up
Estimate how long your animation will take to render, what it costs in electricity, and how a render farm compares. Enter a frame count and the time one frame takes.
Step by Step
The whole estimate depends on one number: how long a single frame takes at your final settings. Here is how to get it accurately.
Ballpark Reference
Rough time per frame at 1080p on a modern dedicated GPU. Use these only to sanity-check your own test render, not as inputs.
| Scene type | Engine | Rough time / frame | Notes |
|---|---|---|---|
| Simple stylised shot | Eevee | 0.5 – 3 s | Few lights, no heavy shadows |
| Complex scene, many lights | Eevee | 3 – 15 s | Soft shadows, SSR, bloom |
| Product or character shot | Cycles (GPU) | 30 – 120 s | Denoised, ~128 samples |
| Interior / archviz | Cycles (GPU) | 2 – 10 min | Bounced light, glass, many textures |
| Volumetrics or caustics | Cycles (GPU) | 10 – 60 min | Fog, fire, water, high samples |
| Any of the above | Cycles (CPU only) | 3 – 10× slower | Depends on core count vs GPU |
Hardware changes these numbers by an order of magnitude. A laptop iGPU and a workstation with two high-end cards can differ by 20 times or more on the same frame. Always run your own test render.
Cut the Time Down
Before committing to a long job or paying for a farm, most scenes have easy time to claw back.
Common Questions