What Happened to LimeWire Why the King of Free Music Fell

LimeWire wasn’t shut down because its technology failed. In a strange way, it worked too well. At its peak, LimeWire was installed on nearly one in six Windows PCs, used by tens of millions of people, and powered by a decentralized network with no central server, no master index, and no single machine that could simply be switched off. That architecture was LimeWire’s greatest strength. It also became part of the case that destroyed the company. This video tells the story of how LimeWire went from a Java-based Gnutella client built in New York to one of the most recognizable file-sharing programs of the 2000s — and how a Supreme Court decision, LimeWire’s own business decisions, its paid Pro version, copyright infringement lawsuits, and one federal court ruling changed everything. In 2010, LimeWire was ordered to disable its file-sharing software. Founder Mark Gorton was held personally liable. The company later settled with the record industry for $105 million. But there was one problem. The company could be shut down. The network couldn’t. Just weeks after the injunction, an unauthorized version known as LimeWire Pirate Edition appeared — because the decentralized Gnutella network had never belonged to LimeWire in the first place. The engineering designed to make LimeWire difficult to kill had succeeded. And that same engineering helped put its founder’s name on the judgment. If you used LimeWire back in the 2000s, there’s a good chance you still remember the search bar, the painfully slow downloads, the suspicious MP3 filenames, LimeWire Pro… and that shared folder buried somewhere on an old hard drive. What’s still in yours? Comment below with the oldest file you still have from your LimeWire days — and tell me which story should be next: Napster, Kazaa, or RealPlayer. #LimeWire #FileSharing #InternetHistory #TechHistory #Napster #Gnutella #P2P #Piracy #MusicIndustry #2000sInternet