XO3D Studio · Guide
CGI Studio vs Render Farm.
A render farm processes 3D files. A CGI studio creates them, with creative direction, material craft, and production management. The difference is not only computing power. It is who is responsible for creating and approving the scene. Providers also vary in how much technical help they give with a submission.
The studio behind this guide
Which of the two we are
A render farm processes scene files that are already built and approved; a CGI studio creates them, making the decisions about the product's geometry, materials, lighting and camera. XO3D is the studio side of this comparison, with a named Creative Director making the visual decisions and attending the reviews. When what you need is compute against an already approved scene, a render farm is the correct tool.
How XO3D compares to the other five supplier modelsThe distinction matters because buying the wrong type of service produces a predictable outcome: technically processed output that doesn't work commercially. A render farm given a poorly lit, generically materialled 3D scene will return a well-processed version of that poor scene, quickly. Judging whether the scene was right to begin with is not the farm's job. That responsibility sits with whoever built and approved it.
Understanding what you are actually commissioning, and what the output of that commission will be, is the most important decision a brand or agency makes at the start of a product CGI project. A launch-image brief belongs with a studio responsible for director-led product CGI; an accuracy-led mechanism or engineering brief belongs with Technical CGI.
Definition
What is a render farm?
A render farm is a group of computers that processes the frames of a scene you have already built. Render farms split the job across many machines, so it finishes sooner than on one workstation. A farm does not create the scene; the model, materials, lighting and camera come in the file you submit. Some providers also check submissions or help with technical setup, and that help varies from one provider to the next.
The comparison
What each provides.
| Capability | CGI Studio (e.g. XO3D) | Render Farm |
|---|---|---|
| Creative direction | Named Creative Director on every project | Not part of the service; the creative decisions are already in the scene you submit |
| 3D model creation | Full modelling from CAD or reference | Processes existing files; the model arrives in the submitted scene |
| Material development | Custom PBR materials from physical reference | Normally supplied in the submitted scene; separate assistance varies by provider |
| Lighting design | Per-project custom lighting rigs | Normally supplied in the submitted scene; separate assistance varies by provider |
| Animation direction | Storyboard, animatic, directed animation | Normally decided and approved before the scene is submitted |
| Client review process | Frame.io review, revision rounds | Creative approval is owned by your team or studio; providers may help with job setup and render errors |
| Rendering processing | Included in production pipeline | Core service |
| Post-production & grade | Full grade, sound design, delivery | Normally done by your own team after the frames come back |
| Source asset required | Can build from scratch | Requires complete, render-ready scene file |
| Output quality | Determined by creative direction and craft | Depends on the quality of the supplied scene and a compatible render setup |
When a render farm is the right choice
Render farms serve a specific, legitimate need.
Render farms are the right choice when you have complete, production-ready 3D scene files and need to process large volumes of frames faster than your own hardware allows. Visual effects studios, animation houses, and other studios with in-house 3D teams use render farms routinely to accelerate their own production pipelines.
If you have an in-house 3D team that produces complete scene files and needs processing power, a render farm is the correct tool, and XO3D offers managed render farm capacity for studios in that position. If you are commissioning product imagery from scratch, without an in-house 3D team, you need a CGI studio.
Before you send a scene
What render-ready means.
"Render-ready" is the phrase that decides whether a farm is the right choice, so it is worth being specific. A render-ready scene is one where every creative decision has been made and approved, and everything the renderer needs travels with the file. Ask your artist or studio to confirm these six things.
- The right model revision. The geometry matches the product version and references you approved, not an earlier export.
- Approved cameras, materials and lighting. The look has been signed off locally. A farm renders the decisions in the file; it does not make them.
- Packed textures and linked assets. Every texture, linked file and asset the scene uses travels with it, with paths that resolve on another machine.
- Compatible software versions. The application, renderer and plugin versions are ones the provider supports, and match what you used to approve the look.
- Complete caches and proxies. Simulation caches, proxies and any baked data are finished and included, so nothing is recalculated differently on the farm.
- Agreed frame range and output. Frame range, resolution, frame rate and output format are set and written down.
Then render a representative test frame on the farm and compare it with the approved local result. If the two differ, stop and find out why before the full job runs.
This is a general checklist for any provider, not XO3D's acceptance specification for its managed render farm service. Ticking an item means someone has checked it; it does not mean a tool or provider has validated the file.
Responsibility
Who owns each decision?
Three parties can be involved: the brand or reviewer who approves the work, the team that creates the scene, and the provider that supplies the computing power. The table below is a typical split, shown as an example rather than a record of any one project. Real contracts can allocate tasks differently, so agree the split in writing before work starts.
| Decision | Brand or reviewer | Scene-creating team | Compute provider |
|---|---|---|---|
| Product source approval | Approves the product data and references | Builds from the approved source | No role |
| Look and camera | Approves | Creates and proposes | No role |
| Animation and preview | Approves | Animates and renders previews | May render previews if asked |
| Submission and test | Agrees the test is representative | Packages the scene and checks the test frame | Runs the test and reports technical errors |
| Final image review | Gives final creative sign-off | Checks frames against the approved look | Reports missing or failed frames |
| Delivery | Receives and uses the files | Grades, assembles and delivers | Returns rendered frames |
For engineered products, accuracy review belongs at the model stage: Plan technical review. For the files, formats and sizes the work ends in: Agree delivery outputs.
Timing
Estimate frames before estimating elapsed time.
Start with the frame count, because it separates the computing question from the preparation question. A hypothetical example: a 30-second film at 25 frames per second is 750 frames. If a test frame takes a measured time t to render, rendering one frame after another would take 750 × t.
That figure is render time only. Queueing, uploading, loading the scene, building caches and downloading the frames all add to it. Spreading the frames across many machines can shorten the elapsed time, but it does not remove that overhead, and the gain is rarely a straight division by the number of machines. None of this covers the time to build and approve the scene.
Estimate render time from your test frame with the XO3D Labs tool.
Procurement questions
Ask before sending a scene.
Whichever provider you use, these are questions for that provider to answer about its own service. The answers differ, and they matter more for an unreleased product.
- Which exact application, renderer and plugin versions do you support?
- Who packages and checks the assets before the job starts?
- Who authorises the test render, and what happens if it does not match?
- How are failed or missing frames found and handled?
- How are files transferred, and how long are they kept afterwards?
- What confidentiality terms cover the scene and the frames?
- Who reviews the final output before it is used?
Next step
Which route fits?
I have an approved scene
You need computing power for a finished, render-ready scene. Tell us about the scene and we will check the scope with you first.
Check the scope for managed render farm capacityI need the imagery created
There is no finished scene yet, or the scene is not at the standard the launch needs. That is studio work.
Product stills: 3D product renderingProduct films: product CGI filmsFAQ
Common questions, answered.
What is a render farm?
What must already exist before a scene goes to a render farm?
Does more compute fix the scene?
Can I use a render farm instead of a studio?
Does XO3D use render farms internally?
Your next project
Decide who owns the creative work.
A finished scene needing computation is a different brief from a product needing a story. Identify whether you need creative direction, asset preparation, animation or rendering before selecting a production route.
A route to consider
Product CGI Films
A product film developed through creative treatment, storyboard, animatic, product review and final picture and sound.
Bring these three things.
- Is the creative direction already approved?
- Do production-ready scenes exist?
- Who owns review and final delivery?
Start with an outline. We review the product, intended outputs and timing before agreeing the production scope.