
Yes. With a valid OpenColorIO configuration, Affinity Photo 2 uses a recognized color-space affix in an OpenEXR filename to interpret the source and convert it to scene_linear on import. Preserve an affix such as _acescg when it describes the actual render data. Do not add one merely to make a file look different.
Key Takeaways
- An EXR filename can contain meaningful color-pipeline information.
- The recognized name must agree with the real source space and active OCIO configuration.
- Document interpretation before applying compensating color corrections.
Check the render's stated source space
The official EXR page describes valid color-space affixes. The OCIO guide also describes source conversion and the message shown with a valid configuration. These are workflow-specific interpretation rules, not permission to infer source space from the image's appearance.
For a proposed architectural render, obtain the renderer's output specification before renaming its deliverables. A suffix added during packaging can alter what a receiving tool understands. Conversely, replacing descriptive filenames with short marketing names can remove information that the import workflow expected.
Compare the import record before editing pixels
- Retain the original render files and original names.
- Identify the intended source color space from the render pipeline.
- Confirm which OCIO configuration Photo 2 is using.
- Import a copy and read any conversion notification.
- Record the interpretation before adding a color adjustment.
If the notification names an unexpected source space, stop and investigate the filename, configuration and source specification together. Do not repeatedly warm or desaturate the imported image to compensate for an interpretation you have not established.
Preserve provenance through renaming
If a delivery system requires a different filename, keep an accompanying manifest that records the original name, actual source space and intended import handling. A manifest is proposed organizational guidance; it does not automatically change how Photo 2 reads a renamed file.
Avoid manufacturing a suffix as a substitute for a real color conversion. Renaming identifies how numbers should be read; it does not recreate a render exported in a different space. Likewise, the available recognized spaces depend on the OCIO configuration, so a name valid in one job should not be assumed valid in every installation.
Accept the interpreted source
Accept the import when the actual renderer output, documented filename information and reported conversion agree. Then review the agreed display transform and downstream export. Keep those stages separate: a correct source conversion does not by itself establish an approved appearance on every display. If disagreement remains, retain the unmodified render for a pipeline correction instead of baking a speculative fix into the only working copy.
Related tasks
- GIMP: Assign or Convert an Untagged Adobe RGB Image?
- Is Your 3D LUT a Creative Look or a Camera Log Conversion in darktable?
- Why Do My Photo Colors Change Between the Editor and Browser?
Sources and scope
- 32-bit OpenEXR support: With valid OCIO config, EXR valid color-space affix such as _acescg converts to scene_linear on import.
- Using OpenColorIO: On EXR loading source-to-scene_linear conversion and notification usually determined from filename affix.
Direct official documentation supports technical claims; original proposed examples and checks, no firsthand product test or measured performance claim.
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.