Protect Actors’ Likeness and Creative Rights in AI VFX

Using AI in visual effects can alter, recreate, or extend a performer’s image, voice, and movement, so teams need clear permission and controls before production begins. This guide helps producers, VFX supervisors, and performers set boundaries, document approvals, and manage generated or altered material from capture through release. Start with the relevant contracts, a description of the planned AI use, and a way to track approvals; legal requirements vary by location and should be checked with qualified counsel.

What You’ll Need

• Signed performer agreements and any applicable collective bargaining or production rules.
• A plain-language description of each intended AI use, including whether it involves a digital replica, voice, face, body, or performance alteration.
• A named production contact authorized to approve and record changes.
• Secure storage for source footage, scans, voice recordings, model files, approvals, and usage records.
• Access to production counsel or a union representative when rights or obligations are unclear.

Step-by-Step

1. Identify the material and the proposed use. Make an inventory before scanning, recording, or generating anything. Distinguish ordinary VFX work—such as removing a wire—from creating or substantially changing a performance. Flag face replacement, synthetic dialogue, voice cloning, body doubles, age changes, digital doubles, and reuse of scans or recordings in later projects. State whether the result is for a particular scene, a trailer, promotional material, localization, or future reuse.
2. Check existing agreements and applicable rules. Review the performer’s contract, releases, production policies, and any relevant union or guild agreement. Check what those documents actually authorize; permission to film a performance does not necessarily settle every question about generating a new one or reusing a digital replica. Requirements differ across jurisdictions and agreements. Ask counsel or the relevant representative to resolve gaps before capture or generation, rather than relying on a general release or a vendor’s terms.
3. Request specific, informed permission. Explain what data will be captured, what the AI-assisted work will change or create, why it is needed, where it may appear, and how long it may be retained. Describe meaningful restrictions, such as prohibited contexts, unrelated projects, advertising, or changes to dialogue and emotional delivery. Avoid vague language like “any use in any media” as a substitute for explaining a sensitive use. Give the performer time to ask questions and record their agreement in the required form.
4. Agree on compensation, credit, and review points. Clarify whether the use triggers additional compensation, credit, consultation, or approval under the contract or applicable agreement. Set practical review milestones: for example, a preview of a digital double, a synthetic line, or a materially altered scene before final delivery. Define who receives the preview, how feedback is submitted, and what happens if the parties disagree. Do not promise a veto or payment unless the agreement provides for it.
5. Limit capture and access. Capture only the scans, images, voice, and performance data needed for the approved work. Tell the performer when and where capture happens and who will operate the equipment. Restrict access to named crew and vendors with a production need; use individual accounts and secure transfer rather than open links or personal devices. Keep identifiable source files separate from broadly accessible project assets where practical.
6. Set vendor and model conditions in writing. Before sending material to a VFX house, model provider, or other supplier, specify permitted purposes, approved subcontractors, security expectations, retention and deletion schedules, and whether data may be used to train or improve a system. Prohibit unrelated reuse unless separately authorized. Require the supplier to report incidents and confirm deletion or return when the work ends. Check that the contract and technical workflow match; a promise in a contract is not a substitute for access controls.
7. Keep a usage and approval record. Maintain a simple register for each performer and asset: what was captured, the approved purpose, versions created, vendor access, review decisions, delivery locations, and retention or deletion status. Link approvals to the relevant scene or asset version. Record changes in scope and obtain fresh authorization when required before proceeding. This record helps production teams avoid accidentally using a permitted asset in a different context.
8. Review the finished work before release. Compare the final shot, voice, or digital performance with the agreed scope and any promised review process. Check that the result does not introduce unapproved dialogue, actions, endorsements, or contexts. Confirm that marketing, trailers, dubbed versions, and later edits are covered rather than assuming approval for one scene covers every use. If a cut or reuse changes the agreed purpose, pause and resolve it first.
9. Close out and handle later requests. At wrap or delivery, account for copies held by production and suppliers, then follow the agreed retention and deletion terms, including any legitimate archival obligations. Keep only access-controlled records needed to demonstrate compliance. Create a contact route for correction, questions, or a request to investigate suspected misuse. Escalate promptly to production leadership and counsel instead of quietly circulating disputed material.

Common Mistakes

• Assuming a general image release automatically covers synthetic performances, voice cloning, or future reuse.
• Seeking permission only after a digital replica or generated shot has already been made.
• Using broad consent language without explaining the intended scene, context, audience, and duration.
• Sending scans or recordings to a supplier without checking training, subcontracting, storage, and deletion terms.
• Confusing a creative review opportunity with a contractual approval right; state clearly what each person can decide.
• Failing to track trailers, localization, revised cuts, and promotional uses as separate possible destinations.

Tips

• Use a one-page AI-use brief alongside formal agreements. List the performer, asset, purpose, boundaries, supplier, and approval contact in plain language.
• Make consent an ongoing production checkpoint, not a one-time signature: revisit it when the intended use materially changes.
• Keep identifiable scans and voice data out of general-purpose folders and limit download permissions.
• Use version labels and retain a copy of the approved preview so teams can compare it with the delivered result.
• Build time for performer questions and review into the schedule; rushed approvals create confusion and rework.
• Have counsel check local privacy, publicity, employment, copyright, and collective-agreement issues. These may overlap, and no single checklist replaces jurisdiction-specific advice.

Troubleshooting

The agreement is unclear: Pause the affected use. Write down the exact proposed change and ask production counsel or the relevant performer representative to interpret the agreement and document any new permission needed.

A vendor cannot confirm whether it trains on submitted material: Do not upload identifiable assets until the vendor provides a clear written answer and acceptable terms. Consider a controlled environment or a supplier with suitable restrictions, subject to production approval.

The final result goes beyond the approved use: Hold the shot from delivery and promotion. Compare it with the documented scope, notify the designated production lead, and obtain the necessary review or revised authorization before release.

A performer raises a concern after delivery: Acknowledge it, preserve relevant records, restrict further distribution where feasible, and escalate to production leadership and counsel. Check contractual and applicable legal obligations; do not promise a specific remedy before reviewing them.

Files may have been shared or retained improperly: Limit access, preserve incident details, contact the vendor and production security or privacy lead, and follow the incident-response process. Determine which copies and recipients are affected and document the steps taken.

Frequently Asked Questions

Does permission to film an actor cover an AI-generated digital double?
Not necessarily. The answer depends on the agreement, the specific use, applicable rules, and jurisdiction. Check the documents and obtain specific permission where needed.

Can a production use an actor’s voice to generate new dialogue?
Only if the relevant rights and approvals allow that use. Explain the lines, context, distribution, and any applicable compensation or review terms before creating them.

Should actors approve every AI-assisted VFX shot?
Not automatically. The contract or applicable agreement may set review or approval rights. Define review points clearly, especially for material changes to a face, voice, body, or performance.

Can a VFX vendor use production scans to train its tools?
Do not assume it can. Specify whether training or system improvement is permitted, and obtain any required authorization before sharing the material.

What if the production needs to use an approved asset in a new project?
Check whether the original permission covers that project and context. If it does not, pause and secure the required permission and terms before reuse.

What should be retained after production?
Follow the agreement, applicable rules, and legitimate archival requirements. Restrict access, document what is retained, and arrange deletion or return of other copies as agreed.

Related

• US vs Taiwan Semiconductor Manufacturing: Costs & Supply Chain
• Foldable Phone Cases: Hinge Coverage vs Open Hinge
• Programmable Knob: The Keyboard Feature You’ll Use Most