This render farm cost calculator turns a few test frames into a cost estimate. Time a few frames on your own machine, enter the numbers, and see what the same job would cost under the three common billing models: GHz-hours for CPU farms, OctaneBench-hours for GPU farms, and hourly machine or card rental. Results are planning estimates, not quotes.
New to farm billing? Read how render farm pricing works, compare providers on the render farm comparison page, or open a software guide for Blender, Redshift or Corona.
Most farms bill in one of three ways: GHz-hours or core-hours for CPU rendering, OctaneBench-hours for GPU rendering, or a fixed price per machine or card per hour. Each model multiplies a measure of hardware capacity by time, so the same job can cost different amounts depending on which unit a farm uses.
Farms measure hardware their own way, add priority multipliers or minimum charges, and may run your scene faster or slower than your workstation. A test render on the target farm is the only reliable check before a full job.
On remote machine rental the meter usually runs from start to shutdown, which includes installing software and transferring files. Managed render farms usually charge only for render time. Check each provider’s billing terms.
Providers are listed alphabetically. Presets cover only rates RadarRender read on official pricing pages on the date shown, in the currency each page uses; nothing is converted. A farm missing from a list either uses a unit the calculator does not cover or did not show a readable rate. For any other farm, choose “Custom rate” and enter its published price.
Sorry, the comment form is closed at this time.