California’s synthetic-performer disclosure law creates a production control, not a talent verdict
SB 1050 moves synthetic-performer disclosure into the advertising workflow. The useful response is an asset-level control before release—not an assumption that a label settles consent, quality or the role of human talent.

What happened
California enacted SB 1050, requiring clear and conspicuous disclosure when an advertisement prominently includes a synthetic performer.
Why it matters
Creative, legal and procurement teams need to know which assets trigger disclosure, who supplies the label, and what separate evidence is required for rights and worker decisions.
California has enacted Senate Bill 1050. The governor’s announcement frames it as a worker-protection and transparency measure. The enrolled text requires a clear and conspicuous disclosure when an advertisement prominently includes a synthetic performer.
The word “prominently” matters. The text focuses on a performer in the foreground demonstrating or illustrating a product or service, narrating the advertisement or conveying its commercial message. That is narrower than a rule for every synthetic pixel. It still creates a new production question: before release, can the organisation identify covered performer use and prove that the required disclosure travelled with the final asset?
This is an analysis of the operating implications, not legal advice. Application depends on the final statutory provisions and facts of a campaign. Teams should have counsel confirm scope, effective dates and exceptions.
Put classification before finishing
The weakest implementation would ask a legal reviewer to inspect a finished campaign at the end. By then the source files, vendor decisions and distribution variants may be hard to reconstruct. Classification belongs at intake and again before export. The brief should state whether a person’s voice, likeness or performance is real, modified or synthetic; who authorised it; and whether the performer carries the commercial message.
Each asset needs a durable identifier that follows it through editing, localisation, resizing and platform delivery. The production record should link the source or model, human direction, rights documentation, synthetic-performer classification, disclosure treatment and final render. If a vendor supplies the asset, the contract should require equivalent provenance and a duty to notify the buyer when the classification changes.
The disclosure itself also needs a quality check. “Clear and conspicuous” is not satisfied by storing a label in a project note. Teams should test placement, duration, contrast, language and survival across crops. The exact standard should come from the law and counsel, not an invented internal rule.
Keep separate questions separate
A disclosure says something about how an advertisement was made. It does not prove that a person consented to use of a likeness, that underlying material was licensed, that the synthetic portrayal is accurate, or that replacing a performer was an appropriate workforce decision. Those questions need separate owners and evidence.
Kelley Drye’s independent overview places SB 1050 within a wider California privacy and AI package, while Reason Foundation’s pre-enactment testimony highlights the narrower design and policy trade-offs. Neither source provides evidence that viewers understand the label or that disclosure changes employment outcomes.
That limitation changes the metric. Do not count labels and declare success. Measure classification coverage, assets blocked before release, missing rights records, vendor corrections, disclosure survival across formats and post-release exceptions. Sample final ads from the audience’s view rather than relying only on the production file.
Operations also need a correction path. If a distributor drops, crops or obscures the disclosure, the team must know which variants are live, who can pause them and how quickly a corrected asset can replace them. Preserve proof from the delivered placement rather than assuming the master file controls every channel. Contracts should assign responsibility for platform transformations and downstream reuse.
The Skills Atlas can map the creative, legal, procurement and AI-production capabilities involved. The immediate decision is to add one release gate: no covered asset moves to distribution until classification, rights evidence, disclosure treatment and accountable approval are attached to the exact final version.
A defensible release packet
For every synthetic-performer asset, preserve the brief, provenance, rights basis, classification decision, legal interpretation, disclosure specification, final files, distribution variants and named approver. Record uncertainties and the decision to proceed or hold. That packet cannot guarantee compliance or fairness, but it makes the organisation’s reasoning visible and allows a correction without reconstructing the campaign from memory.