Quick Presets
Render Job
Frame count
frames
Render time / frame
min @ 1080p
Output resolution
Render nodes
machines
Nodes
10
Real-World Factors
Scaling efficiency
90%
Overhead / retries
8%
Cost is billed per node-hour, the standard render-farm unit. Higher resolutions multiply render time per frame. Scaling efficiency reflects that more nodes rarely give perfectly linear speed-up, and overhead covers failed frames, asset sync and retries.
Estimated Render Cost
£--
on the selected farm tier
Wall-clock time
--
Total node-hours
--
Cost by farm tier (click to select)
Budget CPU
£/hr
--
shared CPU nodes
Standard GPU
£/hr
--
mid-tier GPU nodes
Job summary
Effective time/frame
--
at chosen res
Single-node time
--
1 machine
Wall-clock
--
nodes in parallel
Cost / frame
--
selected tier
Wall-clock time vs node count
More nodes cut wall-clock time but the cost in node-hours stays broadly flat (it even rises slightly as scaling efficiency drops). Speed is what you buy, not savings.
Tier
Standard GPU
Wall-clock
--
Job Breakdown
Frames--
Resolution--
Res multiplier--
Raw render hours--
With overhead--
Active nodes--
Cost Range
Budget CPU--
Standard GPU--
High-End GPU
Farm Tips
Cost tracks node-hours. Adding machines speeds delivery but the total billed hours barely change.
Test one frame first. Time a single frame at final settings before committing the whole sequence.
Mind the overhead. Failed frames, licensing and asset upload all add to the bill. Budget a buffer.