
Affinity Photo 2 can import an OpenEXR alpha channel as a separate layer ending in .A. That is the documented default when Associate OpenEXR alpha channels is disabled. Enable association when the intended workflow needs that alpha merged into its associated RGB layer's alpha, rather than treating a separate .A layer as proof that the render is damaged.
Key Takeaways
- Separate alpha and associated alpha are different import representations.
- Alpha association is distinct from dividing RGB values by alpha.
- Compare import choices using copies of the original render.
Read the imported channel structure
The official OpenEXR reference documents these options under Colour settings. It also describes multichannel import as separate layers retaining channel affixes. Start by locating the expected RGB and alpha components, rather than deleting unfamiliar layers until the picture looks plausible.
For a proposed product render, suppose the renderer delivers color and transparency for an object on an empty background. Your next task may be a composite that needs RGB-layer transparency, or a pass inspection where retaining the alpha separately is useful. The correct representation follows that task.
Compare association without mixing other changes
- Keep the original EXR in a protected source location.
- Note the current alpha-related import settings.
- Open a separate copy with the intended association choice.
- Inspect the layer names and the RGB layer's transparency against a contrasting background.
- Compare recognizable opaque, partially transparent and empty regions.
This is a proposed inspection plan, not a measured result for a particular renderer. Do not assume every layer ending in .A is a disposable duplicate; it may be a component the recipient expects to inspect or process.
Review division as a separate decision
The manual also exposes Post divide EXR colours by alpha, plus Perturb zero EXR alpha for the zero-alpha case when division is enabled. Those controls address color-channel interpretation, not simply where alpha appears in the Layers panel. Enabling all of them together obscures which change improved or damaged the result.
Use the renderer's documented channel convention and the receiving composite requirements to decide on division. A transparent edge that appears wrong is a reason to investigate the convention, not proof that every EXR should use the same import recipe.
Accept the channel handoff
The working import passes when the expected alpha is available in the intended representation and the object's boundaries behave correctly in the proposed composite. Retain the source render and note the import settings alongside the project. If the client requires a separate alpha pass, make that requirement explicit before merging or dropping it from a later delivery. A visually convincing preview alone cannot establish that the channel package is complete.
Related tasks
- Why Does a Clean Cutout Develop a Dark Halo Only After Import into Video Editing?
- Why Does a Transparent Blender Surface Appear in the Render but Not the Depth Pass?
- How Do I Keep Extra ImageMagick Meta Channels Instead of Flattening Them Into RGB?
Sources and scope
- 32-bit OpenEXR support: Associate EXR alpha merges alpha into associated RGB; default imports separate .A layers. Post divide and perturb zero are separate options.
Directly read official Photo 2 help. Original documentation-based synthesis and proposed checks, not firsthand application testing. Existing and reserved titles screened; near-neighbor decisions are identified explicitly.
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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.