
Check the individual image output's Override Node Format setting. Blender's File Output node can give an image output its own format settings instead of inheriting the node-wide format. A mismatched file is therefore not necessarily evidence that the whole render used the wrong configuration.
Key Takeaways
- Review node-wide settings and each image output's override separately.
- Confirm resolved output paths before rendering a full sequence.
- Treat image outputs and multilayer EXR layers as different delivery structures.
Inspect the affected output rather than the whole graph
The Blender File Output node documentation describes per-image Override Node Format. This matters when a node sends several related deliverables to disk: a review image may legitimately need a different format from a compositing intermediate.
Find the specific output connected to the unexpected file. Compare its override state with the node's main format and with neighboring outputs. If the override is enabled intentionally, inspect its own settings. If it is accidental, return it to the agreed inheritance behavior rather than changing all outputs to suit one file.
Do not assume that two outputs sharing one node share every effective setting. Conversely, do not remove a deliberate override solely to make the interface look consistent. The correct state depends on the recipient's requirements for each asset.
Define each deliverable before changing formats
Write a separate specification for each output. Suppose a compositor requests two illustrative deliverables:
| Output | Proposed format and precision | Setting to inspect | Acceptance task |
|---|---|---|---|
| review.png | 8-bit PNG preview | Deliberate per-image override | Recipient can inspect the approved composition |
| comp.exr | 16-bit floating-point OpenEXR intermediate | Node format inherited, override disabled | Receiver reads the required channels and precision |
These are hypothetical requirements, not universal Blender defaults. Confirm that the installed version offers the required format and precision before agreeing to this pair. Also agree on color interpretation and alpha. A display preview and a compositing intermediate should not be judged by equal file size or identical unmanaged thumbnails.
Record both the node-wide format and the override state beside each filename. If comp.exr was accidentally assigned the preview's override, restore its agreed format on that output rather than changing the valid review copy.
Blender's documentation distinguishes image outputs from multilayer EXR organization. In the multilayer case, inputs describe layers within that structure. Confirm whether the receiver wants separate files or channels/layers in one EXR before reorganizing the node.
A separate render pass must also exist and be connected correctly. A File Output node cannot create depth or a custom pass from an unrelated combined picture. The Scene strip pass limitation guide explains why a film-editing strip should not be assumed to carry every render pass into this workflow.
Check paths and a representative frame
Inspect the resolved output paths before a long render. Distinct labels are not enough if effective paths collide or point to a previous delivery folder. Use a new, clearly named test location so an old file cannot be mistaken for the latest result.
Render a representative frame through the intended graph and open every required output in the receiving application. For the hypothetical handoff, the proposed acceptance check is that each expected file exists, uses its agreed format and exposes the required image or data correctly. Check the actual file, not just the node label.
If the result is still wrong, trace the input connection, relevant pass and output-specific settings in that order. A correct format cannot repair the wrong upstream signal. For custom shader outputs, the AOV naming and type guide offers a separate diagnostic boundary. Keep the accepted test frame and a concise output specification with the project before starting the full batch.
Related tasks
- Can a Blender Scene Strip Deliver Separate Render Passes to My Film Edit?
- Why Are My Blender Compositing Nodes Not Affecting the Video Strip?
- Why Is My Blender Shader AOV Missing the Intended Material Values?
Sources and scope
- File Output Node: Individual output images can override the node format.; Multi-layer EXR stores inputs as separate layers.; Output Paths displays the resolved paths and extensions for inspection.
Documentation-based guidance; example settings and acceptance checks are proposed rather than reported measurements.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.