Render farm cost comes down to one calculation: how much computing your job consumes, multiplied by the rate you pay for it. The rate is easy to find on a price page. The consumption is the hard part, and it is why two quotes for the same shot can look nothing alike.
The good news is that you can get a useful estimate before uploading anything. All you need is a realistic test frame, your frame count and an understanding of how the farm bills its work.
The Three Ways Farms Charge
Commercial render farms generally use one of three billing units. Knowing which one you are looking at is essential, because the headline rates cannot be compared directly.
| Billing unit | What it measures | Usually used for | Watch out for |
|---|---|---|---|
| GHz-hour | CPU clock speed multiplied by cores and time | CPU rendering | Hard to predict without a test |
| OctaneBench-hour | GPU benchmark score multiplied by time | GPU rendering | Depends on the GPU assigned |
| Machine-hour | A fixed price per server per hour | Rented servers and IaaS farms | You pay for idle and setup time |
When we checked commercial price pages in November 2026, published CPU rates ranged from a fraction of a cent to several cents per GHz-hour, depending on provider and priority. Rates change often, so use each provider’s current page for any real budget.
Work Out a Job in Five Steps
- Render a test frame from one of your heavier shots, not the easiest one.
- Note the render time and the CPU that produced it.
- Multiply cores by clock speed to get the machine’s GHz.
- Multiply that by the frame time in hours to get GHz-hours per frame.
- Multiply by your frame count and the farm’s rate.
A Worked Example
Take a 16-core CPU at 3 GHz, which gives 48 GHz. If a frame takes 20 minutes, that is one third of an hour, so each frame uses 16 GHz-hours.
At an illustrative rate of $0.02 per GHz-hour, each frame costs $0.32. A job of 2,400 frames would be 38,400 GHz-hours, or about $768. The rate here is only an example, chosen to keep the arithmetic simple.
This estimate is rough, because a farm’s CPUs will not match yours and clock speed is an imperfect measure of real speed. Many farms offer a small trial or an estimation tool, so test a few frames on the farm itself before committing to the full sequence.
Priority Can Change the Bill More Than the Hardware
Many farms sell the same hardware at different prices depending on how soon you want the job. Higher priority gives you more machines at once and a shorter wait, at a higher rate.
This is worth planning for. If you start a week before delivery, a low-priority queue may be enough. If you start the night before, you may pay several times as much for the same frames, so a late start is often the most expensive decision in the budget.
Costs That Do Not Appear in the Per-Frame Rate
The render itself is rarely the whole bill. Before comparing farms, check each of these:
- Plugin and renderer licenses: some farms include them, while others charge extra.
- Upload time: large scenes and textures may take hours on a slow connection.
- Failed frames: a missing texture can burn money across a whole sequence.
- Re-renders: client changes mean paying for the same shot twice.
- Storage and download: some providers charge to hold or retrieve output.
- Minimum spend: credit packages may leave unused balance behind.
Failed frames deserve special care. Render a small spread of frames from the start, middle and end of the sequence and inspect them before releasing the full job.
Comparing a Farm With Rendering Locally
Local rendering feels free, but it has its own costs. The biggest is that your workstation is tied up while it renders.
Continuing the example above, a single machine would need 800 hours for 2,400 frames at 20 minutes each. That is over 33 days of continuous rendering, which settles the question for most deadlines.
| Factor | Render farm | Local workstation | Rented cloud GPU |
|---|---|---|---|
| Upfront cost | None | Already paid, or high | None |
| Speed at scale | Very high | Limited to your hardware | Depends on how many you rent |
| Setup effort | Low | Lowest | Medium to high |
| Best for | Deadline-driven sequences | Stills and short tests | Custom software setups |
If you need control over the software on the machine, compare this with our guide to renting a cloud GPU as a freelancer. It shows how to judge the cost per finished frame instead of the cost per hour.
How to Reduce the Bill
The cheapest frame is the one you optimize before uploading. A few changes tend to matter most:
- Reduce samples where denoising can cover the difference.
- Render heavy shots in layers, so a change does not mean re-rendering everything.
- Test at low resolution, then send a short high-resolution sample.
- Remove unused assets to shorten the upload.
- Check for fireflies and artifacts first, using our guide to troubleshooting ray tracing artifacts.
Frequently Asked Questions
How much does a render farm cost per frame?
There is no fixed price. It depends on frame time, the billing rate and priority. Using the example above, a 20-minute frame on a 48 GHz machine costs $0.32 at $0.02 per GHz-hour.
Are render farms cheaper than buying a workstation?
For occasional big jobs, usually yes, because you pay only when rendering. If you render all year, owning hardware can work out better. Compare your real yearly render hours.
Why was my final bill higher than the estimate?
The most common reasons are heavier frames than the test, failed frames, higher priority or re-renders. Testing a spread of frames across the sequence narrows the gap.
Do render farms charge for failed frames?
It varies by provider. Some charge for compute that was used, whatever the result. Read the provider’s policy before starting a long job.
Next Step
Render one heavy test frame and enter the time into our render time and output storage planner to see the total machine hours. If the job is too big for your deadline, read our guide to scaling a render farm around a deadline.
