Bump Mapping vs Displacement Mapping in Blender
Understanding the difference between bump mapping and displacement mapping in Blender is essential for creating realistic 3D textures while optimizing render performance. While both techniques are used to add fine surface details like wrinkles, cracks, and roughness to a 3D model, they achieve these results through fundamentally different methods. Bump mapping creates an optical illusion of depth by manipulating how light interacts with the surface, whereas true displacement mapping alters the actual physical geometry of the mesh.
What is Bump Mapping?
Bump mapping is a rendering technique that simulates surface texture without changing the underlying mesh geometry.
- How it works: In Blender, a grayscale texture map (or procedural noise) is plugged into the Height input of a Bump node, which connects to the Normal input of a shader (such as the Principled BSDF). Blender uses the grayscale values to calculate fake surface angles (normals), tricking the render engine into calculating highlights and shadows as if the surface were uneven.
- Performance: It is extremely fast, lightweight, and requires minimal memory because polygon counts remain unchanged.
- Limitations: Because the geometry is flat, the illusion breaks down when viewing the edges of an object (the silhouette remains completely smooth), and the surface cannot cast or receive real self-shadows.
What is True Displacement Mapping?
True displacement mapping physically modifies the vertices of the mesh to create authentic depth and geometric relief.
- How it works: A texture is plugged into the Displacement node and connected to the Displacement socket of the Material Output. To enable true physical displacement in Blender, you must use the Cycles render engine and set the material's surface settings under Settings > Surface > Displacement to Displacement Only or Displacement and Bump.
- Geometry requirements: True displacement requires sufficient geometry to deform. It is typically paired with a Subdivision Surface modifier or Adaptive Subdivision (Micropolygons) to subdivide the mesh dynamically at render time.
- Benefits: It produces completely realistic silhouettes, true self-shadowing, and accurate interactions with light, depth of field, and other intersecting objects.
- Limitations: It consumes significantly more RAM, increases render times, and is computationally heavy compared to bump mapping.
Key Differences at a Glance
- Geometry: Bump mapping keeps the original mesh flat; displacement physically pushes and pulls vertices.
- Silhouettes: Bump mapping leaves object outlines smooth and unchanged; displacement alters the actual outline.
- Shadows: Bump maps only simulate lighting on the surface facing the light; displacement creates real physical occlusions and cast shadows.
- Render Cost: Bump mapping has virtually no impact on render time or memory; displacement mapping demands high vertex counts and longer render times.
- Engine Compatibility: Bump mapping works seamlessly in both EEVEE and Cycles; true micro-displacement is primarily designed for Cycles.
When to Use Each
Use bump mapping for micro-details that do not significantly alter the silhouette of an object, such as pores on skin, fabric weaves, fine wood grain, or subtle scratches.
Use displacement mapping for large, prominent physical deformations where the silhouette and true depth are critical, such as rocky terrain, deep brick mortar, tree bark, or tire treads. Combining both—using displacement for major structural shapes and bump mapping for tiny surface variations—provides the best balance of realism and performance.