X.AI Challenges Minnesota’s AI “Nudification” Ban on First Amendment Grounds
State legislatures have spent the past two years racing to regulate specific applications of artificial intelligence, and few targets have drawn as much bipartisan urgency as “nudification” tools — AI image editors that let a user upload an ordinary photograph and generate a version depicting the subject nude or partially undressed. Minnesota became the first state in the country to ban that capability outright, rather than simply punishing the people who misuse it, and the company behind one of the most widely used AI image tools on the market has now asked a federal court to strike the law down before it can be enforced. The resulting case is an early and closely watched test of a question that will recur across dozens of statehouses: how far can a state go in regulating what an AI system is permitted to generate before it runs into the First Amendment?
On July 27, 2026, X.AI LLC — the Elon Musk-owned company that develops the Grok chatbot and its Grok Imagine image-generation tool — sued Minnesota Attorney General Keith Ellison in the U.S. District Court for the District of Minnesota, seeking to enjoin the state’s new nudification law before its August 1 effective date.1 X.AI does not dispute that Minnesota has a legitimate, even compelling, interest in stopping the nonconsensual creation of AI-generated nude images of real people. Its argument is narrower, and more consequential for the broader AI industry: that the statute Minnesota actually enacted reaches so much further than that interest that it functions as a content-based restriction on a wide range of ordinary, protected image editing.
Minnesota’s Nudification Law
Minnesota Gov. Tim Walz signed House File 1606 on May 7, 2026, after it passed the House 132 to 1 and the Senate 65 to 0 — a lopsided vote reflecting how little political disagreement exists over the underlying harm the law targets.2 The statute, now codified at Minn. Stat. § 325E.91,3 prohibits any person who owns or controls a website, application, software program, or other service from allowing a user to access, download, or use that service to “nudify” an image or video of a real person, or from nudifying an image on a user’s behalf. A separate provision bars advertising or promoting a nudification service. Unlike most existing state deepfake statutes, which impose liability on the individual who creates or distributes a nonconsensual image, HF 1606 places the entire enforcement weight on the platform or tool that made the image possible in the first place; the person who actually generates and shares the image is not directly reached by the statute at all.
The statute defines “nudify” as altering or generating an image so that it depicts “an intimate part not depicted in an original unaltered image or video of an identifiable individual,” where the result is realistic enough that a reasonable viewer would believe the depicted body part belongs to that person. For “intimate part,” the law borrows a definition from Minnesota’s criminal sexual conduct statute — the primary genital area, groin, inner thigh, buttocks, or breast of a human being — a list drafted to define unwanted physical touching, not photographic content.4 The law contains no consent defense and no scienter or knowledge requirement: liability attaches whenever a covered service is used to produce a qualifying image, regardless of whether the subject consented, whether the platform prohibited the conduct in its terms of service, or whether the platform took reasonable steps to prevent it. Legislative history indicates the omission of a consent defense was deliberate, and that lawmakers considered and rejected a narrower definition of “intimate part,” drawn from Minnesota’s existing deepfake statute, before settling on the broader language now in the law.5 Penalties run as high as $500,000 per violation, recoverable by the attorney general or by the depicted individual in a private civil action that also permits compensatory and treble damages.6
X.AI’s Constitutional Challenge
X.AI’s complaint frames HF 1606 as a content-based restriction on speech subject to strict scrutiny under the Supreme Court’s decision in Reed v. Town of Gilbert, which held that a law is content-based, and therefore subject to strict scrutiny, whenever applying it requires examining what a piece of expression says or depicts, and that content-based laws are presumptively unconstitutional unless the government proves they are narrowly tailored to serve a compelling interest through the least restrictive means available.7 Because enforcing HF 1606 requires determining what an image depicts, X.AI argues the law is content-based on its face, and that Minnesota cannot satisfy strict scrutiny because far less restrictive alternatives exist, including the distribution-based nonconsensual-imagery statutes that most other states have already enacted.
The complaint argues the statute’s borrowed “intimate part” definition sweeps in a large volume of protected expression that has nothing to do with image-based sexual abuse, photographs of men without shirts, people in shorts or swimwear, and other body parts that are ordinarily and lawfully depicted in public.8 Because the statute does not distinguish a nonconsensual sexual deepfake from a satirical image, a restored family photograph, or an otherwise innocuous edit made with Grok Imagine, X.AI contends the law is substantially overbroad relative to the legitimate sweep of conduct it could otherwise reach.
X.AI’s second major argument targets the statute’s strict-liability structure. The complaint asserts that because the law imposes liability regardless of a platform’s content-moderation efforts, and because no image-generation system can filter every possible attempt to circumvent its safeguards with perfect accuracy, HF 1606 effectively forces providers to either withdraw general-purpose image-editing functionality altogether or accept unlimited financial exposure. X.AI has already restricted Grok Imagine’s editing features for users located in Minnesota, which it describes in the litigation as the only practical response available to it under the statute as written.9 The absence of any safe harbor for platforms that prohibit and actively police nudification, X.AI argues, is itself evidence that the law is not narrowly tailored, since a law that treats a compliant platform the same as a bad actor cannot be the least restrictive means of achieving the state’s interest. That argument echoes the Supreme Court’s reasoning in Counterman v. Colorado, which held that even categories of speech that receive no First Amendment protection at all, such as true threats, generally require some showing of the speaker’s mental state before liability can attach.10
Where the Case Stands
X.AI moved for a temporary restraining order on July 29, 2026, two days after filing suit and just three days before the law’s effective date. U.S. District Judge Donovan Frank denied that motion on July 31, but on narrow procedural grounds that did not reach the constitutional merits. Judge Frank found that X.AI’s own delay undercut its claim of irreparable harm, writing that the company “filed the motion on July 29, 2026, nearly three months after the law was signed, and only three days before the law is set to take effect,” and that “such a delay in bringing the action and the motion suggests that harm is not immediate”.11 HF 1606 accordingly took effect as scheduled on August 1, 2026. Rather than dismissing X.AI’s request outright, Judge Frank converted the motion into one for a preliminary injunction and scheduled a hearing for August 19, 2026 — the first occasion on which any court will evaluate whether the statute survives First Amendment scrutiny.12 Attorney General Ellison has defended the law publicly, stating that nudification tools “have been used to generate child sexual abuse materials and harass people in the vilest ways imaginable”.13
A Broader Pattern in State AI Regulation
Minnesota’s approach did not emerge in a vacuum. Nearly every state has now enacted some form of law addressing nonconsensual intimate imagery or AI-generated sexual content involving minors, and by one recent count roughly 48 states have some statute on the books addressing nonconsensual deepfakes, AI-generated child sexual abuse material, or both.14 Most of those laws, however, target the creation or distribution of specific images after the fact, leaving platforms exposed only when they knowingly host or fail to remove offending content. Texas, for example, amended its penal code in 2025 to extend criminal and civil liability to the owners of websites, applications, and payment processors that facilitate nonconsensual deepfake imagery, while still keying liability to the underlying conduct.15 California’s AB 621, enacted the same year, expanded an existing civil cause of action (originally enacted in 2019) to reach “deepfake pornography services” and those who knowingly facilitate them, raising statutory damages to up to $250,000 for malicious violations.16 At the federal level, the TAKE IT DOWN Act requires covered online platforms to establish notice-and-removal procedures for nonconsensual intimate images, including AI-generated ones, but likewise does not ban the underlying editing technology.17 Minnesota’s law is the only one of these to impose strict, no-fault liability directly on the tool itself, independent of distribution, consent, or the platform’s own conduct — precisely the feature X.AI has put at the center of its constitutional challenge.
What This Means for Businesses and Other States
The outcome of the August 19 hearing will matter well beyond Minnesota. First, AI companies that offer general-purpose image or video editing tools should assume that any state considering nudification legislation may look to Minnesota’s tool-based model rather than the distribution-based approach that has prevailed until now, and should evaluate now whether their existing content-moderation architecture could survive a strict-liability standard with no safe harbor. Second, companies operating in Minnesota should treat the current statute as fully enforceable while the litigation proceeds; a TRO denial on timing grounds is not a ruling on the law’s validity, and businesses cannot rely on the pending challenge to excuse noncompliance in the interim. Third, in-house counsel advising clients on AI product design should document content-moderation efforts, filtering architecture, and enforcement statistics now, since those facts will be directly relevant if a company later needs to argue that a strict-liability regime is not the least restrictive means available to address a state’s interest. Fourth, businesses and trade associations that want a voice in how these statutes are drafted should engage during the legislative process rather than after enactment, since Minnesota’s own legislative history shows that lawmakers considered and rejected narrower statutory language before adopting the broader version now being challenged in court. Fifth, companies should watch not only the August 19 ruling but also how courts and legislatures in other states treat similar proposals, since a ruling either upholding or enjoining HF 1606 is likely to shape how California, New York, and other states drafting their own nudification bills approach the same content-based line-drawing problem.
Conclusion
The Minnesota case is unlikely to be the last word on how far states can go in regulating specific AI capabilities, but it will be an important early data point. X.AI has conceded that the state’s underlying interest is legitimate and even compelling; the entire dispute is about tailoring — whether a strict-liability statute with no safe harbor and no consent defense is the least restrictive way to prevent AI-generated image-based abuse, or whether it reaches so much ordinary, protected image editing that it cannot survive strict scrutiny. Whatever Judge Frank decides on August 19, businesses that build or deploy generative AI image tools, and the states drafting the next generation of AI-specific legislation, will be studying the result closely.