Architectural Render Compositing in Blender: View Layers and Color Grading

What will you learn in this guide?

In architectural visualization, you may need to change a shadow, background, or the contribution of a particular material after rendering. Instead of rebuilding the scene or regenerating the entire image for every small adjustment, you can use Blender’s Compositor nodes to separate the image into parts and combine them again. View Layers and render passes make this workflow more flexible.

This guide covers how to start a compositor workflow for a scene, keep render elements separate, manage color, and save the result appropriately. The steps draw on concepts from Blender Studio’s Blender 4.5 LTS compositing tutorial and the Blender Manual’s explanations of the compositor, View Layers, and color management.

Requirements

• Software: Blender. The tutorial source was prepared for Blender 4.5 LTS; the Blender Manual’s explanations of the compositor and View Layers are also used as a reference.

• Scene: A Blender scene that can produce an image to process in the compositor. You can use an architectural interior, exterior, or product scene.

• Account: The sources do not specify an account or membership requirement.

• Output preference: You can save a single image or use the animation button and settings to create an image sequence or a movie file.

Step-by-step compositing workflow

1. Create a node tree in the Compositor

Open the Compositor and click New at the top to create a new compositing node tree. The tree is linked to the scene; it can be reused in other scenes or brought in from other Blender files by linking or appending it.

To make sure the render engine uses this node tree, check that Compositing Pipeline is enabled under Post Processing in the output settings. If this option is disabled, the node tree you created will not be included in the post-render pipeline.

In the Compositor, nodes are added and connected in a graph. You can use them to color-correct an image or combine multiple images. The node-based approach keeps the processing order visible instead of baking adjustments into a single final image.

2. Separate scene elements with View Layers

A View Layer lets you define which collections in the scene contribute to the render. For example, you can handle the background and foreground objects on separate layers, or set up different lighting arrangements as separate View Layers. You can manage collection visibility independently for each layer, so there’s no need to duplicate the entire scene.

You can add a layer from the View Layer list, duplicate existing settings, or create a layer with collections disabled. Manage layer visibility in the Outliner or through a collection’s View Layer properties. The scene must contain at least one View Layer.

3. Select render passes and render again

Render passes provide different types of shading data that contribute to the final image as separate channels. The sources give examples including Combined, Diffuse, Glossy, Transmission, Shadow, Mist, Ambient Occlusion, Cryptomatte, mask data, Normal, UV, and Depth. These can be used for tasks such as masking, color grading, rebalancing certain elements, and investigating image issues.

Enable the required passes in the View Layer settings. Blender Studio’s tutorial includes an especially important reminder: if you enable passes after rendering, you must render the scene again to generate that data. In the Compositor, you can bring the relevant View Layer and passes into your workflow through a Render Layers Node.

4. Adjust the image and compare the result

Processing passes independently allows for more controlled changes in specific areas. For example, you can apply a different compositing effect to a separate background layer or target selected elements with Cryptomatte or object masks. Blender Studio’s tutorial also demonstrates combining render passes and then applying denoising.

Make temporary changes and compare the output to see how they affect the rest of the scene. According to the Blender Studio tutorial, the Compositor preview can be enabled in Viewport Shading; however, not all compositing nodes are supported in this preview. Check the render output as well before settling on a result.

5. Set up color management and save the file

Color management helps ensure consistent interpretation of colors across renders and different display devices. The Blender Manual explains that rendering and compositing are performed in scene-linear color space, and that images such as PNG or JPEG intended for web display should be converted to an appropriate display space. Images that carry data rather than color, such as normal and displacement maps, should be marked as Non-Color Data.

The choice of view transform also affects the appearance of the result. The Manual describes AgX as a transform that handles high-dynamic-range colors; it also notes that Filmic is deprecated and superseded by AgX. Check how the same scene looks with different transforms, and choose a consistent option for the display device and target output.

You can create a single frame with Render and save it with Save Image. The Manual recommends OpenEXR for intermediate files intended for further compositing or color grading. When exporting a render to PNG or JPEG for web display, use Save as Render when the view transform needs to be applied during saving. For an image sequence, the Animation button and settings are used; AVI and QuickTime are examples of movie file formats. If you plan to composite layers later, choose a format that supports an alpha channel, such as PNG.

Common mistakes

• Compositing Pipeline is disabled: The node tree may be set up but not used after rendering. Check the output’s Post Processing settings.

• Not rendering again after enabling passes: A previous render won’t include pass data selected afterward. Finish selecting passes before rendering, or render again.

• Applying a color transform to a data map: Normal and displacement maps carry data, not color. Mark them as Non-Color Data.

• Treating OpenEXR as a final web image: OpenEXR is useful as a linear intermediate file; check the required view transform and save settings when preparing a web output.

• Assuming the preview displays every node: The Viewport Compositor preview may not support every node. Inspect the final render separately.

Impact on architectural and visualization workflows

This method is particularly useful for architecture firms and archviz artists who want to evaluate different lighting scenarios or scene elements separately. Reviewing a lighting change independently of other elements can reduce the need to rebuild the entire scene for each revision. Since different View Layers can share the same collections, you can organize layers according to the scene’s visibility and contribution requirements.

Before starting, decide on the output format, alpha channel requirements, and color management preferences. Also check that the render passes you need are enabled and that any required rerender has been completed. The flexibility of this workflow is not a promise of performance gains or cost savings related to hardware, licensing, or versions—none of which are specified in the sources—and should be tested with your existing scene and team workflow.

Next steps

Start by organizing the background and main objects in a single scene as separate View Layers. Then add only the passes you need and review them individually in the compositor. Run comparison tests while keeping color management settings and save formats consistent. Finally, check that other team members can interpret a layered intermediate file correctly.

Sources and licensing

This guide has been adapted into Turkish from concepts in Blender Studio’s “Compositing Theory” tutorial and the Blender Manual’s sections on compositing, color management, and View Layers. The Manual pages are licensed under CC BY-SA 4.0. The Blender Studio tutorial page identifies its sample project file as CC-BY.