Blender View Layers and Render Passes: An Archviz Guide

The Blender 5.2 LTS documentation explains that View Layers and render passes let you split scene elements into separate outputs for independent adjustments in the Compositor. In architectural visualization, this approach can help you control elements such as the interior, background, and lighting components without being locked into a single result. The steps below will help you set up layers and passes for the same scene and choose the data that suits each task.

1. Organize your scene with View Layers

First, arrange scene objects into Collections according to their purpose. View Layers can use different combinations of these collections, so you can keep interior furniture, surrounding elements, or specific decorative objects in separate render layers, for example. This lets you define which collections are visible in each layer without duplicating the entire scene.

1. Add a new layer from the active scene’s View Layer list. The documentation describes options for creating an empty layer, copying the current settings, or starting with collections disabled.

2. Give the layer a descriptive name. Clear layer names make it easier to track which elements each output contains as the scene grows.

3. Set collection visibility for the relevant View Layer in the Outliner or Collection View Layer Properties. If you’re using Cycles, you can also manage holdout and indirect-only options for collections.

4. Check that each layer makes a distinct contribution. Avoiding recalculation of unchanged layers can keep the workflow flexible during iteration.

A scene must contain at least one View Layer. Layers are not duplicated scenes: the same collections can be used in multiple layers, with visibility configured differently in each one. This lets you separate the background or specific scene elements while keeping the underlying scene structure intact.

2. Choose render passes for the task

Render passes output intermediate data generated during rendering as separate images. You can access them through the Render Layers Node in the Compositor, then adjust the final image by combining the data in different ways. Select passes in Properties › View Layer › Passes.

The Depth pass can be used with the Defocus Node for depth-of-field effects. However, Depth can produce noisy results if the render itself has depth of field or motion blur; in that case, the documentation recommends the Mist pass for a cleaner image. Mist can also be used to fade distant objects.

3. Manage masks and lighting separately

Cryptomatte is a practical option when you need to select a specific object or material for color or visibility adjustments. The documentation notes that it is easier to set up than Object Index and Material Index passes, can be used with other compositing software, and supports multiple objects per pixel. In Cycles, it can also work with transparency, motion blur, and depth of field.

For a more specialized mask, consider the Object Index or Material Index passes. These are available in Cycles and can be turned into masks with the ID Mask Node. Note that the Depth, Position, Object Index, and Material Index data in these passes are not anti-aliased. It’s important to check how the edges look in the final composite.

Cycles offers Light Groups for adjusting light sources individually after rendering. Each group produces a limited Combined pass in which only specific lights illuminate the scene. You can combine these outputs in the Compositor and change the color and intensity of individual lights without rendering the scene again. Don’t assume this option is available in EEVEE; the documentation describes Light Groups as Cycles-only.

4. Combine layers in the Compositor

Once rendering is complete, each View Layer can be used in the Compositor through a Render Layers Node. Connect the required layers and passes first, then combine and adjust the images for their intended purpose. Re-rendering only the changed layer can make iteration more flexible. However, as the number of layers grows, it also becomes more important to keep track of the scene organization and output names.

The Blender 5.2 LTS documentation highlights several EEVEE limitations: depth of field and motion blur are not rendered in passes other than Combined; they can be simulated in the Compositor with the Defocus Node and Vector Blur Node. Transparent materials set to Blended are also not rendered in passes other than Combined and Transparent; the documentation recommends using Dithered in this case. It also notes that the Shader To RGB Node works correctly only in the Combined pass in EEVEE, and that there can be up to 16 AOVs each of the Color and Value types.

Impact on architecture and archviz workflows

Using layers and passes for material masks, lighting changes, or background separation in interior design presentations can reduce the need to rebuild the entire scene for every revision. Visualization teams that want to select and adjust specific objects after rendering can benefit from Cryptomatte; Cycles users who want to control the contribution of different lights separately can use Light Groups.

Before starting, clarify which render engine you’ll use and what post-production adjustments are needed. Denoising Data passes can increase memory usage and render time, so don’t enable them unnecessarily if you won’t be denoising in the Compositor. If you’re using EEVEE, check its pass limitations; if you plan to export to other compositing software, test mask and output compatibility in advance. The documentation does not specify hardware requirements or licensing terms; hardware impact should be measured with your scene and chosen outputs.

Common mistakes

• Enabling every pass just in case: Denoising Data can increase memory usage and render time, so select only what you actually need.

• Assuming every effect will show up in every EEVEE pass: Check the documented limitations for depth of field, motion blur, and Blended transparency.

• Using the Depth pass directly in every scene: Results can be noisy in renders with depth of field or motion blur; consider the Mist pass.

• Skipping a check of mask edges before arranging layers: Some data passes are generated without anti-aliasing, so edges may look different than expected in the composite.