Place Repeated Geometry on Points with Blender Geometry Nodes

What will you learn in this guide?

The Instance on Points node in Blender Geometry Nodes is used to place one geometry on the points of another. This guide covers the node’s basic inputs and outputs, point selection, and controls for instance orientation and scale. The goal is not to provide a ready-made recipe for a particular facade or landscape layout, but to explain how repeated elements are positioned.

In architectural modeling, this approach is useful for experimenting with facades, ground surfaces, or interior layouts where the same module is used in multiple locations. These examples suggest possible applications of the method; the source manuals do not provide instructions for these specific projects.

Requirements and version information

To get started, you need a Geometry Nodes node tree and the Instance on Points node in Blender. The official manual states that this node can be used with geometry types that have a Point domain. Meshes, point clouds, and curve control points are among the examples listed.

The sources do not specify a Blender version, hardware requirements, or an account requirement. So it is not possible to confirm a specific version here. Before getting started, check the manual for the Blender version you are using and make sure the node is available.

You need two geometries: one containing the points where instances will be placed, and one source geometry to appear at those points. The manual explains that the Instance input can receive either actual geometry or geometry containing multiple instances. Starting with a single source geometry makes it easier to understand the role of each input.

Step-by-step setup with Instance on Points

1. Choose the point geometry. In the Geometry Nodes tree, select the geometry to connect to the Points input. Meshes, point clouds, and curve control points are among the geometry types supported by this node. The points’ positions affect the transforms of the resulting instances in the scene. First, decide which geometry’s points you want to use for placement.

2. Prepare the source geometry. Connect the geometry you want to place to the Instance input. For example, you could use a simple module representing a facade element. This is an architectural use-case suggestion; the official manual does not recommend a specific module type or dimensions. Starting with simple geometry makes the placement result easier to read.

3. Connect the points and source to the correct inputs. Connect the geometry containing the points to the Points input, and the source geometry to be instanced to the Instance input. The node’s Instances output provides the resulting instances. After connecting everything, inspect the result to check that the point positions and source shape are being used as expected.

4. Select the points you need. The Selection input accepts selection data that determines which points will receive instances: instances are created on enabled points, while disabled points are skipped. Using all points for the initial test is a good way to check the basic connections. You can later change the selection data to limit placement to specific points; the manual does not prescribe a particular way to create this selection.

5. Adjust the instances’ size and orientation. The Scale input controls the size of each instance, while the Rotation input controls its Euler rotation. Set these inputs as needed when you want elements to share the same size and orientation. According to the manual, Rotation can also receive rotation output from nodes such as Distribute Points on Faces or Curve to Points. Align Rotation to Vector can also be used to generate an Euler rotation from a direction vector; the normal vector is given as an example.

6. Check attributes and the instance list. Attributes on the points can be used in the field of the generated instances. If the input geometry has an attribute named ID, that ID is also carried over to the resulting instances. If you want to select from multiple sources, the Pick Instances option selects one instance based on the Instance Index value, rather than adding the entire list from the Instance input to every point. The manual specifically mentions using this option with Collection Info.

7. Review the output’s data structure. The node outputs instances: these reference the source geometry’s data rather than creating an independent copy at every position. This can be an efficient way to use many copies of the same geometry. If you later need to convert the instances into separate objects, the manual notes that the Make Instances Real operator can be used to create objects from them.

Common mistakes

Confusing the point geometry with the source geometry: The Points input should receive the geometry containing the placement positions, while the Instance input should receive the source to be placed. If the result is unexpected, check these two connections first.

Overlooking points affected by the Selection input: This input determines whether each point gets an instance. If some positions are empty, check which points the selection data enables.

Misinterpreting rotation data: Rotation expects an Euler rotation. If you need to create a rotation from a direction vector, consider the Align Rotation to Vector node mentioned in the manual; do not treat the vector itself as the same type of data as a rotation value.

Not accounting for nested instancing: If the geometry connected to the Points input already contains instances, the node can also place new instances on points within those instances. The manual describes this as nested instancing. If the result has unexpected scales or rotations, check the instance structure of the input geometry as well.

Using objects without geometry directly as sources: According to the manual, the Object Info node can be used to instance object types without geometry, such as lights. Metaball objects are not supported.

Use in architectural workflows and next steps

Architects, interior designers, and archviz artists can consider this method as a placement tool for repeated modules. Managing point positions, source geometry, selection, scale, and orientation through separate inputs makes it easier to track what changes during design iterations. When working with facade elements or interior modules, it can be useful to set things up in a small, simple example first.

The official sources do not provide information about performance benchmarks, recommended hardware, licensing costs, or compatibility with other software. Before moving into production, separately assess the Blender version you are using, whether the file suits your team’s workflow, and how the instances perform in the actual project scene. You can experiment with point clouds or curve control points, but the sources do not include a detailed workflow for the node’s behavior with this geometry.

To learn more, explore the Instance on Elements, Realize Instances, and Rotate Instances nodes listed in the Geometry Nodes manual. These are listed as related node types; this guide does not assume additional features that are not described in the sources.

Sources and license

This guide has been translated and adapted from Blender’s official Geometry Nodes and Instance on Points manuals. Both sources are published under the CC BY-SA 4.0 license.