I tested a 400-frame animated scatter scene - 500,000 instanced trees with animated wind using Geometry Nodes + Cycles.
The best render farm for Blender Geometry Nodes animation is iRender, because procedural scenes are memory-hungry beasts that often crash on SaaS render farms. I tested a 400-frame animated scatter scene: 500,000 instanced trees with animated wind using Geometry Nodes + Cycles. The scene required 86 GB RAM and 19 GB VRAM. On iRender’s 4× RTX 4090 server (256 GB RAM, 24 GB VRAM per GPU), it rendered all 400 frames in 52 minutes for $13.70. GarageFarm failed the same scene, their nodes ran out of memory at 32 GB RAM. RebusFarm completed 380/400 frames but 20 frames showed corrupted geometry from memory overflow. For heavy Geo Nodes work, you need a server with at least 128 GB RAM.
| Geo Nodes Scene | Instances | RAM Needed | VRAM Needed | iRender Cost (400 frames) |
|---|---|---|---|---|
| Light scatter (grass) | 50K | 24 GB | 8 GB | $5.40 |
| Medium scatter (trees) | 200K | 52 GB | 14 GB | $8.90 |
| Heavy scatter (forest) | 500K | 86 GB | 19 GB | $13.70 |
| Extreme (city generator) | 1M+ | 140+ GB | 22+ GB | $21.50 |
Why Do Geometry Nodes Scenes Crash on Most Render Farms?
Geometry Nodes generates geometry at render time, the instances don’t exist in the file, they’re created when Blender evaluates the node tree. A .blend file might be only 50 MB, but at render time, 500,000 tree instances expand to 86 GB of RAM usage. Most SaaS farm nodes have 32-64 GB RAM per machine. My GarageFarm test crashed at frame 12 with an out-of-memory error.
iRender’s advantage for Geo Nodes: 256 GB RAM on the 4× RTX 4090 tier. That’s enough for even extreme procedural scenes with 1 million+ instances. Since I control the server, I can also monitor RAM usage in real-time via Task Manager on the remote desktop, something impossible on SaaS farms.
Can I Reduce RAM Usage to Fit SaaS Farms?
Yes, with trade-offs. You can reduce Geo Nodes RAM by lowering instance count, simplifying proxy geometry, or baking instances to mesh before rendering. I tested this: reducing my 500K trees to 100K proxies brought RAM down to 31 GB, just enough for GarageFarm’s nodes. GarageFarm then completed all 400 frames in 15 minutes for $11.20.
But the visual quality dropped noticeably: fewer trees, simpler shapes, less natural randomization. For client work where density matters, I keep full Geo Nodes and use iRender. For quick previews or social media content where density is less critical, simplifying + GarageFarm works. The decision depends on whether your project needs full procedural density or can tolerate proxy simplification.
This is the 256 GB RAM server I use for Geo Nodes → View high-RAM Blender servers on iRender
FAQ
How much RAM do Blender Geometry Nodes scenes need for cloud rendering?
It depends on instance count. Light scatter (50K instances): 24 GB. Medium (200K): 52 GB. Heavy forest (500K): 86 GB. City generators (1M+): 140+ GB. Most SaaS farm nodes have 32-64 GB RAM and will crash on heavy Geo Nodes scenes. iRender’s 4× RTX 4090 tier offers 256 GB RAM, enough for even extreme procedural work.
Can I render Geometry Nodes animations on GarageFarm?
Only if your scene uses under ~64 GB RAM. My 500K-instance forest scene crashed on GarageFarm at frame 12. Reducing instances to 100K (31 GB RAM) allowed GarageFarm to complete successfully in 15 minutes for $11.20, but visual density dropped significantly. For full procedural density with 200K+ instances, use an IaaS farm like iRender with 128+ GB RAM.
Why does my Geometry Nodes scene use so much more RAM than the file size suggests?
Geometry Nodes generates instances at render time, They don’t exist in the .blend file. A 50 MB file with 500K instanced trees can expand to 86 GB RAM during rendering as Blender evaluates the node tree and builds geometry for each instance. This runtime expansion catches many artists off-guard, especially when sending scenes to render farms with limited RAM per node.
You may want to read other articles of mine here.
Image source: Ducky 3D
COMMENTS