MORI Motion

Blog

What Is a Render Farm?

A render farm is a group of networked computers that render a 3D project together. A film or an animation is thousands of separate frames, and because each frame can be calculated independently of the others, the frames can be shared out across many machines instead of waiting in line on one. A farm can be your own set of computers or an online service that rents you machines by the hour. You need one when the render time on your own computer is longer than the time you have. You do not need one for a single still or a short test. Below: how a farm works, own vs online, what drives the cost, a free check that uses your own numbers, and the limits of a farm.

Written by Marco Mori, 3D artist, Lindau, Germany · Updated 2026-11-16

What is a render farm?

A render farm is a computer system built to render. Wikipedia describes it as a high-performance computer system, for example a cluster, built to render computer-generated imagery. In plain words: many computers doing the same kind of job at once, so one long wait becomes many short ones.

It matters because 3D rendering is slow work. Every frame of a film is calculated from lights, materials and geometry, and the finished animation is made of hundreds or thousands of frames. CGI projects therefore plan render time the way a film plans a shooting day.

How does a render farm work?

A farm works because frames do not depend on each other. Wikipedia notes that frames, and sometimes tiles of a frame, can be calculated independently. That is what makes the work easy to split.

  1. The scene goes to the farm. The scene file, textures, caches and any plug-ins it needs are uploaded or placed on shared storage.
  2. A queue manager splits the job. The article describes a queue manager that distributes the work across the many processors. Frame 1 to 10 go to one node, 11 to 20 to the next, and so on.
  3. Each node renders alone. The nodes barely talk to each other. They read the scene, render their frames and write the images out.
  4. The frames come back. The finished frames are collected, and you download or assemble them.

One part cannot be shared out this way. A simulation such as smoke, fabric or liquid runs frame after frame, because each frame grows out of the previous one. It is calculated first and saved as a cache, and only then does the render of that cache get distributed. That is why simulation-heavy Houdini FX work needs more planning than a product turntable.

Do you need a render farm?

You need one when your own machines cannot finish before the deadline. Everything else is preference. A quick sort:

Situation Own machine Farm
A single still image Usually fine Rarely worth the upload
A short animation, relaxed deadline Fine, let it run overnight Not needed
A long animation, short deadline Too slow The reason farms exist
Many colourways or versions of the same scene Slow, but predictable Useful if the deadline is tight
Several revision rounds with full re-renders Each round eats days Useful, because rounds repeat the whole cost
Heavy simulation Simulate locally, then render Only the render step can be shared out

The numbers decide, not the feeling. Render one typical frame at final quality, time it, and put the result into the check below. I do not publish render times of my own projects because they depend on the scene, so the check starts from your test frame instead of a benchmark.

Free check, no signup

Do I need a render farm for this job?

Enter your own numbers. The start values are only an example, replace them with a test render from your scene. The result is plain arithmetic, frame by frame, not a quote.

Frames per second

Render one typical frame at final quality and time it. A frame with heavy glass or hair is the one to test.

1 means no changes. Every note that changes the image can mean another full render.

Machines are assumed to run around the clock.

One node is one farm machine of about your speed.

A render farm would save the deadline

Frames to render
750 (375 per full render)
On one machine
6.3 days
On your 1 machine
6.3 days of 3 days available
On 20 farm nodes, best case
7.6 h

To meet the deadline you need 3 machines of your speed. A farm is the way to borrow that many machines for a few days.

The farm figure is a lower bound. Uploading the scene, checking it, waiting in the queue and re-running failed frames come on top, and a farm can never beat the time of one frame on one node. Simulations are cached before they are rendered and are not split across nodes.

How much does a render farm cost?

There is no flat price, because a farm bills for the time its machines run for you. GarageFarm is one example of how it looks in practice: you buy credits, pay only for the time you render, pick a priority tier, and are billed by the second. Other farms use different units, so compare the cost of your own job rather than the headline rate.

These factors move the bill:

Cost driver Why it matters
Minutes per frame The base unit. Every extra minute is multiplied by every frame
Number of frames Length times frame rate. A 30 fps film has 25 percent more frames than a 24 fps film of the same length
Full re-renders A change that touches the whole image renders everything again
Priority tier Faster queue position costs more per hour
CPU or GPU nodes The two kinds are billed differently, and your renderer decides which you need
Storage and transfer Large scenes and caches take time and sometimes money to move

