The First Amendment Was Not Written for a Button That Undresses Anyone.

The injury begins before publication

The conventional legal response to an abusive image begins after something has gone wrong. A perpetrator creates it. Someone posts or transmits it. The subject demands removal, seeks an injunction, reports a crime, or sues for damages. Every remedy arrives downstream from the act that changed an ordinary photograph into a weapon.

Minnesota decided that downstream was too late. The legislative record, as summarized in the state's federal-court filing, includes testimony from women whose photographs were transformed into explicit material by someone they knew. One said the experience kept her from work and left her uncertain who had seen the images. Another described lost work, depleted savings, and debt. These are allegations and legislative testimony, not findings in the constitutional case. They explain why the state aimed at the tool itself.

That choice creates the case's central tension. The more frictionless the technology becomes, the stronger the argument for prevention. The closer the state moves toward prohibiting a general-purpose expressive tool, the stronger the First Amendment objection becomes.

Minnesota regulates the machine, not just the image

Minnesota's new Section 325E.91 took effect August 1. It defines nudification as altering or generating an image or video to depict an intimate part that was not shown in the original, when the result is realistic enough that a reasonable person would believe it belongs to an identifiable individual.

The prohibition is directed at whoever owns or controls the website, application, software, program, or service. A provider may not allow a user to access or use the service to create a covered image, create one for a user, or advertise a service that performs the function. The statute's only express exemption applies when using the service requires substantial individualized technological or artistic skill from the human creator.

A depicted person may bring a civil action for compensatory damages, including up to three times actual damages for mental anguish, punitive damages, injunctive relief, attorney fees, costs, and other equitable relief. The attorney general may seek a civil penalty of up to $500,000 for each unlawful access, download, or use. The law also says it does not alter the protections and liabilities provided by Section 230 of the federal Communications Decency Act.

This is not a notice-and-takedown law. Distribution is not an element. The statutory design tries to prevent creation by making the provider responsible for access to the capability.

xAI's strongest argument is the text Minnesota wrote

xAI does not claim that Minnesota lacks a legitimate interest in stopping nonconsensual synthetic sexual imagery. Its preliminary-injunction brief says the company prohibits users from generating nude or sexualized images of real people without consent. Its constitutional argument is that the statute reaches well beyond that undisputed target.

The word consent does not appear in the enacted provision. Neither do knowledge, intent, or distribution. On xAI's reading, a consenting adult who edits an image of herself is treated like a stranger who targets an unwilling victim. A provider can face liability even if its policies prohibit the conduct and its safeguards are designed to stop it. The statute contains no express exception for artistic, political, journalistic, educational, medical, scientific, satirical, or religious uses.

The definition of an intimate part also borrows from Minnesota's sexual-contact statute and includes the inner thigh, buttocks, groin, and breast. xAI argues that this language can reach ordinary depictions of swimmers, shirtless men, or people wearing shorts when an image is altered in a realistic way.

Those are not merely clever hypotheticals. Overbreadth doctrine exists because severe penalties can cause speakers and platforms to suppress lawful expression rather than risk becoming the test case. A potential $500,000 penalty for each violation gives the chilling-effect argument practical weight.

The state's strongest answer is scale

Minnesota's response is not that every conceivable application of the law is perfect. The state argues that xAI has brought a facial challenge and must show that the statute's unconstitutional applications substantially outweigh its legitimate ones. It characterizes the law as regulation of a technological tool used to produce harmful material, not a ban on a disfavored viewpoint.

The practical point underneath that doctrine deserves attention. An industrial tool can produce harm at a speed and volume that remedies aimed only at individual users cannot match. The provider designs the interface, chooses what the model will generate, sets the safeguards, observes attempts to evade them, and decides whether a capability remains available. The person depicted controls none of that.

It is easy to say that government should punish the bad actor. It is harder when a child can become the subject of a realistic explicit image between classes, the creator may be anonymous, and the file can be copied indefinitely before a court can issue an order. Minnesota is testing the proposition that prevention obligations should sit with the party that made the scale possible.

Speech doctrine meets product design

The case resists the categories lawyers usually prefer. An image generator is plainly a medium through which users create expression. Images do not lose First Amendment protection because software helped make them. But the same system is also a commercial product whose architecture can make a predictable category of abuse dramatically easier.

Calling the system speech does not end the analysis. Calling it a tool does not end it either. A printing press is a tool. So is a camera. Courts will need to examine what the law regulates, how closely that regulation depends on content, which protected uses it burdens, and whether narrower measures can address the same harm.

This distinction will recur far beyond intimate imagery. Legislatures increasingly want to regulate what AI systems can do before a specific unlawful output causes injury. Providers will respond that capability restrictions burden lawful uses and expression. The law has extensive doctrine for harmful speech, dangerous products, and intermediary liability. Generative systems occupy all three neighborhoods at once.

Federal law chose a different trigger

The federal TAKE IT DOWN Act offers a useful contrast. According to current Federal Trade Commission guidance, covered platforms must provide a process for requesting removal of nonconsensual intimate imagery, including AI-generated digital forgeries, and remove reported material and known identical copies within 48 hours of a valid request.

That framework turns on nonconsensual publication and platform notice. Minnesota moves earlier. It targets access to a low-skill capability even if a covered image is never distributed. The federal model addresses the spread. The Minnesota model addresses the means of production.

Neither trigger is complete. Takedown can be inadequate after a file has escaped into other services. A capability ban can suppress lawful creation and impose liability without knowledge or fault. The hard policy work lies between those failures, in duties calibrated to consent, age, provider knowledge, safeguard quality, user circumvention, realistic risk, and distribution.

A necessary goal can still produce an overbroad law

The state is right about the basic allocation of responsibility. An AI provider should not collect the benefit of making a dangerous capability effortless while assigning every cost of misuse to victims and anonymous users. Product design is conduct. Safeguards are not charity. A company that can see a systematic pattern of abuse cannot make the problem disappear by placing a prohibition in its terms of service.

xAI is also right to press the omissions. Consent, knowledge, distribution, and good-faith safeguards are not peripheral details. They distinguish abuse from lawful expression and culpable indifference from a defeated security measure. A statute imposing enormous penalties should say more clearly which side of those lines creates liability.

The defensible answer is not that Minnesota must wait until after publication. It is that prevention rules should be tied tightly to the harm they are designed to prevent. A law can impose strong duties on providers, require effective barriers, and create meaningful remedies without treating every realistic alteration of an enumerated body part as the same constitutional event.

Tomorrow's hearing will not finish the argument

U.S. District Judge Donovan Frank previously declined to issue a temporary restraining order, relying on xAI's delay in seeking emergency relief. That ruling did not decide whether the statute violates the First Amendment. The court fast-tracked the preliminary-injunction dispute and scheduled a hearing for August 19.

The immediate question is whether the law remains enforceable while the case proceeds. The broader question will survive whichever side wins that motion: when a general-purpose AI system makes a specific form of abuse nearly instantaneous, may the government regulate the capability itself, or must it wait for an unlawful user, a completed image, and a victim trying to contain the damage?

The Constitution should not be treated as a permission slip for digital undressing. It should not be treated as an inconvenience that disappears when a technology is offensive either. Minnesota has identified a real regulatory gap. xAI has identified real drafting defects. The court now has to decide which problem the First Amendment requires it to confront first.

General educational information only. X.AI LLC v. Ellison is pending, the parties' factual assertions remain contested unless established in the record, and this article is not legal advice.