Useful passes, an EXR you can truly pick up and work with

Turn every retouch request into the data it requires

Start with a concrete sentence: adjust the color of an object, balance a light element, separate a background or redo the denoising. Pair every request with a piece of data and a control. If no one can explain what a pass will let them modify, it has no clear reason to be in the delivery yet.

In Blender, a pass exposes intermediate render information. Combined is the render result before compositing. So you should not assume it includes the corrections and effects added later in your node tree. Give the recipient a reference that actually matches the approved stage. The passes manual explains their role.

Also ask whether the recipient wants elements ready to composite or a technical breakdown to rebuild. The second request implies a shared method. Stacking all the layers in Add mode does not automatically reconstruct the render: some describe colors, others masks or data.

Use masks without asking them to rebuild the scene

Cryptomatte lets you isolate objects or materials from the dedicated passes. In Cycles, the manual documents in particular how it handles transparency, motion blur and depth of field. That capability does not mean every optical contribution of the object becomes independently editable. The Blender 4.5 LTS documentation lays out the categories and their coverage.

Test the real case: a partially hidden object, a blurred edge, a material shared by several parts. A local correction should follow the expected selection. If it also changes another element, examine the type of mask chosen and the organization of the objects before painting a fix on every frame.

Avoid changing names and scene structure between the accepted test file and the full render without warning. A usable mask depends on what was rendered and on what the recipient knows how to select. A request for a new camera, different geometry or a physically consistent reflection may require going back to the scene, even with good masks.

Choose the container together with the end viewer

Agree on an OpenEXR containing the necessary layers and check that the destination application can find them. Blender's Image node exposes the layers of a multilayer EXR, but reading it in Blender does not prove that another piece of software can. Ask for the reader's name and version, then exchange a test file before producing the sequence. The Image node manual describes the internal reading.

OpenEXR accepts several channel types, including 16-bit floating-point HALF and 32-bit FLOAT. The choice depends on the precision the data requires; 16-bit float is not the same representation as a 16-bit integer. Keep the precision required by the technical passes and verify how they are decoded, especially for IDs. For a diagnostic test file, lossless compression avoids adding an approximation to the pixels.

The format also distinguishes the full display window from the area containing data. A cropped file may therefore open with an offset if the reader misinterprets this organization. Check the dimensions and placement on the canvas, especially after a region render. The OpenEXR documentation defines these elements.

Example: a lamp, its shade and its emission

Let's take an illustrative Cycles delivery for Blender 4.5 LTS, to be checked in the receiving software: a ceramic lamp, a fabric shade and a plain background. The recipient wants to rebalance the shade slightly, change the title and control a glow added in compositing. They are not planning a new camera or a change of lighting in the scene.

The first proposal includes the Combined render, a Cryptomatte mask allowing the shade to be selected, and the reference composite output. The glow, added after rendering, is provided separately if its setting is to remain independent. We do not claim that it is automatically included in Combined. A test EXR is opened in the receiving software; the mask is tested where the shade meets the base and in its thin areas.

Now suppose the request changes: the tint of the base needs to be modified, including its reflection in a nearby surface. The base's mask does not necessarily resolve that whole interaction. We decide whether a limited retouch is acceptable or whether the scene needs to be redone. That decision is worth more than a promise of total freedom based solely on the number of passes.

The accepted test file becomes the technical reference for the series: same layers, same reading, same naming. It remains distinct from the artistic approval of each new image.

Prepare a reading sheet that is short but sufficient

Include an understandable description of each layer, its role and its state: raw, filtered or composited. Identify the color space, the alpha convention and the settings needed to retrieve the visual reference. Don't leave the recipient guessing whether the view transform has already been applied to the pixels.

For an animation, add the sequence range, the frame rate and the mapping between file names and frame numbers. Give an example that is genuinely representative of the planned naming. The frame rate of sequences deserves a separate check: correctly read layers can still be assembled at the wrong pace.

Describe the operations that remain possible and those that require the source project. A note like "mask for light adjustment of the shade; lighting change to be redone in the scene" helps more than a general mention of "all retouches." The guide exporting a project covers the full structure of the archive; this sheet focuses on reading the EXR.

Check the opening before accepting the delivery

Open the file from a delivery copy, in a clean session of the receiving software. Find the layers by name, display them separately, then make a small modification matching the intended use. If the operation requires an element that is missing, the delivery is not yet complete even if the file opens without errors.

Check the mask, the placement, the colors and the alpha. For Depth, pay particular attention to the edges: the manual states that this pass is not antialiased. A distance data pass is therefore not interchangeable with an image already softened for a visual effect. Do not arbitrarily replace an expected pass without retesting the composite.

On a sequence, check the beginning, the end and a portion containing the difficult elements. Playing back every frame and the presence of the announced layers are part of the delivery check; the assessment of edges and motion remains visual. Note any defects found with a frame number and a precise area.

Link intake to a portable project folder

The folder Pli, preparing your Blender files targets Blender 4.5.x LTS and provides a concrete method for organizing assets, reconstruction and acceptance. The 5.x references in this guide do not extend the pack's advertised compatibility. Its published checks cover the pack's file structure and dependencies; they do not prove that a Blender render or an EXR from your project was executed and received correctly.

You can apply this discipline to your own delivery: keep immutable sources separate from outputs, fill in an acceptance record for the files actually produced, and keep the validated reference. Moving on to the full render then depends on this check and on the project schedule. Passes give you room for targeted reworking, not an unlimited reserve of computation already performed.