The same farm gives you a way to estimate before you commit. GarageFarm advises test-rendering a spread of frames, for example every twentieth frame, and extrapolating, and for stills rendering at a lower resolution. That is also the right way to fill the check above. For the other side of a project budget, see what drives the cost of a CGI commercial.

Own render machines or an online render farm?

Own machines Online farm
Cost shape You buy hardware once You pay when you render
Speed Limited by what you own As many nodes as the farm has free
Control Full, nothing leaves your network Your scene is uploaded to someone else's servers
Setup Software, licences and updates are yours The farm must support your software, version and plug-ins
Transfer None Wikipedia lists slow uploads of large files as a known weakness

The control row matters in client work. A product that is not launched yet is often confidential, and its model is in the scene. Before you upload anything, read the farm's terms and check them against any NDA you signed. For a studio that renders every week, its own machines usually pay off. For a freelancer with an occasional crunch, renting is the more flexible route.

Does a render farm fix everything?

No. Three limits:

  • One frame sets the floor. If a single frame takes four hours, a hundred nodes still need four hours. A farm shares frames, it does not shorten a frame. The check above shows this when the deadline is shorter than one frame.
  • Preparation is not parallel. Modeling, look development, simulation and testing all happen before the farm starts. A farm shortens the last step only. Preparation is where 3D modeling and lighting decisions pay off.
  • Mistakes get multiplied. A wrong material found after a farm run means another run. Cheap test frames and staged approvals are worth more than extra nodes.

After the render, compositing can still fix many things without a re-render, such as colour and depth of field. That is why a good render plan asks which changes can be made in the comp and which reopen the scene.

Which renderers work on a farm?

It depends on the farm, not on the renderer alone. Redshift, the renderer I use with Houdini, is described by its maker Maxon as GPU-accelerated and able to render on the CPU as well, and it works with Houdini, Cinema 4D, Maya and others. A farm still has to offer the exact renderer, version and plug-ins your scene needs. If it does not, the job cannot run there, however many nodes it has. Ask before you upload, with a small test scene.

What should you ask your 3D artist about rendering?

If you hire someone for CGI work, four questions keep render time from becoming a surprise:

  • Does the work render on their own machines or on a farm, and is there a limit on re-renders?
  • How are revision rounds staged, so that a change at the still stage does not become a re-render of a finished animation?
  • Which files do you receive, for example single images, EXR passes or a finished video?
  • Who owns the scene files and can they be re-rendered later?

I stage approvals for exactly this reason: a change at a still costs minutes, the same change after a full render costs days. If you want a plan for a film, write to me with a few lines about length, format and deadline. The same questions apply to CGI commercials as to any other rendered work.

Written by Marco Mori, 3D artist and creative director in Lindau at Lake Constance, Germany, working with brands and agencies worldwide.

Frequently asked questions

What is a render farm?

A render farm is a group of networked computers used to render 3D images or animation together. A job is split into frames, each machine renders some of them, and the finished frames are collected in one place. It can be a rack in a studio or an online service.

How does a render farm work?

You send the scene and its textures to the farm. A queue manager splits the job into frames, hands them to the nodes, and each node renders its frames on its own. The finished images are written back to storage and you download them.

Do I need a render farm?

Only when your own machines cannot finish the renders before the deadline. Work out the total number of frames, time one test frame, and divide. The free check on this page does that with your own numbers.

How much does a render farm cost?

There is no fixed price, because farms bill for the computing time you use. The main drivers are the time per frame, the number of frames, the number of full re-renders, the priority tier and whether the job needs CPU or GPU nodes. Some farms publish their rates and offer a small trial, which is the cheapest way to test.

Is a cloud render farm the same as an online render farm?

In practice yes. Both mean rented machines you reach over the internet, usually billed by the time they run. The difference between providers is mostly which software and renderers they support and how they handle priority and support.

Can a render farm render a simulation?

A simulation runs frame after frame, because each frame depends on the one before it, so it is calculated first and saved to disk as a cache. The render of the cached result can then be shared out across nodes like any other render.

Does Redshift work on a render farm?

Redshift is a GPU renderer that can also render on the CPU, according to its maker Maxon. A farm has to support your exact renderer and version, so ask before you upload, and note that GPU nodes are priced differently from CPU nodes.

Is a render farm worth it for a small project?

Often not. For a single still or a short animation with a relaxed deadline, your own computer is simpler, and uploading the scene takes time too. A farm pays off when the deadline is shorter than the render time on your own machines.

Let's Work
Together

Get in touch