The problem
People estimate animation time by staring at the first frame. That frame is only a sample. A 10-second shot at 24 fps is 240 frames. If one frame takes 40 seconds, the local job is 2 hours 40 minutes on one machine, before retries, crashes, or overnight heat.
Cause
Total local time ≈ (fps × shot seconds) × time per frame.
- 24 fps × 8 seconds = 192 frames. 30 fps × 8 seconds = 240 frames.
- A preview at 64 samples is not the final pass at 512 samples.
- Motion blur, volumes, and hair usually raise time per frame after the first still looks “done.”
Calculator
Enter frames and time per frame. The tool reports local duration, a human-readable total, an independent-machine illustration, and an optional target completion. It never multiplies frames by a public dollar rate.
Local total render time
50 minutes3000.00 seconds on one machine
- Frames
- 250
- Time per frame
- 12 seconds
Parallelism illustration
If independent machines each took the same time per frame and there was no queue, the wall clock would divide like this. This is planning math, not FARPY routing.
- 1 independent machine
- 50 minutes
- 2 independent machines
- 25 minutes
- 4 independent machines
- 12 minutes 30 seconds
- 8 independent machines
- 6 minutes 15 seconds
Get exact quoteUpload your .blend. Inspect returns a locked quote. This calculator estimates time only.
Measurement vs executionSee how this GPU performs. Need the render finished?
BenchMork measures GPU performance on a frozen benchmark. FARPY executes your Blender file, shows an exact quote, and returns a receipt. A verified benchmark is not a render-time or price guarantee.
Need the actual render finished?
Upload the .blend. FARPY inspects it and returns a locked quote before start. The accepted price does not increase after you approve it.