While AO3 is down, fanfiction clone sites are reposting authors’ work without consent, and one was even selling AI audiobooks
ao3.life tried to sell AI audiobooks of fanworks, and the fallout is putting fandom’s protections at risk
When Archive of Our Own (AO3) went offline, the team behind the site estimated service restoration could take 2 weeks to a full month. Readers and authors alike braced for a long, agonizing wait. What they didn’t expect was a swarm of opportunists moving in to fill the void with their stories.
Chief among them was ao3.life, which pitched itself as the salvation of the real AO3. According to Kotaku, it hosted an outdated, unauthorized version of the fanfiction website, with works reposted without the authors’ consent. Users also found older versions of their work, plus works they had deleted or made private. By November 2, Fanlore says the site was hosting 15,831,236 works.
It wasn’t alone. Fanlore also lists ao4.lol as another platform hosting fics scraped from AO3. Two more archives have drawn the same anger: fanfic.party, which says it has archived over 13.4 million works, and blk archive, a Black-centred fanworks archive claiming more than 13 million works from over 1.8 million authors. A Tumblr account tracking the situation says everything on these sites was nonconsensually mass-scraped from authors.
“Backup” is doing a lot of heavy lifting here
The sites differ in what they say they’re doing. fanfic.party stresses that it is not affiliated with ao3.life and does not agree with selling AI-generated audiobooks of fics for profit. It describes itself as a not-for-profit, temporary backup that will never train AI on any works, and says it archives files sent to it rather than scraping anything itself. It even acknowledges that its approach left many authors feeling frustrated and angry. blk archive’s page says all rights remain with the authors and that it is not affiliated with the Organization for Transformative Works (OTW) or AO3.
Every one of these sites has the same flaw, though: nobody asked. Writers posted their stories to AO3, under their rules, with whatever privacy settings they chose. Some locked their works to registered users. Some deleted them. None agreed to have those stories copied onto a mirror, a megadrive, or a “backup” they’ve never heard of. And the fix on offer is always the same — ask us and we’ll take it down. fanfic.party says authors can simply email to have work removed, and blk archive says writers can request a takedown or opt out.
That flips consent on its head. Authors shouldn’t have to hunt through half a dozen sites, find their own fics and beg strangers to delete them. Posting a story in one place isn’t permission to post it everywhere.
Profiting off fans, one AI audiobook at a time
ao3.life was the worst offender. It claimed to pay authors by selling their works as audiobooks, with proceeds split 91% to the author and 9% to the site. Fans say the audio was made using generative AI, and authors say they never agreed to any of it.
Getting paid or getting your work removed required sending an email from the account associated with your AO3 profile. Users on social media alleged it was an elaborate phishing and doxxing attempt, and one widely shared warning told authors not to email the site for takedowns because it had no business holding that information.
Fanfiction has survived for decades in a legal gray area, largely because it’s non-commercial and rights-holders have mostly looked the other way. The OTW maintains that fanfic authors do own the copyright to their fanfic as a transformative work. Someone profiting from that work without permission doesn’t just exploit writers. It gives companies a reason to start caring about a space that has stayed safe by staying non-commercial.
What happened to ao3.life
The site didn’t last long. The OTW said its legal team was taking legal and technical steps to dismantle the site, but before that finished, ao3.life went dark. According to fan accounts, on November 2, the site was taken down and replaced by an apology from its creator.
Users passed along a message from the owner, who they say is just a 17-year-old from India. One fan summarizing it said the owner described themselves as a teenager who wanted to run an AI farm to make some money and did an in-depth scrape of AO3, and likely some other sites. None of that has been independently verified, and readers are cautioned to take it with a pile of salt.
Then there’s the theory spreading through fandom. Some fans have speculated that ao3.life could be connected to why AO3 went down in the first place. The suspicion comes from long-deleted fics and, more alarmingly, unpublished authors’ drafts showing up on the site. One widely shared post argued it looked increasingly likely that ao3.life was behind the AO3 breach. Another noted the domain had only just been registered.
It’s important to be clear that this is speculation. OTW confirmed a security incident, not a confirmed hack, says it is still determining the scope, and has not entirely ruled out that user account data may have been accessed. Outlets covering the outage reported that the cause was still unclear. In the accounts I found, the owner’s reported explanation describes a scrape, not a breach, and the OTW hasn’t tied ao3.life to the outage.
Not the first time
This pattern is depressingly familiar. In December 2024, fans spotted WordStream, a site calling itself the “Netflix of audiobooks” that pulled popular fics from AO3 and reposted them with AI-generated audio, covers and summaries.
The OTW has warned that any website claiming it can help you access AO3 is lying, because there are no mirrors until the real archive is back. Authors can lock their fics to registered users, which AO3 itself suggested as a way to avoid data scraping. It’s not foolproof, and it shouldn’t be the writers’ job. Until the real archive returns, the best thing readers can do is skip the clones and wait for the stories to come back to the place their authors chose.
Have a tip we should know? [email protected]
Follow The Mary Sue:
