Render Passes for Architects: Proven in 1,000 Projects
Render Passes for Architects: Proven in 1,000 Projects
Render passes, also called AOVs, are separate image channels a renderer outputs alongside the final image so compositors can adjust lighting, materials, masks, and effects without a full re-render. For architectural and commercial visualization, that means faster client revisions, precise control over exposure and reflections, and the ability to swap a sky or tweak a shadow in minutes instead of hours. A typical pass set includes beauty, diffuse, shadow, Z-depth, and Cryptomatte.
TL;DR:
- Rendering only the essential passes, such as beauty, Cryptomatte, and Z-depth, reduces storage costs and saves rendering time in architectural projects.
- Using multilayer EXR files in linear color space with proper naming and embedded metadata is crucial to maintain pass integrity and streamline compositing workflows.
- Rebuilding the final image in compositing software should be done in linear space to prevent banding and ensure accurate highlight and shadow rendering.
- Cryptomatte offers reliable, edge-perfect masks that remain accurate through motion blur and depth of field, unlike flat color ID passes.
- Test export pipelines with a single frame before full batch renders to avoid losing critical pass data due to compression or format issues.
Table of Contents
- What Are Render Passes and How Do They Fit Into a 3D Pipeline?
- Common Render Passes and What Each One Actually Contains
- Setting Up Your Pipeline: File Formats, Color Space, and Naming
- Compositing Recipes: Rebuilding and Adjusting the Beauty Pass
- Best Practices for Choosing Passes on Production and Archviz Jobs
- How Rendimension Applies Render Pass Workflows on Real Projects
- Practical Compositing Use Cases Worth Knowing
- The Real Lesson Behind Render Pass Workflows
- Sources
- FAQ
What Are Render Passes and How Do They Fit Into a 3D Pipeline?
A render pass is an intermediate piece of rendering information, split out into its own image rather than baked into the final frame. Blender’s own documentation defines a pass exactly this way: diffuse color, light distribution, depth information, and surface normals each get extracted as a standalone image a compositor can open and manipulate independently, per the Blender manual.
The final rendered frame you’d normally see is the beauty pass, sometimes called the combined pass. It’s every other pass already merged together by the render engine. Raw passes are the individual ingredients: diffuse without shadows, specular without color, ambient occlusion without lighting at all. You need the beauty pass for a quick look and client sign off. You need the raw passes when someone asks to punch up the reflections on the glass curtain wall three days after the render was approved, and you don’t want to wait another six hours for the GPU farm to finish.
A few terms come up constantly in this workflow:
- AOV (arbitrary output variable): the general term for any extra data channel a renderer can output beyond the beauty image.
- Render layer: a grouping mechanism, often used to separate objects or collections into their own output stream.
- Multilayer EXR: a single file format that can hold dozens of passes at once, preserving full precision and metadata.
- Cryptomatte: an ID system that stores per-object and per-material data so a compositor can generate pixel-perfect masks after the fact.
Passes get generated at the engine level, inside the render layer stack, or through dedicated output systems like Unreal Engine’s Movie Render Queue, which can export the final image plus object IDs, depth, and motion vectors for use in external compositing, according to Epic’s own documentation. The reason studios bother with all this: compositing freedom, targeted fixes without touching the 3D scene, and the ability to absorb late client-driven changes without blowing the schedule.
Common Render Passes and What Each One Actually Contains
Here’s the practical reference most compositors keep taped to their monitor, mentally if not literally.
- Beauty/combined: the fully composited final image, every pass merged by the renderer.
- Diffuse (albedo): base surface color with lighting stripped out, useful for repainting materials without relighting.
- Specular/reflection/glossy: highlights and mirror-like reflections, isolated so you can dial intensity up or down.
- Shadow pass: direct shadow information you can multiply back in, lighten, or offset.
- Ambient occlusion (AO): contact shadows and crevice darkening, often blended at low opacity to add grounding.
- Z-depth: distance-from-camera data, the backbone of depth of field and atmospheric haze effects.
- Normal pass: surface direction data used for relighting tricks and edge-based filters.
- Cryptomatte/IDs: encoded per-object and per-material data for instant, precise masking.
- Emission, subsurface, transmission/refraction, motion vectors: specialty passes for glowing signage, skin or wax-like materials, glass, and motion blur respectively.
Architectural-visualization best practice leans on a fairly tight core set. Guidance from Maxon’s architectural rendering article recommends beauty, cryptomatte/IDs, global illumination, reflection/specular, and Z-depth as the baseline, because that combination gives a compositor control over exposure and separation without ever touching the 3D file again.
Statistic Callout: Cryptomatte stores ID data across multiple sample layers per pixel rather than a single flat color, which is why it keeps working cleanly through motion blur and depth of field where old-fashioned color-ID passes break down, per Maxon’s guidance.
The most common mistake: rendering every pass “just in case” on every frame of a large image sequence. Motion vectors matter enormously on an animated walkthrough and mean nothing on a single hero still. Subsurface scattering matters for a skin-like material and is dead weight on a concrete facade. Match the pass list to the shot, not the other way around.
Setting Up Your Pipeline: File Formats, Color Space, and Naming
Get the export settings wrong and every pass you rendered becomes useless the moment it reaches a compositor. A handful of rules keep the handoff clean:
- Use multilayer EXR with linear color space (gamma 1.0). Linear math is what makes pass math behave predictably, and EXR preserves full floating-point precision through every compositing operation. Blender’s render layers documentation backs this as the standard for multi-AOV interoperability, per the Blender manual.
- Choose bit depth by purpose. 16-bit half float is fine for most color passes and keeps file sizes manageable; reserve full 32-bit float for Z-depth and any pass feeding heavy mathematical manipulation, where rounding errors show up as banding.
- Decide multilayer versus single-layer deliberately. One multilayer EXR per frame keeps a project folder sane. Split into single-layer files only when a specific compositing tool in the pipeline can’t read multilayer EXRs, which still happens with some legacy Photoshop workflows.
- Standardize naming. Something like
SceneA_Frame0120_beauty.exrbeatsrender1_final.exrevery time a project resurfaces six months later for a revision. - Bake in metadata. Scene name, frame number, and AOV name embedded in the file header save enormous time when a compositor opens a folder of 40 sequences at once.
- Verify Cryptomatte and motion vectors survive export. Both are easy to accidentally strip when compressing EXRs or converting formats; check a test frame before rendering the full sequence.
Pro Tip: Render one full test frame through your entire export pipeline, including whatever compression settings you plan to use, before committing to an overnight batch. Catching a stripped Cryptomatte layer on frame one costs five minutes; catching it on frame 4,000 costs a weekend.
Compositing Recipes: Rebuilding and Adjusting the Beauty Pass
Once the EXRs land in Nuke, After Effects, or a similar compositor, a handful of repeatable recipes cover most production requests.
Rebuilding beauty from raw passes. Multiply the diffuse pass by its lighting/AO contribution, then add specular and reflection passes in screen or add mode on top, keeping every operation in linear space until the final tone-mapping step. Doing the math in linear space and only converting to display gamma at the very end avoids banding and wrong-looking highlight roll-off, a point emphasized in OTOY’s beauty pass documentation. Skip this discipline and blown-out windows or glowing chrome trim start looking clipped and flat instead of bright.
Depth of field and atmosphere from Z-depth. Remap the depth pass to the focal range you need, clamp the far end so background haze doesn’t wash out to solid white, and feed the result into a refocus or fog node. A few practical steps:
- Normalize the Z-depth range to the camera’s actual near and far clip values.
- Clamp extreme values so sky or infinite backgrounds don’t blow out the effect.
- Feed the clamped depth into a defocus node for DOF, or a fog/atmosphere node for haze.
Motion vectors for motion blur. These only work correctly when generated with the exact same shutter timing as the beauty render; a mismatch produces smeared or doubled edges, a known pitfall documented in Blender’s compositing docs.
Using Cryptomatte for isolation. Pull a Cryptomatte node, click directly on any object or material in the viewer, and get an instant, edge-perfect mask, even through glass or foliage. That single click replaces what used to be twenty minutes of rotoscoping around a tree canopy.
Selective denoising. Denoise noisy AOVs like diffuse or GI individually before recombining them into beauty, rather than denoising the finished composite. Denoising the final beauty pass tends to smear fine detail across every material at once; denoising component passes lets you protect sharp edges where they matter, like window mullions or signage text.
Best Practices for Choosing Passes on Production and Archviz Jobs
Not every deliverable needs the full pass stack, and treating every render like it does is how storage bills and render farm queues get out of hand.
For a hero marketing image, request the full set: beauty, diffuse, specular/reflection, shadow, AO, Z-depth, normal, and Cryptomatte. That image is going on a billboard or a developer’s homepage, and every bit of post-production flexibility earns its file size.
For bulk client preview batches, beauty plus Cryptomatte is often enough. Clients reviewing forty unit layouts for a condo development need to approve the look, not fine-tune reflections on each one. Some industry guidance is blunt about the tradeoff: choosing passes by actual project need, rather than rendering every AOV by default, keeps file bloat and render time under control.
A short QC checklist before any handoff:
- Confirm gamma is set to linear, not sRGB baked into the raw passes.
- Verify Cryptomatte layers survived any compression step.
- Check that channels are properly packed in the multilayer EXR, not scattered across mismatched single files.
- Match every naming convention across the full sequence, no exceptions for “just this one frame.”
Pro Tip: Keep a one-page pass manifest per project, listing exactly which AOVs were rendered and why. When a client asks for a change eight months later, that manifest tells you in ten seconds whether you already have what you need or have to re-render from scratch.
How Rendimension Applies Render Pass Workflows on Real Projects
Rendimension typically delivers a working set of beauty, Cryptomatte, Z-depth, reflection, and ambient occlusion passes on marketing-grade architectural imagery, matching the same pass logic covered above: enough control to handle client revisions without touching the 3D scene again, supporting Architecture SEO Services | Be Discovered & Win Better Projects. EXRs are organized and handed off with clear naming and comp notes so an internal or client-side compositor can pick up the file and understand exactly what’s inside it.
That workflow discipline comes from having built it across more than 1,000 completed projects spanning residential and commercial developments. The process stays collaborative from concept through final delivery, which matters most exactly at the pass-selection stage. A developer who knows their marketing team will want to swap the sky in six months needs a different deliverable than one who just needs forty unit previews approved by Friday.
Practical Compositing Use Cases Worth Knowing
Color grading gets far easier with separated passes: adjusting the diffuse pass alone lets you shift material tone without dragging shadows or highlights along with it. Exposure control benefits the same way, since a beauty pass baked into one flat image forces global adjustments, while raw passes let you brighten interior glow without blowing out an exterior facade.
Replacing a sky is one of the most requested archviz edits, and it’s trivial with a Z-depth or alpha mask isolating everything above the horizon line, no rotoscoping required. Adding depth of field after the fact, using the Z-depth recipe covered earlier, saves a full re-render when a client suddenly wants a shallower, more cinematic look on a hero shot.
Selective denoise, applied to individual AOVs before recombination, protects fine detail on window frames and signage that a blanket denoise pass would soften. Mask creation through Cryptomatte turns what used to be tedious manual selection work, tracing around landscaping or glass railings, into a single click in the compositor. For a deeper look at how this fits into a full architectural post-production workflow, see Rendimension’s notes on post-production for architects.
The Real Lesson Behind Render Pass Workflows
Most advice on render passes treats “more AOVs” as automatically better, and that’s where a lot of teams waste render time and storage for no real benefit. The honest priority order is different: figure out what the deliverable actually needs to survive contact with a client’s second and third round of feedback, then render exactly that set, nothing more.
Conventional guides also underplay how much the export step matters compared to the render step itself. A perfectly rendered Cryptomatte pass that gets stripped during a careless EXR compression pass is worthless, and that failure happens far more often than anyone admits. If there’s one thing worth prioritizing before anything else on this list, it’s testing your export pipeline on a single frame before you commit a farm to an overnight batch.
For architectural and marketing visualization specifically, the pass list isn’t really a technical decision. It’s a bet on what the client will ask for next month. Bet conservatively on bulk previews, generously on anything with “hero” or “marketing” attached to it.
, Rendimension
Sources
- Passes - Blender 5.2 LTS Manual
- Cinematic Render Passes in Unreal Engine
- Architectural rendering techniques (Maxon)
- Beauty Passes (OTOY docs)
FAQ
What Is a Render Pass?
A render pass, or AOV, is a separate image channel a renderer outputs alongside the final image, isolating one element like diffuse color, shadows, or depth so it can be adjusted independently during compositing, as defined in the Blender manual.
How Do I Use Render Passes in Maya?
Maya-based pipelines follow the same core workflow covered above: enable the AOVs you need at the render layer level, export as multilayer EXR in linear color space, and bring the file into a compositor like Nuke or After Effects to recombine or adjust passes non-destructively.
Which Passes Should I Always Render for Architectural Work?
Beauty, Cryptomatte/IDs, global illumination, reflection/specular, and Z-depth form the recommended baseline for architectural imagery, according to Maxon’s guidance, since that combination covers exposure control and object separation without a re-render.
Why Use Cryptomatte Instead of Color ID Passes?
Cryptomatte stores ID data across multiple sample layers per pixel, so masks stay clean through motion blur and depth of field, while flat color-ID passes tend to break down in exactly those situations.
What File Format Should Render Passes Be Exported In?
Multilayer EXR in linear color space is the standard, since it holds many AOVs in one file at full precision without the gamma and compression issues that come with formats like PNG or JPEG.