The record industry's campaign against stream rippers produced one of the most-cited copyright jurisdiction decisions in recent memory, a settlement that quietly switched off the world's best-known YouTube converter, and a GitHub takedown that collapsed within a month. It produced very little money. That gap between legal victories and operational results is the story of streaming ripper lawsuits, and it explains which enforcement levers actually work in 2026.
The practical answer for anyone affected: you cannot notice-and-takedown a ripping tool out of existence, because the tool stores nothing. You can remove the copies the tool creates, re-uploaded videos, shared audio files, mirrored courses, through ordinary takedowns where those copies live. Everything below builds on that distinction.
Why Stream Rippers Broke the Standard Takedown Playbook
A stream ripper takes a stream meant to be heard or watched once, a YouTube video, a radio feed, a livestream, and saves it as a permanent file. The copy is made on the user's device. The site that arranged the conversion never stores the recording on its own servers.
That design defeats the DMCA's core mechanism. Notice-and-takedown, the process at the center of how DMCA safe harbor works, assumes a copy sits somewhere a host can reach and remove. Send a takedown notice about a specific song to a converter site and the plain answer is that nothing on its servers belongs to you. The notice has no target.
So the labels built different theories. The main one is secondary liability: contributory infringement for knowingly supplying the means of infringement, vicarious liability where the operator has the right and ability to control the activity and profits from it, and inducement, the theory the Supreme Court added in Grokster, holding that promoting a product for infringing uses creates liability even when the product has lawful ones. Converter sites advertise one function, which makes the inducement theory unusually easy to plead.
The industry had also tested the softer route first. In September 2016, youtube-mp3.org, then the largest converter in the world, shut down after settling with the major labels. Two years later the labels went back to court against an operator who refused to settle. That campaign is one chapter in a longer courtroom record covered in our history of RIAA piracy lawsuits, but the FLVTO case deserves its own account.
The FLVTO and 2conv Lawsuit, Filed in a Virginia Courtroom
In October 2018, the US record companies of the three major music groups, Universal, Sony, and Warner, sued Tofig Kurbanov, the Russian operator of flvto.biz and 2conv.com, in the Eastern District of Virginia. The RIAA's name attaches to the campaign, though the plaintiffs were its member labels. The Eastern District has one of the fastest civil dockets in the federal system, which is part of why copyright plaintiffs choose it.
The complaint did not allege that the sites stored the labels' recordings. It alleged that they built a business on them. A user pastes a URL, the service converts the stream into a downloadable file, and the operator earns advertising revenue on enormous traffic. Contributory and vicarious infringement were the operative counts, with the inducement theory doing much of the work.
Kurbanov did not fold the way youtube-mp3.org had. He answered through counsel: the sites were run from Russia, under Russian law, with no meaningful presence in Virginia. That response turned the first phase of the case into something bigger than a copyright dispute, a fight over whether a US court could hear it at all. The sites' massive US traffic sat at the center of that fight.
The Jurisdictional Saga: Dismissal, Appeal, and the 2020 Reversal
In 2019, the district court dismissed the case. A Russian operator running servers abroad, the court reasoned, was not purposefully availing himself of Virginia; a website that merely happens to be visible from a forum is not the same as deliberately doing business there. Under that reading, suits against foreign converter operators would have been nearly impossible anywhere in the country.
The labels appealed, and in March 2020 the Fourth Circuit reversed. UMG Recordings, Inc. v. Kurbanov, 961 F.3d 327 (4th Cir. 2020) is now the leading appellate precedent on suing foreign website operators in US courts. The panel emphasized what Kurbanov actually did: he operated English-language sites on commercial top-level domains, served enormous numbers of US visitors, earned substantial advertising revenue from them, and never geo-blocked the United States. An operator who cultivates a US audience and profits from it has availed himself of the US market, and an operator who wants to avoid US jurisdiction can decline to serve US users.
Two caveats matter. First, the Fourth Circuit decided jurisdiction only; no court ever ruled on the infringement claims on the merits. Second, the decision is Fourth Circuit law, persuasive elsewhere but binding only there.
The ruling also settled something practical. The DMCA is a US statute with no extraterritorial reach; personal jurisdiction is the doorway that brings a foreign operator under US law at all. Win that fight and the merits proceed in a US courtroom. Lose it and the plaintiff is choosing between foreign courts and pressure applied outside the courtroom. How the DMCA works internationally fills in the rest of that map.
The Default Judgment Against FLVTO and 2conv, and What It Bought
On remand, the case sputtered. The operator's defense wound down, Kurbanov stopped actively participating, and the labels moved for default. The court granted a default judgment in their favor, with injunctive relief. On paper, total victory.
In practice, it bought much less. An injunction binds the defendant, not the internet. It cannot make American ISPs block the sites, because the United States, unlike the UK, Australia, and a lengthening list of countries, has no general site-blocking statute. And a judgment against an operator in Russia, with no visible US assets, is close to uncollectible. Statutory damages under 17 U.S.C. § 504(c) can reach $150,000 per work for willful infringement, and thousands of recordings were in suit, so the paper exposure was staggering. How statutory damages actually work, and how rarely they convert into collected funds from judgment-proof defendants, is a topic of its own.
The real yield was the precedent. Kurbanov changed the calculus for every foreign site operator doing business with US users, and it handed right holders credible leverage in negotiations: after March 2020, a threat to sue in a US court was believable. In enforcement economics, that is often the point of filing. Judgments are instruments. The shadow they cast does the work.
The y2mate Settlement: Shutdown Without a Trial
y2mate spent years at or near the top of the converter market, routinely ranked among the most-visited ripping sites in the world. Its exit shows what the litigation track rarely delivers.
According to industry reporting, the major labels reached a settlement with y2mate's operator in 2023. The terms were never published; settlements like this almost never are. What is visible is the outcome: the site stopped offering its ripping services and began pointing visitors toward licensed alternatives. The deal followed the template set in 2016, credible legal exposure, negotiated wind-down, clean exit.
For rights holders, this is the quiet lesson of the whole campaign. A default judgment against an absent defendant is a legal event. A settlement that turns off a service is an operational one. Settlements also solve the two problems litigation cannot: the operator has a reason to actually comply, and nobody has to collect anything.
The economics run both ways. For a site owner earning advertising revenue on enormous traffic, a settlement converts existential legal risk into an orderly shutdown. For the labels, a guaranteed exit by the world's most prominent ripper was worth more than an uncollectible damages award. Enforcement budgets are finite. Spending them on outcomes rather than paper is the discipline this campaign eventually taught.
The youtube-dl Takedown: Section 1201 Meets Open Source
In October 2020, while the FLVTO case wound down, the RIAA sent GitHub a takedown notice, on behalf of the major labels, targeting youtube-dl, an open-source library for downloading YouTube videos with thousands of users: archivists, journalists, developers building research tools. GitHub removed the repository. The reaction was immediate and hostile.
The legal theory differed from the converter-site suits. This notice invoked the DMCA's anti-circumvention provision, Section 1201(a)(2), which bars supplying technology designed to get around technical measures protecting copyrighted works. The notice claimed youtube-dl circumvented YouTube's 'rolling cipher' signature mechanism, and it leaned partly on rulings from foreign courts against similar tools, a reminder that platform practice and foreign law often run ahead of anything a US court has decided. The youtube-dl GitHub takedown is covered in depth on its own page, alongside the Section 1201 anti-circumvention rules that powered the notice.
The claim ran into trouble fast. EFF, working with the project's maintainers, submitted a counter notice arguing that youtube-dl defeats no access control at all: YouTube serves streams to any ordinary browser, and the rolling cipher is a request-signing mechanism, not a lock. GitHub's process gave the RIAA a window to sue and defend the takedown. The RIAA let it pass. In mid-November 2020, GitHub restored the repository, put a million dollars into a legal defense fund for developers, and rebuilt its process for 1201 claims.
No US court ruled on the merits, and the labels never sued the maintainers. The episode left two marks. First, takedown senders who knowingly misrepresent their claims face exposure under Section 512(f), as the Diebold case demonstrated years earlier. Second, the tool-versus-service line hardened: monetized ripping services are litigation targets; open-source tools with substantial lawful uses are expensive to attack, and the majors have largely left youtube-dl and its active fork, yt-dlp, alone since. If you build or host downloader tools, take a notice like this seriously and get advice before responding, because the underlying dispute was never settled by anyone.
Where Stream-Ripper Enforcement Stands Now
A decade of lawsuits and settlements has reshaped the top of the market. youtube-mp3.org exited in 2016. FLVTO and 2conv have continued operating in some form, shadowed by a US judgment their operator does not honor. y2mate left by settlement in 2023. The gap filled with a long tail of clones that appear, draw traffic for a few months, and re-emerge under new domains, the same clone-and-replace cycle the industry has known since the Napster shutdown. Suing each one is arithmetically hopeless.
So enforcement moved to chokepoints, where one action reaches many sites. The labels and their trade bodies pressure the ad networks that monetize converter sites and the payment processors that move their revenue; a ripper that cannot monetize has a short lifespan. Platform policy does quiet work too: app stores periodically purge converter apps, and search engines demote sites that accumulate takedown records. Those are contract and policy levers, not statutes, and they change without notice, worth remembering when you predict what a platform will do. Courts abroad do something US courts cannot: order ISPs to block pirate sites outright. How site-blocking orders work explains that machinery; US law simply has no general equivalent. USTR's annual Notorious Markets reviews, meanwhile, flagged stream-ripping year after year, raising the temperature for hosts, registrars, and advertisers that touch the sites.
Individual users have mostly stayed out of the line of fire. No wave of consumer lawsuits followed the ripper cases; enforcement concentrates on operators and services. Using a ripper is still an unauthorized reproduction, still breaches platform terms, and can end accounts, but the lawsuit risk belongs to whoever runs the tool.
For creators, the takeaway is the one from the top of this article. The ripping tool is mostly out of reach. The copies it creates are not: ripped tracks resurface as re-uploads on YouTube, SoundCloud, file lockers, and Discord servers, and every copy is takedown-eligible where it lives.
Frequently Asked Questions About Stream-Ripper Lawsuits
Is using a YouTube to MP3 converter illegal?
In the US, the file you make is a reproduction of a copyrighted work, and copying without permission infringes unless an exception applies. Fair use might cover narrow purposes such as research, criticism, or accessibility; a simple wish to own an MP3 has no winning track record in the courts. YouTube's terms also prohibit downloading outside official channels, which adds a contract problem on top of the copyright one.
Can US courts reach a stream-ripper operator based abroad?
Yes, when the operator deliberately serves US users. Under the Fourth Circuit's 2020 Kurbanov decision, running a site that draws heavy US traffic and earns US advertising revenue counts as purposeful availment, especially with no geo-blocking. Reaching an operator and collecting from one are different problems, though, which is why these disputes often end in negotiated shutdowns instead of judgments.
Why did GitHub restore youtube-dl after the RIAA takedown?
EFF and the maintainers filed a counter notice arguing the tool circumvented nothing, since YouTube serves streams to ordinary browsers and the rolling cipher is request signing rather than a lock. GitHub gave the RIAA a window to sue and defend the takedown; it passed. The repository went back up in November 2020, and no court ever ruled on the merits.
Can you send a DMCA takedown notice against a stream-ripper site?
You can send one, but notice-and-takedown has nothing to bite on, because the site stores no infringing files. The responses that work look different: abuse reports to the host about a circumvention service, complaints to the site's ad networks, app-store reports where an app exists, and litigation on secondary-liability theories. Those are the levers the labels actually used.
What can I do if my music is being ripped and shared online?
Target the copies, not the tool. Ripped tracks resurface as uploads on YouTube, SoundCloud, file lockers, and Discord servers, and each copy can be removed where it lives. Document everything before you begin, send notices to the hosting platforms, and monitor for re-uploads, our guide to stolen music online walks through the full sequence.
If Your Content Is Being Ripped: A Practical Checklist
- Separate the two problems. The ripper is a tool you most likely cannot remove. The copies it produces are targets you can. Spend your effort accordingly.
- Preserve evidence first. Capture URLs, dates, and copies of the infringing pages before sending anything, because content moves once it is noticed. The takedown evidence checklist lists what to keep.
- [Find out who hosts each copy](/kb/find-out-who-hosts-a-website) and where the operator sits. That determines which route will work.
- File takedowns against the re-uploads on the platforms where they sit. This is the ordinary, high-yield work, and it scales.
- Use chokepoints on the ripper itself, the host's abuse desk, the site's advertisers, its app-store listing, if the volume justifies the effort.
- Put monitoring in place. Ripped copies reappear, and a scan-and-takedown service such as ProtectionPro keeps cleanup ahead of the re-uploads instead of behind them.
- Match the help to the stakes. For monetized piracy at scale, knowing when to hire a copyright lawyer versus a takedown service is itself an enforcement-economics decision, and it is worth making deliberately.