November 5, 2026 Linh Nguyen

Blender Geometry Nodes Instancing for Cycles Rendering (2026): Memory, Baking and Culling

Quick answerRendering Geometry Nodes scatters in Cycles
Checked Nov 2026

Keep scattered objects as instances: the Blender Manual explains that instancing stores geometry once, which lets Cycles handle the same data in many places better than duplicated data, while realized instances take more memory. Bake simulations and heavy node trees before rendering so every frame and every GPU uses the same data, and use Simplify › Culling to drop objects outside the camera.

  • Memory: avoid Realize Instances unless copies must be unique.
  • Speed: bake heavy node trees and simulations to disk.
  • Consistency: render from baked data on every GPU.
  • Culling: Simplify › Culling › Camera Culling.

Geometry Nodes makes it easy to scatter millions of plants, rocks or buildings. Whether that scene renders on a GPU depends mostly on one choice: whether the scatter stays as instances or becomes real geometry.

This guide covers how instancing saves memory in Cycles, when realizing is worth it, why baking matters for frames rendered in parallel, and the culling options that trim what is off screen.

Checked against the Blender Manual (Geometry Nodes Instances, Baking, Cycles Simplify), November 2026.

1. Instances vs realized geometry

The Manual describes instancing as duplicating geometry without duplicating the data, and notes this lets render engines like Cycles handle the same geometry in many locations better than duplicated data. Realizing converts instances into unique geometry; realized instances take more memory and each copy must be processed separately (Blender Manual: Instances). Since every GPU in a multi-GPU render holds the whole scene, this memory difference applies to each card.

iRender
Instances vs realized geometry in Cycles
Schematic
Instances1 tree meshstored once15 transforms point at one meshRealizedmeshmeshmeshmeshmeshmeshmeshmeshmeshmeshmeshmeshmeshmeshmesh15 full copies of the mesh in memoryEvery GPU holds the whole scene, so realized copies cost memory on each cardInstances store one mesh; realized copies multiply memory on every GPUBlender Manual: Geometry Nodes Instances
instancesrealized
Source: Blender Manual, Geometry Nodes Instances

2. When to realize, and the nesting limit

Realize only when each copy needs unique geometry, for example a boolean that cuts each instance differently. The Manual also notes that only eight levels of nested instancing are supported for rendering and viewing; deeper trees must be realized at the end of the node tree. Instances can store an id attribute, which keeps motion blur correct when instances move.

FixesBlender 5.x + Cycles

Heavy Geometry Nodes scenes: what to check

Where memory and evaluation time usually go in scattered scenes.

SymptomLikely causeFirst check
GPU runs out of memory on a forest or cityRealize Instances at the end of the treeRemove Realize Instances unless each copy must be unique
Long pause before each frame startsNode tree or simulation re-evaluated every frameBake the simulation or heavy node output to disk
Frames differ between GPUs or machinesUnbaked simulation evaluated separately per instanceBake, then render from the baked data
Instances flicker in motion blurNo stable id attribute on moving instancesKeep the id attribute on instances that move
Objects off camera still cost memoryNo cullingSimplify › Culling › Camera Culling, with Camera Cull enabled on the objects
NoteOnly eight levels of nested instancing render; deeper trees must be realized at the end.

3. Bake before rendering

Geometry Nodes can bake simulation and node output to disk (Blender Manual: Baking (Geometry Nodes)). Baking moves the expensive evaluation out of the render, so each frame starts sooner, and every Blender instance reads the same data. That matters when frames are split across GPUs: an unbaked simulation is evaluated separately in each instance. Keep the bake folder inside the project with relative paths so it travels with the file; see multi-GPU rendering in Cycles.

iRender
Baking Geometry Nodes before a split render
Schematic
Unbaked: every instance evaluates the treeBlender 1simulate / evaluatebefore each frameBlender 2simulate / evaluatebefore each frameBlender 3simulate / evaluatebefore each frameBlender 4simulate / evaluatebefore each frameBaked: evaluated once, read by allbake folderinside the projectrelative pathBlender 1Blender 2Blender 3Blender 4Baking moves the expensive evaluation out of the render and gives every instance identical dataBlender Manual: Geometry Nodes Baking
evaluated per instanceread from the bake
Schematic, not to scale

Without a bake, four instances repeat the same evaluation four times and each can only be as consistent as its own run. With a bake, the work is done once and every frame reads the stored result.

4. Culling what the camera cannot see

Cycles Simplify includes Culling options: Camera Culling removes objects outside the camera view with a margin, and Distance Culling removes objects beyond a distance. Objects need Camera Cull or Distance Cull enabled in their own visibility settings (Blender Manual: Simplify). Use a margin large enough that culled objects do not pop into shadows or reflections, and check the edges of frame in a moving shot. For the rest of the memory budget, see Cycles GPU memory.

iRender
Camera and distance culling, top view
Schematic
cameramargindistance limit✕✕✕✕✕✕Objects need Camera Cull or Distance Cull enabled; use a margin wide enough for nearby shadows and reflectionsBlender Manual: Simplify (Culling)
kept: in viewkept: inside marginculleddistance limit
Schematic, not to scale

The margin is the safety zone: objects just outside the frame can still throw a shadow or appear in a reflection, so they are kept, while objects well outside the view or beyond the distance limit are dropped before rendering.

A Geometry Nodes checklist before a long render

  1. Instances: scatter kept as instances; Realize Instances removed where not needed
  2. Nesting: eight or fewer instance levels at render
  3. Bake: simulations and heavy node output baked, bake folder inside the project
  4. Motion: id attribute kept on moving instances
  5. Culling: camera or distance culling set with a safe margin
  6. Test: heaviest frame rendered and peak memory checked

For paths, caches and other scene checks, see our 10-point Blender Cycles pre-flight checklist.

Both farm models can render Geometry Nodes scenes once the bakes travel with the project. On an IaaS server you can open the node tree, re-bake if a path breaks, and test memory on the same GPUs that render the sequence.

Rendering Geometry Nodes scenes on an iRender server

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found
  1. Upload the project with its bake folders to iRender Drive before you start the server; uploading is free and does not use rental time.
  2. Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and connect by remote desktop.
  3. Open the file, confirm bakes load, and render the heaviest frame.
  4. Render the sequence one Blender per GPU, then shut down; multi-GPU servers are billed per minute.

Frequently asked questions

1. Do instances save memory in Cycles?

Yes. Instances store the geometry once; realized instances store every copy and take more memory.

2. When should I use Realize Instances?

Only when each copy needs unique geometry. Otherwise keep instances for memory and speed.

3. How many levels of nested instances can render?

The Manual says eight levels are supported for rendering and the viewport; deeper trees must be realized at the end.

4. Why bake Geometry Nodes before rendering?

Baking stores the result on disk, so frames start sooner and every render instance reads the same data.

5. How do I stop off-screen objects using memory?

Enable Camera Culling in Render › Simplify › Culling and Camera Cull on the objects, with a margin.

Render your Blender projects on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.

Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.

This quick start shows how to start a server and render Blender on it:

Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, ,

Linh Nguyen

Linh Nguyen works in customer support at iRender, helping artists render Blender and Houdini projects on multi-GPU servers. She has written more than 300 articles for the iRender blog, covering Blender, Houdini and practical GPU rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →