DTWdailytechwire
Tech Intelligence, Wired Daily
Policy

Minnesota's Deepfake Law Survives First Legal Test

A federal judge has allowed the nation's first ban on non-consensual AI image generators to proceed, dismissing xAI's emergency request but leaving the constitutional challenge alive.

PN
Priya Nair
Startups Reporter · Bengaluru
Aug 2, 2026
5 min read
Minnesota's Deepfake Law Survives First Legal Test
Minnesota's Deepfake Law Survives First Legal TestCredit: Primakov / Shutterstock

The First Attempt to Block Enforcement Fails

US District Judge Donovan Frank has declined to halt Minnesota's first-in-the-nation law targeting applications that generate non-consensual intimate imagery, allowing the statute to take effect as scheduled on August 1. The ruling rejected xAI's emergency motion for a temporary restraining order, though the company's underlying lawsuit challenging the law on First Amendment grounds remains active.

The judge's order focused less on the merits of xAI's constitutional arguments and more on the timing of its legal strategy. xAI filed its complaint on July 29, barely three days before the law's effective date and nearly three months after Minnesota Governor Tim Walz signed the legislation. Judge Frank found that delay significant: "Such a delay in bringing the action and the motion suggests that harm is not immediate," he wrote in his order.

The decision reflects a procedural skepticism that courts often apply when litigants seek emergency relief at the last moment. For xAI to secure a temporary restraining order, it needed to demonstrate imminent and irreparable harm. The company's timing worked against that argument.

What the Minnesota Statute Actually Does

Minnesota's law establishes two primary mechanisms. First, it prohibits the operation of apps and websites designed to generate "nudified" content within state borders. Second, it creates substantial financial liability for developers: a $500,000 penalty for each instance in which a user generates a non-consensual intimate image using their product.

The statute defines a "nudified" image or video as content that has been "altered or generated to depict an intimate part not depicted in an original unaltered image or video of an identifiable individual." Crucially, the law applies only when the altered content is "so realistic that a reasonable person would believe that the intimate part belongs to the identifiable individual."

That realism threshold is central to Minnesota's legislative intent. The law targets tools that create convincing synthetic imagery of real people, not cartoons or obviously fictional content. It's a response to a specific technological capability that has proliferated over the past two years as generative AI models have become more accessible and more powerful.

From a policy perspective, Minnesota is attempting to thread a narrow needle. The state wants to prevent a category of harm (non-consensual sexualized imagery of identifiable individuals) without sweeping in artistic expression, satire, or other protected speech. Whether the statute succeeds in that goal is the core question xAI's lawsuit will force the court to answer.

xAI's Constitutional Argument

In its complaint, xAI framed the Minnesota law as "an overbroad, content-based ban on free speech and the tools of visual expression in a clumsy attempt to prohibit 'nudification.'" The company argued that while it does not contest Minnesota's interest in preventing the spread of synthetic nude images of real people, the law "extends far beyond that goal, exposing a wide array of protected speech to civil liability and government sanction."

Content-based restrictions on speech face strict scrutiny under First Amendment doctrine. Courts ask whether the law is narrowly tailored to serve a compelling government interest and whether it uses the least restrictive means available. xAI's legal theory hinges on the claim that Minnesota's statute fails that test by sweeping too broadly.

The company did not specify in its public filings which categories of protected speech it believes the law would chill, but the argument likely centers on edge cases: artistic projects that manipulate imagery, satire that sexualizes public figures, or research tools that could technically generate prohibited content. The $500,000-per-instance penalty creates a strong incentive for developers to avoid any gray area, which xAI argues could suppress legitimate expression.

Minnesota will counter that the law's realism standard and focus on identifiable individuals limit its scope to unprotected or low-value speech. The state's position is that generating convincing fake nude images of real people without consent is more akin to defamation or harassment than to political commentary or art.

The Grok Backstory

xAI's decision to bring this lawsuit is inseparable from the recent history of Grok, its generative AI chatbot. In early 2026, Grok gained widespread attention for generating sexualized images of real women and children when users requested them. The platform's relatively permissive content policies at the time allowed it to fulfill requests that competing services from OpenAI, Anthropic, and Google routinely blocked.

By mid-January, xAI implemented policy changes intended to prevent such outputs. But evidence emerged as recently as April that Grok continued to generate non-consensual intimate imagery of real individuals, suggesting that technical or policy enforcement remained incomplete.

That context matters for understanding xAI's legal posture. The company is not challenging Minnesota's law as an abstract matter of principle. It is defending a business model that, until very recently, explicitly permitted the behavior Minnesota seeks to ban. Whether that recent history strengthens or weakens xAI's First Amendment claim is unclear, but it will likely shape public and judicial perception of the case.

What Happens Next

Judge Frank has scheduled a hearing for August 19 to consider xAI's request for a preliminary injunction, a longer-term court order that would suspend enforcement of the law while the lawsuit proceeds. That hearing will dig deeper into the constitutional questions that the emergency motion only touched on.

A preliminary injunction requires xAI to show a likelihood of success on the merits, irreparable harm in the absence of an injunction, a balance of hardships favoring the plaintiff, and that an injunction serves the public interest. The August 19 hearing will be the first substantive test of whether xAI can meet that burden.

If xAI prevails, Minnesota's law will be frozen pending the outcome of the full lawsuit, which could take years to resolve. If the state prevails, the law will remain in effect, and xAI will face a choice: comply by blocking Minnesota users, challenge the law's enforcement mechanisms, or continue operating and risk penalties.

Other states are watching closely. Minnesota's statute is the first of its kind, but legislators in California, New York, and Washington have introduced similar proposals. If Minnesota's law survives judicial review, it will provide a template for other jurisdictions. If it falls, state legislatures will need to rethink their approach.

At DailyTechWire, we've tracked the growing tension between generative AI capabilities and content moderation norms across multiple jurisdictions. Minnesota's law represents one of the most direct regulatory interventions to date. The question is whether courts will allow states to regulate AI tools based on their potential harms, or whether First Amendment protections will limit such efforts to narrower, post-hoc enforcement against individual bad actors. The answer will shape not just deepfake policy, but the broader regulatory landscape for generative AI in the United States.

Read next
Policy

ByteDance Stakes $39 Billion on Brazil's Data Sovereignty Gambit

Sofia M. Reyes · 5 min
Policy

Seven US Water Systems Breached Through Industrial Controllers in Week-Long Attack Wave

Marcus Halloran · 5 min
Policy

Kremlin Group Exploits Critical Exchange Flaw With Half-Click Malware

Marcus Halloran · 6 min
Spot something wrong? Email corrections@dailytechwire.com. We log every correction publicly.