
A custom camera LUT is a separate dependency. Apple says that copying a library that uses an imported custom camera LUT also requires copying the LUT file separately. Locate the intended LUT, transfer it with the handoff, then verify the received image against an approved reference.
Key Takeaways
- A library copy does not by itself transfer an imported custom camera LUT.
- Restore the correct LUT instead of substituting a similar-looking file.
- Verify the grade after the warning is resolved.
Identify the missing dependency
Confirm that the warning concerns a custom camera LUT rather than offline footage or a missing third-party effect. These are different dependencies.
Record the LUT's name and intended role from the working system. Ask the originating editor or colorist if several revisions exist. A similarly named file can apply a different transformation even when it makes the warning disappear.
Locate and transfer the intended LUT
Apple documents a Reveal in Finder command in the Camera LUT menu for locating imported LUT files. It recommends compressing the selected LUT files for transfer and importing them on the receiving Mac.
Its guide also describes a yellow warning beside the Camera LUT control when the file is missing, with a way to reimport or replace it. Prefer restoring the identified file when the objective is to reproduce an approved look.
Keep the transfer limited to the project dependencies you are authorized to share. A LUT received under a separate license may have sharing conditions beyond the mechanics of copying it.
Compare the received picture
After import, inspect the relevant clip's Camera LUT selection and compare representative frames with a reference from the originating system. Check skin, bright areas and a neutral object where available.
In a hypothetical interview handoff, the warning can be resolved with a different LUT while the face becomes too warm. That is a failed visual match despite a successful dependency import. Investigate the file identity and the surrounding color workflow before changing every shot's creative correction.
Do not treat the filename alone as proof that the entire grade is identical. Other project settings and effects can still matter.
Make the next handoff explicit
Add the LUT filename and its purpose to the dependency list. State which reference movie or still represents the approved result. Keep the source file available for later reconstruction.
Use the approved-version record to distinguish the library, source media and separate dependencies. Then compare a rendered sample with the preview before accepting the receiving system's full export.
Source: Apple's LUT guide, Share a custom camera LUT.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Captions look correct in preview but move in the export: isolate a small render test
Sources and scope
- Apple: Apply LUTs, share a custom camera LUT: Imported custom camera LUT must transfer separately from a copied library; Reveal in Finder, ZIP transfer/import workflow and missing-LUT warning.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.