Blender Cloud Render Farm

We support Blender 4.4 (latest stable), Blender 4.2 LTS, and Blender 3.6 LTS, plus all minor releases between 3.0 and 4.4. Our support matrix is updated with each major Blender release. If your exact version is not listed in the compatibility table on this page, contact our support team — we typically add new versions within a few business days of each official release.

Bundled add-ons that ship with Blender are available on every render node. External add-ons that affect geometry, shading, or rendering at render time — such as Geometry Nodes (built-in), FLIP Fluids, MOLECULAR, and Hard Ops modifiers that are baked into the mesh — render without issues when the result is embedded in your .blend file. Add-ons that require an active Blender UI session or a running simulation cannot execute on headless render nodes. If you are unsure whether a specific add-on is compatible, contact our support team before submitting.

Use Blender's built-in File > External Data > Pack Resources command to embed all textures and image sequences into your .blend file before uploading. For scenes that reference external .blend libraries via linked or appended data, ensure all linked files are included in the same project folder when you submit. Our desktop application automatically detects and packages the full dependency tree during upload.

Yes, with one important step: bake your simulation data locally before uploading. Mantaflow (fluid and smoke), cloth, and particle simulations must be baked to disk as a cache so the render nodes can read the frame-by-frame data without re-simulating. Include the simulation cache folder in your project upload. The actual rendering of baked simulation frames runs on the farm without any issues.

Cycles GPU rendering runs on NVIDIA RTX 5090 nodes with 32 GB GDDR7 VRAM per card. The 32 GB VRAM capacity handles large production scenes with dense geometry and high-resolution textures. Cycles uses OptiX hardware ray tracing on our RTX cards, which is typically 4–10× faster than CPU Cycles for the same scene complexity.

Cycles CPU rendering starts at $0.004 per GHz-hour. Cycles GPU rendering on RTX nodes starts at $0.003 per OctaneBench-hour. GPU is usually the faster and lower-cost option for Cycles scenes. New accounts receive $25 in free trial credits — enough to test a full short animation or a high-sample still frame. There are no subscription fees or minimum commitments.

Cycles and Blender Internal (Workbench) are the supported render engines for Blender jobs on our platform. Third-party Blender render engine integrations such as LuxCoreRender, OctaneRender for Blender, and AMD ProRender require separate licensing and installation that we do not currently provide for the Blender host application. If you use Blender primarily as a modeler and export to a standalone renderer like Redshift or Arnold, those workflows are supported via our dedicated engine pages.

Download our desktop application, open your packed .blend file, and click Submit Job. The application detects Cycles as your render engine, lets you set the frame range, output format, and node type (CPU or GPU), then uploads your project and starts rendering. Completed frames are available for download as each one finishes — you do not need to wait for the full job to complete.