How to Use Surface Deform and Instance on Points in Blender

What will you learn in this guide?

This tutorial covers two different workflows for creating repeatable scenes in Blender. The Surface Deform Modifier can transfer one mesh’s deformation to another—for example, a simple, simulation-ready cloth model can drive the movement of a more detailed surface. The Instance on Points node lets you use the same element many times in a scene by adding geometry references at selected points.

The two methods address different problems. Surface Deform transfers shape changes from a target mesh to a result mesh. Instance on Points positions existing geometry according to a point layout without duplicating it. Use the first method for deformation and the second for distribution and repetition.

Requirements and setup

You’ll need Blender. The referenced official documentation pages are from the current Blender Manual. Since the sources don’t specify a particular Blender version, this guide doesn’t name one either. The sources don’t specify account requirements or special hardware requirements.

For Surface Deform, prepare two meshes: a target mesh that drives the deformation and a result mesh that receives it. In the simulation example, you could use a simpler, simulation-ready proxy as the target and a more detailed cloth surface as the result. For best results, keep the two surfaces reasonably close together. The greater the distance between them, the more likely unwanted distortion becomes.

Check the target mesh’s geometry before binding it. According to the manual, no edge on the target mesh should be connected to more than two faces. The mesh should also have no concave faces, overlapping vertices, or faces with edges that lie on the same line. If these conditions aren’t met, the Bind operation may fail.

For Instance on Points, you need point geometry and the geometry to place at those points. The points can come from a mesh, a point cloud, or the control points of a curve. The node’s required inputs include Points and Instance; its output is the resulting Instances data.

1. Bind the deformation with Surface Deform

Add a Surface Deform Modifier to the result mesh, then set the target object in the Target field. You can’t change the target after binding; to use a different target, you must first unbind it.

Check the current states of both the target and result meshes before clicking Bind. Bind links the result mesh’s current shape to the target mesh’s current state. The modifier has no effect until the bind is in place. Once bound successfully, subsequent changes to the target mesh’s geometry will also deform the result mesh.

The key distinction here is between object transforms and mesh geometry. According to the manual, binding takes place in global coordinates. Transforms applied to the objects after binding don’t change the result mesh’s deformation. The modifier tracks changes made to the target object’s mesh. So, to control the deformation in this workflow, you need to edit the target’s geometry.

2. Adjust the Surface Deform effect

Strength sets the modifier’s overall influence on the mesh. If you want to apply the deformation only to specific vertices, use a Vertex Group to define the influence per vertex. The Invert option reverses the weights, so vertices in the group are excluded from the effect instead of being deformed.

Interpolation Falloff controls how much a vertex is affected by the faces surrounding its connected face, and therefore how smoothly the deformation transitions. Lower values may produce smoother results, but the manual warns that this setting can also introduce minor distortions. Evaluate the result in context—not just by changing one setting, but also by considering how close the target and result meshes are to each other.

Sparse Bind stores bind data for vertices with non-zero weights in the group at the time of binding. If you use this optimization, adding new vertices to the group later requires rebinding. Keep this in mind if you may need to expand the weight group later in your workflow.

3. Place repeated elements with Instance on Points

In your Geometry Nodes setup, connect the geometry containing points to the Points input, and the geometry you want to instance to the Instance input. The node adds a geometry reference at each selected point. The Selection input determines which points receive instances; a true value creates an instance, while a false value skips that point.

Rotation controls each instance’s Euler rotation, while Scale controls its size. The positions of the point geometry affect the instances’ transforms, so consider the point layout together with the rotation and scale inputs. Attributes on the geometry can also be used in the instance domain of the created instances.

When Pick Instances is enabled, the node selects from the geometry list instead of using all the geometry in the Instance input at every point. The Instance Index input determines which element is selected. By default, the point ID is used; if there is no ID, the index is used instead. Negative values and values that exceed the list’s size wrap around from the other end of the list. The manual notes that this option is intended to be used with the Collection Info Node.

If the point input already contains instances, the node can add new instances at points inside those instances too, enabling nested instancing. When you need to convert the output instances into separate objects, you can use the Make Instances Real operator. For objects without geometry, such as lights, you can use the Object Info Node; Metaball objects aren’t supported for instancing.

Common mistakes

The most basic mistake is expecting Surface Deform to work without binding: the modifier has no effect before binding. If binding fails, first check the target mesh against the topology requirements in the manual. If binding succeeds but the result is distorted, check whether the target and result surfaces are too far apart.

Another common source of confusion is treating moving or rotating the target object as the same thing as editing the target mesh. Object transforms after binding don’t affect the deformation; changes to the target mesh’s geometry do. Also remember that if you use Sparse Bind, adding vertices to the weight group requires rebinding.

With Instance on Points, Selection values determine whether an instance is created at each point. If Pick Instances is off, the geometry in the Instance input is used at every selected point. When it’s on, the selection is made through Instance Index. Also, don’t assume that every object type is supported: the source specifically notes that Metaball objects aren’t supported.

Next steps for architecture and visualization workflows

In architectural modeling and archviz, Surface Deform can be useful for preparing a simulation or movement with a simple proxy, then transferring that deformation to a more detailed surface. Instance on Points is suited to scenes where the same geometry needs to be used at many points. The manual notes that instances don’t duplicate the underlying data, making them a fast way to add many copies of the same element to a scene.

Before moving to a production scene, test mesh compatibility, target topology, and changes made after binding. For instancing, verify that the point data, selections, and instance rotations and scales produce the expected result. The sources don’t provide information about licensing, hardware requirements, or compatibility with specific versions; check these separately against your Blender installation and working conditions before starting a project.

Sources and license

This tutorial has been adapted into Turkish based on the Surface Deform Modifier and Instance on Points Node guides in the Blender Manual. Both sources are licensed under CC BY-SA 4.0.