Choose PNG for sRGB output at 8 or 16 bits, EXR when you need a scene-linear file with a float bit depth, and AVIF for supported grayscale or RGB output where its YUV420 options fit the delivery. Set input_color_space to describe the tensor you actually have, not the appearance you want. Before saving, confirm the channel count: AVIF rejects RGBA, while PNG and EXR accept only 1, 3, or 4 channels.
Decide from the input and delivery
Use this order for a still-image workflow:
- Read the image input’s actual type or channel information in the workflow. Node colors can be a clue, but use the displayed type label as the deciding evidence. The Save Image Advanced documentation defines the accepted counts, but does not describe a universal way to inspect every upstream tensor.
- Pick a format based on the receiving workflow. The PNG controls in this node provide only an sRGB
input_color_spaceoption, so use PNG as the matching choice only when the input is actually sRGB-encoded or an upstream step has explicitly produced sRGB. Choose EXR when the destination expects scene-linear data or floating-point precision. Choose AVIF when its supported channel layout and compression settings suit the use case. Selecting PNG does not by itself verify or convert an arbitrary input encoding. - Match
input_color_spaceto the input encoding. For EXR, the documented choices are sRGB-encoded Rec.709, HLG-encoded Rec.2020, or already scene-linear Rec.709. The node writes EXR as scene-linear in the matching gamut, applying the documented inverse transfer function for sRGB or HLG. For AVIF, select sRGB, HDR (BT.2020/HLG), or HDR PQ (BT.2020/PQ) according to the input. PNG exposes only sRGB. - Select a supported bit depth, then check channels against the format. PNG offers 8 or 16 bits; EXR offers 16-bit or 32-bit float; AVIF offers Auto, 8-bit YUV420, or 10-bit YUV420. Auto is documented as 8-bit YUV420 for sRGB and 10-bit YUV420 for HDR.
- Save a small representative output and inspect the resulting file in the intended receiving application. Treat this as your delivery check, not as proof that a particular format restores clipped or missing source information.
The node’s official documentation lists these conditional controls and channel constraints. Its EXR color-space descriptions are especially important: choosing EXR does not by itself tell the node how the input is encoded.
Acceptance worksheet
The rows below are hypothetical diagnostic observations, not measured results or guarantees. Use them to record what you know about an input and make a format decision; replace the example observations with evidence from your own workflow.
| Hypothetical input and delivery need | Candidate settings | Check before accepting |
|---|---|---|
| Input is verified as sRGB-encoded, or an upstream step explicitly produced sRGB; delivery requests PNG with more than 8-bit storage | PNG, 16-bit, sRGB | Record the upstream evidence or conversion step that establishes the sRGB encoding, then confirm the receiving application reads the saved PNG as intended |
| 3-channel HLG Rec.2020 input; downstream tool requests floating-point scene-linear output | EXR, 16-bit float or 32-bit float, HDR | Verify the input encoding with its upstream workflow; do not label an unverified signal as HDR |
| 1-channel grayscale sRGB input; compact AVIF delivery is acceptable | AVIF, sRGB, Auto | Confirm the receiving workflow accepts the AVIF and its selected YUV420 mode |
| 4-channel RGBA image with transparency required | PNG or EXR, subject to input color-space and bit-depth needs | Reject AVIF for this source; the documented node does not support alpha in AVIF |
For EXR, use the lower float option when it meets the receiver’s requirements; the documentation says it produces smaller files than 32-bit float, but does not claim that it is sufficient for every project. For AVIF, crf ranges from 1 to 63 and lower values are documented as producing higher quality and larger files. Set it according to delivery needs and inspect the result; do not assume a particular value preserves every detail.
Limits and what to do when saving fails
A PNG request cannot select HDR or linear input color space in this node. If the input is not sRGB-encoded, do not treat the PNG control as a general color-space conversion option; use a workflow that explicitly produces the needed encoding, or choose a format whose documented input choices match it.
If the channel count is unsupported, change or prepare the input in an appropriate upstream image workflow, then verify its actual channel type before retrying. PNG and EXR reject counts other than 1, 3, or 4. AVIF accepts 1 or 3 and rejects 4-channel RGBA. The documentation does not specify how a particular upstream node creates, removes, or converts channels, so do not assume selecting a save format will do that work.
If the file saves but looks wrong, re-check the input encoding and the selected color-space control before changing bit depth. Bit depth alone is not a documented remedy for incorrect color interpretation. If the receiving application still cannot use the file, confirm its format and encoding requirements and create another output with matching settings. Save Image Advanced also supports animated AVIF, but frame rate and loop settings are a separate decision from the still-image format and channel checks covered here.
Does 16-bit PNG mean floating point?
No. The documented PNG choices are 8-bit and 16-bit; the floating-point choices belong to EXR.
Which EXR color-space option should I choose?
Use sRGB for sRGB-encoded Rec.709 input, HDR for HLG-encoded Rec.2020 input, and linear for input already scene-linear in Rec.709 primaries.
Can AVIF preserve an alpha channel here?
No. This node’s documented AVIF input supports grayscale or RGB, not RGBA. Choose PNG or EXR when the output must retain a supported four-channel input.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.