AI fanfiction site shuts down after author backlash over scraped stories
The creator said more than 2,000 takedown requests arrived in one day. Promised revenue sharing had not secured authors’ permission.
Loading page…
The creator said more than 2,000 takedown requests arrived in one day. Promised revenue sharing had not secured authors’ permission.
Listen to this story
ao3.life, a fanfiction clone launched during Archive of Our Own’s outage, shut down November 2 after its creator, Ganesh, said it received more than 2,000 takedown requests in one day. The site had copied AO3 stories without permission, offered EPUBs and paid AI-narrated audiobooks, and promised authors 91% of audiobook profits without their consent. The episode highlights the gap between an automated compensation offer and actual rights clearance: AO3’s outage was temporary, and its owner said no works were lost.
Ganesh said AI agents running on 40 virtual machines found stories across online drives, existing scrapes, and other sources.
The creator said the clone attracted 126,592 unique users in 24 hours, consumed terabytes of bandwidth, and sold about 11 audiobooks.
Authors’ takedown verification instructions relied on an AO3 profile note, but AO3 was offline during the outage.
ao3.life promised to preserve access to fanfiction and share audiobook profits with its authors. Instead, the site shut down on November 2 after its creator said more than 2,000 takedown requests arrived in a single day. It had copied Archive of Our Own stories and sold AI-generated audio versions without their authors’ permission.
The shutdown followed widespread backlash from readers and writers, according to 404 Media’s Samantha Cole. The creator, identified as Ganesh, apologized and said closing the site was the clearest way to demonstrate that apology. Their explanation presented the project as an attempt to help readers, rather than hurt authors.
The clone appeared during an extended outage at Archive of Our Own, usually called AO3. Its owner, the Organization for Transformative Works, said a security incident had taken the repository offline on October 29. The outage could last up to four weeks, but the organization said no data had been lost.
That distinction sat awkwardly beside ao3.life’s preservation pitch. Its homepage declared: “AO3, saved before it slips away.” AO3 hosts nearly 18.5 million works, and readers were unable to reach the repository during the outage. But its owner had described a temporary loss of access, not the disappearance of the collection.
Ganesh said AI agents running across 40 virtual machines searched the internet for drives, existing scrapes and other sources of stories. The resulting site offered copied works as EPUB files for e-readers and as AI-generated audiobooks. Listening was free for the first three minutes; continuing required payment.
On a page titled “Authors get paid here,” ao3.life promised writers 91% of audiobook profits, retaining 9% for narration and processing. It said authors did not need an account to accumulate earnings and that their share would be held indefinitely until collected. The offer did not mean authors had agreed to participate.
The commercial offer also differed from AO3’s rules: authors there cannot monetize their works or link to payment platforms. Ganesh defended the audiobook charges as a way to cover server costs, saying the clone had attracted 126,592 unique users within 24 hours and consumed terabytes of bandwidth. They said they sold about 11 audiobooks.
It was never my intention to hurt so many authors - and I’m truly sorry to you all. There’s no way to show my sorry [sic] better than taking this site down.
Ganesh, in an apology quoted by 404 Media
ao3.life told authors they could email a legal address to have their stories removed. Yet its ownership-verification instructions asked them to leave a note on their AO3 profile. With AO3 completely offline, authors could not use that route to prove who they were—the same outage that helped create demand for the clone.
Writers also could not log in to change which stories were publicly accessible. AO3 allows authors to restrict works to logged-in readers, a setting known as an archive lock. One author quoted by Cole said their stories appeared on ao3.life despite already having that restriction, and complained of having no control over the copies.
Loading discussion...
Join the conversation
Explain whether payment changes where you draw the line.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.