Removal is a step, not a verdict
A platform acting on a removal request has not decided that infringement occurred. It has responded to a notification. The statute deliberately gives the other side a route to respond, and that route can put the material back.
A filer who treats a removal as a final result can be caught out by what happens next. One who expects the counter-notification step can plan for it.
How a counter notification works
The uploader responds
The person whose material was removed submits a counter notification stating, under penalty of perjury, a good-faith belief that the material was removed as a result of mistake or misidentification. YouTube states that misidentification includes content that may qualify for a copyright exception, such as fair use.
It carries real commitments
A counter notification includes the uploader’s contact details and consent to the jurisdiction of a federal district court. It is not a complaint form — it is a legal statement with consequences, which is why it should not be submitted casually.
It is forwarded to the filer
The provider passes the counter notification to the party who filed the original request, including the contact information it contains.
A waiting period runs
Under the statute, the provider replaces the material not less than 10 and not more than 14 business days after receiving the counter notice, unless the filer first tells it that they have filed an action seeking a court order. YouTube states that the claimant has 10 US business days to respond with evidence of legal action, after which the content may be reinstated.
What a counter notification asks of the filer
The decision point is uncomfortable, and that is the point of the design. Continuing means going to court. Not continuing means the material is likely restored.
That is a reason to be certain before filing rather than after. A matter that was screened properly is one where a counter notification can be evaluated calmly; a matter that was filed on a similarity match is one where the filer now has to decide whether to litigate something they never examined.
Retraction is a different thing entirely
A retraction is the filer withdrawing their own request. It is not the same as losing a dispute, and it is not the same as the material being restored through the counter-notification route.
Retraction is what a responsible filer does on discovering their own notice was wrong — wrong URL, wrong work, authorization that turned out not to cover the use, an exception they did not weigh properly.
On YouTube, a request can be retracted in YouTube Studio or by email. YouTube states that a retraction by email must come from the original claimant or their authorized representative, from the same email address or company domain used for the original request, and must include links to the content, a statement of retraction and the signer’s full legal name.
YouTube also states that retracting clears the associated copyright strike and restores the content, unless other videos are associated with the strike or the uploader deleted the content.
Two things make a retraction real rather than cosmetic: it is issued through the same filing identity as the original request — for us, copyright@takedownbureau.com — so the platform can match it to the original; and it is recorded, so the correction exists as part of the case history rather than quietly disappearing.
We do not adjudicate disputes, and we do not treat a counter notification as an attack to be repelled. When we confirm an error in a request we submitted, we correct it — retracting it where appropriate — and record it. Where a retraction is appropriate and we are authorized to act on the matter, we do not charge the uploader for it.
Our public status vocabulary keeps these outcomes separate on purpose. Retracted means we withdrew the request. Restored means the platform put the material back through its own process. Reporting that collapses the two into one number is reporting we would not publish.