Take It Down Act nude image removal: what the 48-hour rule requires
Federal enforcement of the Take It Down Act is now active. For the first time, Americans have a statutory right to demand that platforms remove nonconsensual intimate images real or AI-generated within 48 hours. That right is real. Whether it produces results depends almost entirely on what happens before the clock starts.
The law requires covered platforms to remove flagged content and known identical copies within 48 hours of receiving a valid request, per FTC enforcement guidance published this month. The word "valid" carries most of the statute's practical weight and the statute does not define it. That gap is where the process will move quickly for some people and stall for others.
The scale of the problem the law addresses is not abstract. During the 2023-2024 school year, 15 percent of high school students reported hearing about deepfakes of nonconsensual intimate images depicting classmates, according to Congressional debate records. The Take It Down Act nude image removal framework was built partly in response to that evidence.
This piece covers what the law actually requires from platforms, what a person filing a removal request will likely encounter, where the process tends to stall, and what to do if a platform ignores the deadline.
What the law requires: two obligations, one ambiguity
Video of the Day
The Take It Down Act does two distinct things. It criminalizes the publication of nonconsensual intimate visual depictions including real photos, videos, and AI-generated deepfakes and it separately requires covered platforms to build a functioning removal process, per the FTC's legal summary of the statute. The criminal provision matters: it puts legal stakes behind what might otherwise be treated as a terms-of-service question.
On the removal side, any identifiable individual can file a request, and the statute explicitly allows authorized third-party filers meaning a parent, lawyer, or advocate can submit on behalf of a minor or someone who cannot act alone, according to the Congressional Record. Once a platform receives a valid request, it must remove the original content and make reasonable efforts to find and pull known identical copies all within 48 hours.
That last phrase, "valid request," is where the statute's most consequential ambiguity sits. The law sets the deadline but does not specify what information a request must contain, how someone proves they are the person depicted, or what evidence is appropriate for AI-generated content. Those questions are left to each platform's implementation. Until enforcement cases or FTC rulemaking provide clearer guidance, what platforms actually require in practice will vary and that variation is likely to shape how quickly requests move through the system.
Video of the Day
Take It Down Act nude image removal: how the request process works
Platforms are required to provide a clear and conspicuous notice and removal process not a buried link, not a generic abuse form, the FTC specified this month. In practice, the first obstacle many people encounter is finding the form at all.
The FTC's September 2025 enforcement action against Aylo, the adult platform operator, offers a benchmark for what thorough compliance looks like. Under that order, each Aylo site was required to add a dedicated "Content Removal Request" tool, suspend flagged content upon receipt, and if asked assign a case manager to anyone going through the removal process, the FTC reported at the time. Most platforms will not offer that level of support. The Aylo requirements came from a specific enforcement action, not the statute itself.
The FTC has also published consumer-facing guidance specifically on requesting intimate image removal, updated late last year a signal that the agency anticipates people will need help navigating the process.
The statute does not publish a universal filing checklist. Based on what the law requires, though, a person preparing a request should expect to provide their identity and contact information, a statement confirming they are the person depicted (or authorization documentation for third-party filers), URLs or screenshots locating the specific content, and for AI-generated images, whatever context they have about how the image was created or distributed. Gathering this before opening a form is faster than trying to locate it mid-submission.
Several friction points are likely to slow requests down. Some platforms require account login before a report can be filed which could force a victim to create a profile on a service they have no relationship with. Others may route intimate image complaints through validation flows built for copyright disputes, which ask different questions and use different standards. What counts as sufficient identification is not standardized across services. No cross-platform data yet exists on acceptance rates, rejection rates, or how often the 48-hour deadline is actually met. That evidence is not yet publicly available.
One other limitation worth understanding: the law requires platforms to remove known identical copies, but the statute addresses copies, not variants. Re-cropped versions, reposts with modified metadata, and content mirrored on services outside U.S. jurisdiction are not clearly covered by the same request. A successful takedown from one platform does not automatically clear the content elsewhere.
Which platforms are covered and where coverage is unsettled
Covered platforms under the law include social media services, messaging apps, image and video sharing sites, and gaming platforms, per the FTC's compliance guidance published this month. That list covers most apps people use daily.
Congress framed the requirement as applying to "social media and other online public platforms," according to the Congressional Record language broad enough to suggest the named categories are illustrative rather than a closed list.
Platforms also have a concrete legal incentive to act quickly. The statute shields them from liability for removing content in good faith based on a user's request, even if the content is later found not to have been unlawful, per the law's liability provisions. Moving fast carries no legal risk. Moving slowly, on a valid request, does.
What remains unresolved is the law's reach at the edges. Whether encrypted messaging apps, cloud storage services, smaller independent forums, and platforms operated outside the United States fall clearly under the Act has not been addressed in public guidance. Filing a request on those services may mean doing so under a law whose application is uncertain which translates to lower compliance pressure and fewer remedies if the platform does nothing.
If the platform doesn't move
Missing the 48-hour deadline on a clearly valid request is not a customer service failure. It is an enforcement question. FTC enforcement is active as of this month, per the agency's guidance, and platforms cannot treat the removal obligation as optional.
Document everything. Save a timestamped record of the request, the platform's confirmation if one is provided, and any response received. If the deadline passes without action, that record becomes the foundation of a complaint.
The FTC accepts consumer complaints and has stated that enforcement is underway. A form that won't load, a platform that ignores the deadline, a request rejected without explanation each of those is a concrete reason to file a complaint with the FTC. That is not a guarantee of resolution. It does create a record and contributes to the enforcement picture the agency is building.
What that picture looks like is still unknown. No public data exists yet on request volumes, how often the 48-hour window is being met, or how frequently requests are rejected. The law is on the books and enforcement has begun. Whether platforms are actually complying at scale is the question this law will eventually have to answer and the answer will depend on what the FTC chooses to publish about what it finds.