June 10, 2026. Washington's AI likeness and deepfake law takes effect that date. Here is what you need to check before then.
TL;DR: Washington's AI likeness law takes effect June 10, 2026. Signed by Governor Ferguson. The law prohibits creating or distributing AI-generated replicas of a real person's voice, likeness, or identity without consent in commercial, sexual, or deceptive contexts. It also prohibits AI-generated sexual content (deepfakes) of real people without consent. Penalties include civil liability, the affected person can sue for actual or statutory damages. Compliance requires auditing any AI tools that generate or manipulate images, audio, or video of real people.
What the Law Prohibits
Washington's law creates three categories of prohibited conduct:
| Prohibition | What it covers |
|---|---|
| Commercial likeness use without consent | AI-generated voice, image, or likeness used to promote or sell products/services without the person's consent |
| Non-consensual intimate imagery (NCII) | AI-generated sexual or intimate content depicting a real person without consent |
| Deceptive AI media | AI-generated content designed to falsely represent a real person's words, actions, or statements |
The law is enforceable by the person depicted (private right of action) and by the Washington AG.
Who Is Liable
Liability attaches to both creators and distributors:
- Creator, the person or entity that generates the AI content
- Distributor, the platform, service, or individual that shares, hosts, or transmits the AI content
If your platform allows users to generate or share AI-generated content depicting real people, you have potential exposure unless you have adequate consent mechanisms and moderation.
Which Tools Trigger Compliance Risk
Audit your tech stack for anything that falls into these categories:
| Tool type | Examples | Compliance risk |
|---|---|---|
| Voice cloning / AI voice | ElevenLabs, Resemble.ai, Speechify Voice | HIGH, requires consent workflow |
| AI face swap / deepfake video | Various apps, commercial SDKs | HIGH, prohibited for non-consenting real people |
| AI image generation with real person references | Midjourney, DALL-E with name prompts | MEDIUM, depends on output realism and commercial use |
| AI lip-sync / video translation | HeyGen, Synthesia (custom avatars) | HIGH if using real person likenesses without consent |
| AI avatar creation (custom) | Synthesia, D-ID (user-uploaded face) | MEDIUM, requires user consent for their own likeness |
| Text-to-speech with named celebrity voice | Any TTS with licensed/cloned voices | HIGH, requires consent from the voice owner |
| General text generation (no likeness output) | ChatGPT text output | LOW, no likeness reproduction |
What Consent Looks Like
Valid consent under Washington's law is:
- Written, oral consent is insufficient for commercial uses
- Specific, consent to use a person's likeness in one context does not transfer to other contexts
- Revocable, the person can withdraw consent, and continued use after withdrawal violates the law
- Informed, the person must understand what their likeness will be used for
For your own employees or contractors who appear in AI-generated content (product demos, training videos, avatars), you need signed consent that specifically covers AI-generated uses.
Platform Obligations
If you operate a platform where users can create AI content:
- Terms of Service, prohibit users from creating AI content of real people without consent
- Reporting mechanism, provide a way for individuals to report unauthorized AI depictions of themselves
- Takedown process, have a documented process for removing reported violations within a reasonable timeframe
- Content moderation, implement screening for AI-generated NCII (several third-party detection tools exist)
Compliance Checklist Before June 10, 2026
- 1. Audit AI tools, list every AI tool in your stack that can generate, clone, or manipulate human voice, face, body, or likeness
- 2. Identify real-person use cases, for each tool, identify where you use or allow use of real people's likenesses (not fictional characters)
- 3. Confirm consent documentation, for every real person whose likeness is used in AI-generated content, verify you have written consent covering that specific use
- 4. Terminate non-consented uses, if you are using a real person's voice or likeness without documented consent, stop before June 10
- 5. Update ToS and user policies, if your platform allows user-generated AI content, add explicit prohibition on non-consented likeness use
- 6. Implement takedown process, create a process for handling reports of unauthorized AI depictions before the law takes effect
- 7. Train content and product teams, anyone who creates marketing, demo, or training content using AI tools needs to understand the consent requirement
- 8. Review vendor agreements, if you use a vendor to create AI-generated content for you, confirm their consent practices and ensure their indemnification covers you for Washington-law violations
Key Dates
| Date | Event |
|---|---|
| 2026 (earlier) | Law signed by Governor Bob Ferguson |
| June 10, 2026 | Law takes effect, all covered conduct must comply |
| June 10, 2026+ | Washington AG enforcement begins; private lawsuits can be filed |
Penalties
The person depicted can sue for:
- Actual damages
- Statutory damages per violation
- Attorney's fees and costs
- Injunctive relief (court order requiring the content to be removed)
There is no cure period in the private right of action, once the law takes effect, violations are immediately actionable.
How Washington's Law Interacts With the Federal TAKE IT DOWN Act
The federal TAKE IT DOWN Act (signed May 2025) overlaps with Washington's state law on non-consensual intimate imagery. Understanding which law applies, and how they interact, matters for platforms operating nationally.
What the TAKE IT DOWN Act covers: The federal law criminalizes publishing non-consensual intimate images (NCII) of real people, including AI-generated images, and requires platforms to remove reported content within 48 hours of a takedown request. It applies nationwide and is enforced by the FTC.
How Washington's law adds to it:
- Washington's law covers commercial likeness use and deceptive AI media beyond NCII, the federal law is limited to sexual content
- Washington adds a private right of action (the affected person can sue directly), the federal law relies on FTC enforcement
- Washington's 8-item compliance checklist (above) addresses obligations the federal law does not impose, including consent documentation for commercial uses
For national platforms: Comply with both. The 48-hour takedown requirement from the federal act is the more operationally demanding obligation. Washington's consent documentation requirement is the more compliance-intensive one for teams creating original AI content.
Sector-Specific Guidance
The risk profile varies significantly by business type. Here is how Washington's law applies across the most commonly affected sectors.
Marketing and Advertising Teams
Marketing teams using AI to generate product images, brand spokesperson content, or social media visuals face the highest immediate compliance burden.
- AI-generated brand spokesperson content, if your AI-generated spokesperson resembles a real person (even unintentionally), and the content is commercial, Washington's consent requirement may apply. Use clearly fictional characters with distinctive non-human features, or obtain written consent.
- Testimonial and review content, AI-generated testimonials depicting named or identifiable real people are prohibited without consent. This includes generating a realistic-looking "customer" who doesn't exist but could be mistaken for a real person.
- Influencer voice cloning, brands that use AI voice tools to create ad-read variations must have written consent from the influencer whose voice is being cloned. A general talent agreement that predates AI voice cloning does not cover this use.
Podcast and Media Production
Audio and video production teams using AI voice tools need to address consent before June 10.
- Any AI voice clone of a real person used in commercial content requires written, specific consent
- Podcast hosts who have consented to their own AI voice clone for promotional clips must re-confirm that consent explicitly covers the AI-generated use case
- Archival content: if you created AI-voiced versions of past episodes using a real person's voice, review whether original consent covered AI generation
Tech Companies and Product Teams
Teams building products that include AI content generation features must address both their own use and user-generated use.
- Internal use: AI-generated product demo videos, onboarding content, and training materials using real employee likenesses require signed employee consent specific to AI-generated use
- User-generated content platforms: If your product allows users to create AI content with real-person references, your ToS must prohibit non-consented likeness use, and you need a functional takedown process before launch in Washington
- AI avatar products: If your product allows users to create digital avatars of themselves, ensure your consent flow explicitly covers AI-generated uses of the likeness they upload, general terms of service are insufficient
Recruiters and HR Teams
A narrower but real risk: AI tools that generate candidate profile images, interview prep simulations using realistic human faces, or training videos featuring realistic AI-generated people.
- Training videos using realistic human faces without consent from the depicted individuals trigger Washington's commercial likeness provisions
- AI candidate simulations using real interviewer faces or likeness require the interviewer's written consent
Building a Consent Documentation System
Once you have identified your Washington compliance gaps, the operational challenge is managing consent at scale. A minimal consent system for small teams:
Step 1, Consent form template. Create a simple document specifying: the person's name and identity, the specific AI-generated use cases covered (commercial advertising, product demos, voice cloning for X purpose), the media types covered (audio, video, image), the duration of consent, and revocation procedure.
Step 2, Revocation tracking. When a person revokes consent, you need to stop use within a reasonable time and pull existing content. Build a simple tracker (a spreadsheet works) linking each consented person to the content assets they appear in. When revocation arrives, you can identify affected assets immediately.
Step 3, Vendor chain. If an external agency or contractor creates AI-generated content featuring real people on your behalf, their consent documentation must cover your use specifically. Add a contract clause requiring that the vendor can provide consent documentation for any AI-generated likeness they use in work product delivered to you.
The consent and takedown requirements apply from the effective date regardless of when the underlying content was created. If you have synthetic likeness content in production and no consent records on file, getting documentation in place before June 6 is the priority.
Sources: Washington State Legislature, Governor Ferguson's office, enacted bill text. This article reflects the law as signed; consult counsel for advice specific to your situation.
