A Guide to Placing Objects on Points with Blender Geometry Nodes

What will you learn in this guide?

In this guide, you’ll learn the basic principles of placing geometry on points with Blender Geometry Nodes’ Instance on Points node. In architectural visualization, using the same chair, light fixture, plant, or modular component at many positions in a scene is one example of this approach. These examples illustrate possible uses; the node is not limited to any particular type of object.

The key difference is that each placement references the source geometry instead of creating a new, independent copy. The Blender manual notes that instances can use the same geometry data at different positions, which can offer processing advantages over duplicating data. The result depends on the scene geometry and the operations performed, so you shouldn’t assume the same performance improvement in every file.

Requirements and getting started

You’ll need to use Geometry Nodes in Blender and prepare geometry to use as an instance. The source can be a single piece of geometry or geometry that contains multiple instances. The Points input of the Instance on Points node works with geometry that has a Point domain; the manual gives meshes, point clouds, and curve control points as examples.

The source documentation doesn’t specify a particular Blender version, account requirements, or hardware requirements. For that reason, it isn’t possible to provide a version number or system recommendation here. Before you begin, decide on the source geometry and placement points for your scene. The points affect where each instance is placed in the scene.

Creating a layout with Instance on Points

1. Choose the source geometry. Select the object or geometry to repeat. For example, imagine a row of chairs in an interior. You’ll connect the source geometry to the Instance input, so check that its orientation and size are suitable for the intended layout. This is a preparation step involving the source object’s initial orientation; consider it alongside the node’s Rotation and Scale controls.

2. Connect point geometry to the Points input. The points’ positions determine where the instances are placed. If the input geometry already contains instances, the node can also create new instances at points within those instances. This can produce nested instances. Starting with a simple point layout makes it easier to distinguish the roles of the Points and Instance inputs.

3. Check the selection. The Selection input determines which points receive instances. Points with an active selection value are included; the others are skipped. This lets you place source geometry only at selected points instead of using every point in the point geometry. Since the sources don’t specify a required selection-mask method, focus here on the function of this input.

4. Set the rotation and scale. The Rotation input controls each instance’s Euler rotation, while the Scale input controls its size. For Rotation, you can use the rotation output from nodes such as Distribute Points on Faces or Curve to Points. The manual also lists Align Rotation to Vector as an option when you need to create a rotation from a direction vector. These connections can pass orientation information from the points to the instance layout.

5. Pass the result to the rest of the node tree. The Instances output of the Instance on Points node contains the resulting placements. If the point geometry has an id attribute, that information is passed to the resulting instances. Other attributes on the points can also be accessed in the instance domain of the created instances. This lets you use data carried by the point geometry in subsequent operations.

6. Explore Pick Instances if you need to choose a single source from a list. When this option is enabled, the node can select one of the instances in the list instead of adding all the geometry from the Instance input at every point. The Instance Index input determines the selection. The documentation notes that the default selection is based on the point ID, if available, or otherwise the index value; negative values or values exceeding the list’s bounds wrap around from the other end of the list. The feature is specifically designed to be used with the Collection Info node.

What changes in an architecture and visualization workflow?

Architects and visualization artists working with repeated furniture, plants, or modular building elements can use instancing to place the same source geometry at different positions. Since the source geometry’s data isn’t duplicated separately for each placement, this approach can make processing more efficient when working with repeated and complex models. However, it can’t be said to guarantee a speed increase across the entire file.

When you need to convert instances into real geometry, you can use the Realize Instances node. After conversion, each resulting piece of geometry takes up memory, and operations on the geometry are performed on each piece separately rather than on a single source. For this reason, consider converting instances into real geometry only when independent geometry is needed in subsequent steps. For example, realization may be necessary if each copy needs a different geometry operation; if the same operation can be shared across all instances, working with the source geometry may be suitable.

There’s also a limit to nested instance chains: according to the Blender manual, depths of up to eight levels are supported in the viewport and during rendering. You can build a deeper structure, but to display or render it, you need to realize the instances at the end of the node tree. Also, instances created through Geometry Nodes can’t be mixed in the same setup with instances used through the Instancing panel in the Properties editor. These points make it important to plan your workflow, especially when adding a new node setup to an existing scene.

Common mistakes

• Confusing the inputs: Points carries the placement positions, while Instance carries the source to be duplicated. Check the connections with this distinction in mind.

• Ignoring rotation: Rotation affects the instance orientation. If the result is unexpected, check both the source geometry’s orientation and the Rotation input.

• Creating real geometry unnecessarily: Memory usage may increase after Realize Instances, and subsequent operations process each piece of geometry separately. First determine whether this conversion is necessary.

• Forgetting the nested-structure depth limit: Structures that exceed the supported limit of eight levels require realization at the end of the node tree for display and rendering.

Next steps

Once the basic layout works, check the Rotation and Scale inputs against the information provided by the point geometry. If you’re working with multiple sources, explore the Pick Instances and Instance Index options. Make the decision to realize instances based on the needs of your scene: will you need to operate on independent geometry, or is it enough to keep the source references?

Next, you can also try creating curves from points. The Points to Curves node groups points with the same Curve Group ID value into a curve. The Weight input helps determine the order of points within the curve: smaller values are placed at the start, and larger values at the end. Points with the same Weight value retain their relative order. The resulting curves are not cyclic, and the output doesn’t preserve other geometry components from the point cloud. These details help you interpret the result correctly when using curve- and instance-based layouts together.

Sources and license

This tutorial has been adapted into Turkish using the Instance on Points, Points to Curves, Geometry Nodes, and Instances sections of the official Blender manual. The source documents are licensed under CC BY-SA 4.0.