After Removal: Copies, Hashes, and Accountability

The TAKE IT DOWN Act treats a reported intimate depiction as more than a single URL. This chapter focuses on what happens after a valid request identifies the first item: the covered platform must make reasonable efforts to find and remove known identical copies within the same 48-hour response window, while tools such as hashing, request identifiers, and status updates can make containment and accountability more workable. Readers should be able to distinguish the statutory copy duty from optional technical measures and understand why neither one guarantees that every related image has disappeared.

That distinction matters because a platform can remove the visible post while the same depiction remains available in other locations on the service. At the same time, the law does not describe an unlimited search for every image that resembles the report. Its language combines a defined object—known identical copies—with a qualified standard—reasonable efforts. The result is a duty with real reach and a real boundary.

The statutory target is the known identical copy

The Act requires a covered platform, after receiving a valid removal request, to remove the reported intimate visual depiction as soon as possible and no later than 48 hours after receipt. In that same period, it must make reasonable efforts to identify and remove any known identical copies of the depiction. The second obligation changes the unit of action. The platform is not asked only to act on the location supplied by the requester; it must also address other instances that it knows to be identical.

The reason is practical and legal at once. If the same file or depiction is posted in several places, deleting only the first reported location can leave the object of the request available elsewhere on the same service. The law's copy language recognizes that a platform's own systems may contain more than one instance and that a removal process should not force the depicted person to submit a new request for every known duplicate. The Federal Trade Commission's stakeholder letter makes this point directly: people who file a request do not need to report duplicate images, and platforms must make reasonable efforts to find and remove known identical copies within 48 hours of a valid request.

The words “known identical copies” set a boundary. The statute does not say that a platform must find every image that is related to the reported depiction, every altered version, or every image that a person believes looks similar. It also qualifies the effort as reasonable. The sources do not define when a copy becomes “known,” what level of search is reasonable, or how to treat a crop, recompression, edit, or perceptually similar depiction. Those omissions matter because they prevent the reader from converting the statutory rule into either an impossible universal-deletion promise or an excuse to ignore discoverable duplicates.

The timing is equally important. The copy obligation sits inside the same “as soon as possible” and no-later-than-48-hours framework as removal of the reported depiction. It is not presented as a separate, later project that can wait until the first item is deleted. A platform that receives a valid request must connect the reported item and the known identical-copy search to the same response period. The law nevertheless leaves room for judgment about what reasonable efforts can identify and how the platform knows that two instances are identical.

This creates a useful distinction between sameness and similarity. A known identical copy is the same depiction in another location.