How Online Rendering Actually Works
At its simplest, cloud rendering uses a network of remote computers to do the heavy lifting for your 3D projects. When you render on your own machine, it processes every frame one by one. In the cloud, a farm can take an animation and assign each individual frame to a different computer (known as a node). This parallel processing can turn a week-long render into something that finishes in less than an hour, all while leaving your local computer free so you can keep working.
How Pricing Usually Works
Pricing for render farms can be confusing, which is why we created this tool! The most common way is the pay-as-you-go model, where you’re billed for the time the farm’s processors spend on your files. Often farms use specific units like GHz-Hours for CPU tasks or OB-Hours for GPU rendering. Some services do it even simpler by charging a Node-hour, which is the cost of renting one physical computer for sixty minutes. Farms also provide priority levels for your job. If you aren't in a rush, you can choose a low-priority lane where your project sits in a queue and only renders when there’s time. Or you can skip the line and go the high priority route, which assigns more machines to your project, but you pay more for the speed.
Tips on Preparing Your 3D File for a Render Farm
When sending a file to a render farm, you need to make sure the remote computers have everything they need. Some farms make this easy with one-click upload tools, but when they don’t, the most common mistake is forgetting external assets, or not baking a simulation (cloth, fluid, fire, etc.) Absent those, your render may look entirely different, or fail altogether. Most 3D software includes a Pack or Collect Files feature that gathers all dependencies into one folder. It’s also worth checking your scene’s optimization before uploading, since unnecessary high-poly objects or overly complex light bounces can drive up costs. At the end of the day, follow the specific instructions at the farm you’re using.
Cloud Rendering Term Glossary
This glossary covers the essential terms you'll encounter while navigating different services.
-
Render Node: Think of this as a single worker computer in the farm. When you send a job to a farm, it is broken up and distributed across hundreds of these individual nodes.
-
Render Engine: The software (like Cycles, Redshift, or Arnold) that actually calculates the light and materials in your scene. Your scene must be compatible with the specific engine the farm has installed.
-
SaaS (Software as a Service): A one-click style farm. You upload your file through a plugin or web interface, and the farm handles all the technical setup for you. This is the most common way for novices to use a farm.
-
IaaS (Infrastructure as a Service): Instead of a simple upload, you rent a blank high-powered computer remotely and install your own software and licenses on it. This is also known as a Cloud Workstation.
-
CPU vs. GPU Rendering: CPU rendering uses the computer’s main processor (e.g., Arnold, V-Ray) and is great for memory-heavy scenes. GPU rendering uses graphics cards (e.g., Octane, Redshift) and is generally much faster for modern workflows.
-
OctaneBench / V-Ray Benchmark: Standardized scores used by farms to communicate how powerful their nodes are. It helps you compare the bang-for-your-buck across different services.
-
GHz-Hour: A unit of measurement for CPU rendering. It is a way to calculate the cost based on the processor speed multiplied by the time spent rendering.
-
OB-Hour: Short for OctaneBench-Hour. This is the GPU equivalent of a GHz-hour, used to measure how much graphics card power you consumed.
-
Packing/Collecting: The process of gathering all your assets—like textures and lighting maps—into a single folder so the render farm can find them.
-
Dependencies: The specific versions of software, scripts, or plugins your file needs to run. If your file relies on a specific tool that the farm doesn’t have installed, the scene won't render correctly.
-
Strip Test: A common pro-tip where you render every 10th or 20th frame of your animation first. It’s a cheap way to make sure the movement and lighting look right before paying for the full render.
