Render layers: Blender View Layers and Maya Render Setup

You change one wall colour, hit render, and wait the same eight minutes as always. It is not your machine: you are rendering the whole scene in one go. Render layers exist for exactly this, and Blender and Maya build them differently.

What a Render Layer Is (and What It Is Not)

The Blender manual puts it plainly: a view layer lets you split the render into several layers that are composited afterwards, so you can process elements separately -characters, lighting variants, background- without duplicating the scene or reprocessing everything each time something changes. Its three classic cases: different compositing effects for background and foreground, characters rendered apart from the environment, and lighting variants that leave the original setup untouched. I add the fourth, the one that changed how I work: iterating.

And the confusion worth killing up front: a layer is not a pass. The layer decides which objects enter the render; the pass, or AOV, decides which channels come out of it. Passes are already covered in compositing render passes and AOVs; here I build the layer that feeds them.

View Layers in Blender: Where Render Layers Are Built

View layers live in the View Layer tab. The list of scene layers sits at the top and you rename them with a click: renaming is not cosmetic, it is the difference between understanding a file and guessing what the person before you did. The Add View Layer button offers three options:

• New: an empty layer.
• Copy Settings: duplicates the current layer with collection visibility and its overrides.
• Blank: every collection disabled, to build from scratch.

Every scene needs at least one layer, and every layer references a combination of collections: they define visibility, selectability and how much each object contributes, and several layers can share them. Which leads to what most people skip: the scene gets organised into collections before you think about layers. That groundwork is in organising a project with collections and the Outliner.

Per-Layer Collections: The Switch Almost Nobody Uses

Each collection's visibility is set per layer, from the Outliner or from the collection properties inside the layer: one object can sit in two layers without being duplicated. Only in Cycles do two key switches appear there:

• Holdout: cuts a hole in the render and leaves alpha transparency, so that element can be composited separately.
• Indirect Only: the collection is invisible but still lights the scene, the fill background that bounces light without showing up in camera.

In EEVEE neither exists and the plan changes: better read EEVEE vs Cycles before promising a workflow the engine does not support.

Render Layers in Practice: Seven Minutes of Scene, Forty Seconds of Layer

This is not in the manual, it is what I use in class: three layers solve eighty percent of jobs. LAY_FG character, LAY_BG environment, LAY_FX volumetrics and anything burned in post. The golden rule: one layer per post decision, not one layer per object. If nobody will touch that element separately it does not deserve a layer, and every extra layer multiplies setup time.

Two warnings. The engine belongs to the scene, not to the layer: you cannot have one view layer on Cycles and another on EEVEE in the same scene; that takes two scenes and you lose shared layers. And the cost: each layer is a full render of its subset, two layers are not half the time, and the panel does not document per-layer samples. What you gain is iteration, not speed on the first render; when samples are the bottleneck, the road is optimising Cycles.

Render Setup in Maya: Layers, Collections and Overrides

A warning that saves an afternoon: Maya has two systems, the new Render Setup (default) and the old legacy render layers. They do not coexist: you pick one in Preferences - Rendering and restart Maya. The official flow is four steps: create layers; populate them with collections -you do not add objects, you add collections by selection, by expression (membership is by name, so it updates itself) or by combination-; create overrides per collection, which are non-destructive; and mark layers as renderable to launch the batch.

Above everything sits the scene layer, shown as masterLayer: it controls global settings and accepts no collections or overrides, the way back when something looks wrong.

Overrides: Absolute, Relative, and Why Order Matters

An override lives in the layer, not in the object. Absolute sets the exact value; relative multiplies or adds on top of the original: with Translate at 10, a x5 and then a +2 leaves 52. You create them by dragging the attribute into the Property Editor with the middle mouse button, one attribute per override, and they can be disabled without being deleted.

The detail that bites: the order is top-down. If two collections share objects and both override the same attribute, the lower one wins, and you reorder by dragging; lights are overridden per layer the same way. And when the override targets a node type the collection does not include -typical with shaders- Maya creates automatic subcollections so the calculation only runs on applicable nodes: better performance, on the condition that a subcollection can only contain a subset of its parent, or the object will not show up.

With Arnold this intersects lights and materials, so it pays to have lights and materials in Arnold and the utility shaders for mattes solid first.

When the Layers Reach the Compositor

In Blender each layer shows up in the Compositor as a Render Layers node: properties Scene and View Layer -the button next to the dropdown re-renders it instantly- and outputs Image, Alpha and one socket per enabled pass. It can output combined, diffuse or shadow, Cryptomatte and object ID, or data like normal and depth: four or five well chosen ones cover almost everything.

A gotcha that confuses many: the viewport compositor only supports passes with EEVEE; on other engines the pass outputs stay empty, and if you see a node with no channels, that is why.

In Maya the batch creates one folder per layer named after the layer, so name it like the final image, and the whole setup exports and imports as .json: build a master setup and reuse it shot after shot.

The deeper difference: in Blender you composite inside the file; in Maya you almost always deliver multilayer EXR and composite outside, either in the built-in compositor -explained in compositing a VFX shot- or in a post application, as in taking the 3D render into After Effects. Either way, colour management is decided before delivery.

Shadow Catcher: The Case That Breaks the Layer Logic

Cycles has a shadow catcher checkbox in the object properties, and its result changes depending on whether the Shadow Catcher pass is enabled in the layer: with the pass, the full indirect light interaction is captured; without it, a simple approximation. It is the best example of why layer and pass are not the same thing. The full workflow is in integrating a 3D model into a real photo.

Five Layer Mistakes I See in Class

• "I split two characters into two layers and they cut into each other": in Maya, one layer with both and an override that mattes one against the other; in Blender, holdout.
• "My background layer lights too much": it contributes direct light. Indirect Only in Cycles, or take the collection out of the layer.
• "The override does nothing" (Maya): the node is not in the collection. Check View All, the Collection Filter and the name.
• "I changed layers and the render did not change": the wrong layer got rendered, or that layer is not marked renderable.
• "I come from legacy render layers and cannot find anything": switch systems in Preferences and restart Maya.

And one that is not about layers but always shows up: if the layer comes out noisy the problem is sampling; the shortcut is the denoiser in Maya and Blender.

Conclusion

Rendering in layers is not an advanced option: it is the difference between waiting and working. The first time costs you the setup, the second gives you the afternoon back. The test: will you touch that element in post? Its own layer. Is it only a wall changing colour? That layer. Will nobody touch it? Do not split it.

To see it moving, the platform has How to use render layers in Blender and, for the compositing side, How to Render Passes and Blender Compositor: using layers. You can browse the Blender category and, if you come from Maya, the Maya one. No promises beyond what is there: I still have no curated Render Setup video.