What a Cycles render farm is
Cycles is Blender's path tracer. For every pixel it follows rays of light as they bounce around the scene, which is what makes it look right and what makes it slow: more samples, more bounces, more glass, hair and volume all mean more time per frame.
A Cycles render farm is a set of machines running Blender and Cycles that renders your project for you. It works because the frames of an animation are independent of each other. Frame 212 does not need frame 211 to exist, so a sequence your computer would render one frame after another can run on many machines at the same time, and the wait shrinks from the sum of every frame towards the time of a few.
That is the whole mechanism. Everything else a farm offers is built on top of it, and most of it, as it turns out, is not what you need at the moment you actually use one.
When your machine cannot carry it
A farm is not for the render that takes two hours at home. If your machine can finish it over lunch, let it. Cycles earns a farm in three ways. Two come from the weight of the work, and the third, usually the real one, from what the render costs you in days.
The frame that does not fit
A Cycles frame has to fit in the memory of the GPU rendering it. Dense geometry, large textures, volumes and hair push a scene past what a laptop or a mid-range card can hold, and at that point the render either fails outright or crawls along on the CPU. Every node on our farm has at least 24 GB of VRAM and 48 GB of RAM, and a scene that needs more is given nodes with more. The free evaluation renders real frames of your scene on them, so you find out it renders before you pay anything.
The sequence that takes a week
This is the common case. A one-minute shot at 24 frames per second is 1,440 frames. At seven minutes a frame, which is ordinary for a finished Cycles scene, that is a week of your computer doing nothing else. The frames themselves are not the problem; the count is. And the count is exactly what a farm divides.
The days your machine is not yours
The third reason has nothing to do with how heavy the scene is. Even when your machine can finish the render, those days are not free. A project runs through design, production and render, and your work is in the first two. During the render you only wait: the workstation is tied up, Blender crawls if you try to work alongside it, and the next project waits too.
Handing the render off turns those days back into working days. You start the next job while this one renders, or run several projects at once, and rendering stops being something you do and becomes something you delegate. Once the project is uploaded nothing runs on your side, so the machine can go straight back to work, or off.
If a render finishes overnight and you have no use for the machine until morning, a farm gives you little back. The heavier the render, the more it returns.
At the final render, you need a price and a time
Look at what render farms put on their front pages: frames streaming back live, a node picker full of GPU specs, logs scrolling while the job runs. All of it is built for watching a render. Now think about when you actually send one.
You send it at the end. The look is signed off, the camera is locked, and you have rendered test frames at home until you stopped finding problems. Testing is over. What is left is the final frames, as soon as possible, and two questions a professional has to answer before committing: how long will this take, and what will it cost?
They are not idle questions. Rendering is a stage of the project like design and production, and it has to be planned like them: in the budget, in the schedule, and in what you charge the client. A number you only learn after the render is a number you cannot plan with.
A live preview answers neither. Neither does choosing a node. A log tells you what went wrong after it went wrong. They are tools for a stage of the project you have already left, and they turn the one step that should be uneventful into something you have to supervise.
So we built the farm the other way round. Before anything is charged, it evaluates your own scene at your own settings, gives you a fixed price and a delivery time for each tier, and sends back four test frames so you can check it renders as you expect. You read the numbers, pick one, and go back to work. Try it on your own scene: the evaluation is free.
One real job, from upload to frames
Drift That Supra! is one of the real jobs on our pricing page: a Cycles animation of 234 frames at 1920 x 1080, saved in Blender 4.4 and rendered to OpenEXR. This is the quote it got before it started, and it rendered in the time it was quoted.
Blender 4.4 · Cycles · 1920 x 1080 · 234 frames · OpenEXR
- Economy
- $38.95
- Standard
- $51.87
- Express
- $65.70
- Upload. The
.blend, a zip or the project folder goes onto the render page, or straight from Blender with LaunchControl. The Blender version, the frame range and the output format are read from the file. There is no form to fill in and no node to choose. - Evaluation. The farm evaluates your scene at the file's own settings and sends back four test frames. They are your check that it renders here the way it does at home: a missing texture or an unbaked simulation shows up in four frames rather than 234, and if something will not render, you are told why. It is free, and needs no account.
- Quote. A fixed price and a render time for each tier, like the ones above. You pick one and start. Only this step needs an account, and you pay exactly the quoted amount.
- Collect. The frames appear on your dashboard when the job is done and stay there for 7 days.
Read the plate as a trade. This job renders in 9h 30m on Economy, 2h 25m on Standard or an hour on Express, each step up costing about $13 more, because the tier sets how many nodes render your project together: Express is the biggest cluster, Economy the smallest. It buys more machines on your job, not a place ahead of anyone else's, so no render waits behind another. The trade is different for every project, which is why it comes from the evaluation and not from a rate card. Your own project gets the same plate, free: price your Cycles project.
Your file renders the way you set it
A farm should not have opinions about your scene. Samples, the noise threshold, light paths, the denoiser, motion blur and colour management are used exactly as they are in the file. Nothing is quietly re-tuned to make a render cheaper, and a project saved in Blender 3.6 renders in 3.6, not in whatever version the farm happens to prefer.
It also means the render time is yours to shape. If you want the quote lower, the settings in the file are where it comes from, and seven of them do most of the work.
The file stays yours too. It sits in isolated storage, the machines that render it are destroyed when they finish, and everything is deleted with the job. The Blender render farm page has the whole picture.
What to check before you upload a Cycles project
The same short list every farm needs, and the evaluation will catch anything you miss.
- Pack your textures with File > External Data > Pack Resources, or upload the whole project folder, and make linked assets local.
- Bake your simulations. Fluid, cloth, rigid body and particle caches have to travel with the project, or the farm has nothing to read and the motion will not match what you saw.
- Output an image sequence, not a video file: why pros render in image sequences.
Or let LaunchControl prepare the project: it checks integrity, bakes simulations and consolidates assets from inside Blender. The long version, by hand, is in how to prepare a Blender project file.
Questions about rendering Cycles on a farm
Will my Cycles render look different on a render farm?
It should not, and you do not have to take that on trust. The render runs in the Blender version your file was saved in, with the settings in the file, and the four test frames from the evaluation come back before you pay, so you can put them next to your own.
What if my scene does not fit in GPU memory?
A frame has to fit on the GPU that renders it, on a farm as on your desk. Every node has at least 24 GB of VRAM and 48 GB of RAM, and a scene that needs more is given nodes with more. The evaluation is a real render of your scene on them, so that is where you find out, for free: if it still cannot render, the evaluation stops there and tells you why.
Is the farm GPU only?
No. Every node pairs a very strong GPU with a strong CPU, so the part of each frame that happens before the first sample, syncing the scene and loading textures, is fast too.
What happens if my render fails?
Most problems show up in the four test frames, before you pay anything. If a render still fails, you are told why, plainly, and the amount spent is refunded to your balance automatically, ready for a retry or your next render.
Can the farm render multilayer OpenEXR passes?
Yes. Multi-pass output through File Output nodes works, including Multilayer OpenEXR, and Drift That Supra! above was rendered to OpenEXR. Node naming decides what your files end up called, which rendering Blender file outputs walks through.
What decides the price of a Cycles render?
What each frame asks of Cycles, times the number of frames: samples, light bounces, resolution, and how much glass, hair and volume the scene holds. The evaluation works all of that out from your own scene at your own settings, so the price is fixed before you start. The settings that move it most are in seven Cycles settings that speed up renders.