TL;DR: AO3 allows fics written fully or partly with AI, as long as each one is a real fanwork, copies no one and is not posted as spam. Writers are asked to tag AI use, and the tag is voluntary. What AO3 forbids is scraping its archive for commercial AI or paid apps, and it cannot pull fics back out of datasets that already exist.
The AO3 AI policy surprises most people who look it up. Archive of Our Own allows fics made fully or partly with AI, and the volunteers who enforce its rules give a plain reason: they cannot tell AI writing from human writing reliably.
The only ban they say they could enforce would land on writers who admit using AI, which would discourage honest tagging and leave readers less able to filter.
The numbers back that call more than I expected. In early October 2026, 11,778 of AO3’s 18.63 million works carried the Created Using Generative AI tag, about one in every 1,580.
That count only covers writers who chose to tag, so untagged AI works are not in it, and AO3’s rules team said in 2024 that it had not seen a flood of AI fics.
Below are the rules, the tags, the reader filters and what AO3 can do about scraping, including the AO3.life clone of November 2026.
If you draft with our AI fanfic generator, the last section shows what you owe readers before posting.
What Does the AO3 AI Policy Say About Posting AI Fics?
The AO3 AI policy allows fics made fully or partly with AI, as long as each one qualifies as a fanwork and breaks no other rule.
The OTW, the nonprofit that runs AO3, first said so in May 2023, and the current Terms of Service, effective November 19, 2024, did not change it.
In its May 2023 statement, the OTW wrote that “nothing in our Terms of Service” prohibits fanworks “fully or partly generated with AI tools” from AO3, if they “otherwise qualify as fanworks.”
Its 2024 Terms of Service guide repeats the point: “We have not added any specific rules with respect to posting AI-generated works.”
The four rules below matter more to me than the AI question itself, because they apply to every fic, AI or not:
- It has to be a fanwork. AO3’s Content Policy says “Works must be fanworks,” and a work made mostly of non-fanwork content is not allowed.
- It cannot copy. Per the 2024 guide, an AI fic that reproduces “entire sentences or paragraphs from another work” can break the plagiarism or copyright rules, “just as any non-AI work would be.”
- It cannot be spam. “If a user posted many AI-generated works in quick succession, that may be considered spam,” says the same 2024 guide.
- It cannot sell anything. The Terms of Service ban “any commercial activity,” so an AI fic that promotes a paid app or a paid audiobook breaks the rules for that reason alone.
Using AI only to brainstorm, the way other writers use fanfic idea lists, triggers none of these rules. The table sorts the common cases.
| What you did with AI | Allowed on AO3? | Rule that decides it |
|---|---|---|
| Brainstormed, then wrote every sentence yourself | Yes | No AI rule applies |
| Used grammar or translation tools | Yes | Tagging encouraged |
| Posted an AI draft you rewrote | Yes | Must be a fanwork |
| AI draft reuses whole sentences from the book | No | Plagiarism and copyright |
| Posted dozens of AI fics in one sitting | Can count as spam | Spam rule |
| AI fic that promotes a paid AI app | No | Commercial promotion ban |
Why Won’t AO3 Ban AI-Generated Fanfic?
AO3 won’t ban AI fanfic because its volunteers cannot reliably spot AI text, and AI detectors flag too many human writers to act on.
AO3’s Terms of Service guide says “a ban against AI works is not enforceable” and calls detection programs “extremely unreliable and prone to false positives.”
What is an Archive Warning: One of the mandatory warning choices every AO3 work must carry, such as Major Character Death, which the abuse team enforces.
The same guide makes a second argument. The only ban AO3 could safely enforce would hit works that disclose AI use, and that “makes it more difficult for users to filter out AI works if they want to do so.” So AO3 asks for tags and declines to make AI an Archive Warning, since its abuse team “would not be able to enforce the Warning’s presence.”
That reasoning is the part of the policy I find hardest to argue with, even if you hate where it lands.
The guide also reports that what the abuse team saw was “a sharp uptick in AI use in spambot comments,” while AI-generated works never arrived in a flood.
How Do You Tag AI Use on an AO3 Fic?
AO3 asks writers who used AI to add the Created Using Generative AI tag, or its narrower AI-Generated Text or AI-Generated Images tags, in the Additional Tags field.
None of the three is required, and none is an Archive Warning.
The tag page for Created Using Generative AI lists it as a canonical tag that readers can “use it to filter works.” AO3’s tag wranglers, the volunteers who link similar tags, had merged 300 different user-written tags into it by September 2026.
They run from “#ai” and “2 Percent AI Assistance” to “Translated by ChatGPT” and “Use grammarly and DeepL.”
That merge matters for both sides. A writer who tagged “(AI-Assisted Editing)” is already caught by the filter, and so is a writer who tagged a machine translation.
I’d pick the narrower AI-Generated Text tag whenever a model wrote the sentences, because it tells readers the most.
Before: tags like “(AI’s output was heavily edited)” or “90per ai” that only some readers will understand
After: Created Using Generative AI plus AI-Generated Text, with one line in the author’s note saying what the AI did, such as “AI drafted the first scene, I rewrote it”
In early October 2026 the parent tag held 11,778 works, including 5,081 tagged AI-Generated Text and 2,421 tagged AI-Generated Images.
How Do You Filter AI Fics Out of AO3 Searches?
To hide tagged AI fics, open the Filters panel on any AO3 works listing, type Created Using Generative AI into Other tags to exclude, and press Sort and Filter.
Works under its two narrower tags count toward it, so one exclusion catches all three.
- Open any works listing, such as a fandom page, a tag page or your search results.
- Find the Filters panel beside the list, or tap Filters at the top of the list on a phone.
- In the exclude section, type Created Using Generative AI in Other tags to exclude.
- Press Sort and Filter.
- Bookmark the filtered page, since the exclusion lives in that page’s address.
My one warning is about a look-alike tag. “Artificial Intelligence” is a story-theme tag for robots and AI characters, with 6,548 works in August 2026, so excluding it hides stories about AI and leaves AI-made fics in place.
The filter also only catches writers who tagged, which is the cost of a voluntary system. AO3 has been offline since October 29, 2026, and the OTW has since reported a security incident.
Its November 6 status update says the original return estimate of two to four weeks still holds, so these steps work again once the site is back.
Is AO3 Protecting Your Fics From AI Scraping?
AO3 blocks known AI crawlers and bans scraping for commercial AI, but it cannot pull fics back out of datasets built earlier, and locking a work is no guarantee.
Its Terms of Service FAQ forbids “scraping AO3 for the purposes of obtaining material for commercial generative AI or creating an app that hosts or paywalls AO3 content.”
The defenses are real: the OTW’s 2023 statement says it put code in place in December 2022 asking Common Crawl, a web archive “used to train AI such as ChatGPT,” to stop crawling AO3.
It also uses rate limiting against large-scale scraping. AO3’s 2024 Terms of Service guide adds that it has “banned and will continue to ban accounts that place an unreasonable burden on the servers by scraping.”
The gap is everything taken earlier. The OTW’s statement admits “We cannot go back in time to stop data collection that already occurred,” and I keep coming back to that line, because no setting protects a fic that was already copied.
Copies keep surfacing. In April 2025 a user of Hugging Face, a site for sharing AI models and datasets, posted a dataset of about 12.6 million public AO3 works.
Fanlore’s account says DMCA notices, the US legal requests for removing copied work, got it deleted or disabled by April 23. The uploader then re-posted it on ModelScope, a Chinese model-sharing site that pulled it within hours, and on a personal site based in Russia, where, per Fanlore, it remained live.
A separate fiction dataset on Hugging Face lists AO3 as 22.2% of a collection of more than one billion words.
Does Locking Your Work to Archive Users Stop AI Scrapers?
Locking a work to logged-in AO3 users stops bulk crawlers without accounts, but not a scraper that signs in, so treat it as a speed bump.
The OTW’s own advice says locking “will not block every potential scraper,” though “it should provide some protection against large-scale scraping.”
Locking has worked before. Many writers began locking their fics in 2023, TechCrunch reported, and Fanlore notes that the 2025 dataset left out works restricted to registered users.
The November 2026 clone went further. In the r/FanFiction thread on it, a writer who keeps their work locked to archive users still found it there, and the reply was blunt: “Scrapers have accounts now.”
Locking is still worth doing in my view, since it shuts out the cheapest scrapers.
What Should You Do If an AO3 Clone Copied Your Fic?
If a clone site copies your fic, do not send it your AO3 email or any proof of identity, and file the takedown yourself, because the OTW cannot file it for you.
In a support reply the r/AO3 moderators shared, the OTW said its abuse committee “can only take action on violating activity that occurs on AO3 itself.”
The test case is AO3.life, which appeared in early November 2026 while AO3 was down. The same moderators’ post says it was “spun up using an old scrape of the archive.” Writers on r/FanFiction found it was “turning them into AI generated podfics/audio books” that it charged people to access.
The removal form is the part that bothers me most. To take a fic down, the site asked for the email tied to your AO3 login, days after the OTW said it could not rule out theft of AO3’s user database.
The moderators’ advice was short, “do not contact the website,” and they later reported the site “down for good.”
- Do not email the clone, fill in its forms or confirm your AO3 address.
- Save the copy’s URL with a screenshot and the date.
- Send a copyright takedown notice to the site’s web host or domain registrar, since only “the copyright owner (the creator of the fanwork)” can file one, per the OTW’s reply to fans.
- Change the password on any other site where you reused your AO3 password, which the OTW’s October 30 status update also recommends.
Why Are So Many Fans Angry About AI on AO3?
Many fans see AI fics and AI scraping as taking from unpaid fan writing without consent, and AO3’s refusal to ban AI looks to them like taking a side.
The anger has been building since May 2023, when an OTW newsletter quoted its legal chair speaking approvingly of AI-generated fanfic.
The OTW called that quote the opinion of one volunteer, then published its AI statement on May 13, 2023, which drew 862 comments on AO3’s news page, per Fanlore.
The pressure has not let up: a Change.org petition to ban AI from AO3, started on July 14, 2026, had 395 verified signatures toward its goal of 500 on November 6.
I don’t buy the claim that AO3 is quietly pro-AI. The same archive blocked Common Crawl in December 2022, before most of the outcry, wrote commercial scraping out of its terms in 2024, and removes AI spambot comments as they are reported.
Can You Tell If a Fic Was Written by AI?
You cannot tell reliably, and AO3 will not act on a guess or a detector score.
AO3’s Terms of Service guide says humans “are not able to reliably detect the use of AI in creative works,” and that detection tools are “prone to false positives.”
A writing style, a run of long paragraphs or a fondness for dashes is not proof, and accusing a writer on that basis can hit someone who wrote every word.
I wouldn’t accuse anyone on a detector score, and the only signal worth filtering on is the tag a writer chose to add.
Can You Use an AI Fanfic Generator and Still Follow AO3’s Rules?
AO3 has no rule against drafting with an AI fanfic generator, so the real work starts after the draft: check that it copies nothing, fix canon, and tag it if you post it.
A test draft from the AI fanfic generator used Pride and Prejudice as the fandom, with Elizabeth Bennet and Fitzwilliam Darcy as the characters.
The other settings were a Romance with the Second chance trope, a Bittersweet tone, third person, a General audiences rating and Short length.
The idea was a missing scene: the morning after Elizabeth refuses Darcy’s first proposal, she reads his letter in the grove. It returned 481 words in about 10 seconds, opening with “The letter was heavier than paper should be.”
None of the draft’s 37 sentences appears in the novel, and no six-word run matches either, so it passes AO3’s copying rule. It still gets the scene wrong.
In the novel’s text, Darcy hands Elizabeth the letter himself at the grove gate, and it opens by promising no “repetition of those sentiments.”
The draft leaves the letter “waiting on the stone bench,” has it declare his love, and never mentions Wickham, who is named 12 times in the real letter.
That result tells me the copying rule is the easy part. A draft like this needs a human pass before it reads as a fanwork, and our guide on writing fanfiction covers that edit.
If you post it, the honest tags are Created Using Generative AI and AI-Generated Text, plus a line in the author’s note saying what you changed.
Before: “The letter had been waiting on the stone bench where she always sat.”
After: “He was at the gate before she could turn back, holding out the letter.”
Quick Takeaways
- AO3 allows fics written fully or partly with AI if they are fanworks, copy nothing and are not posted as spam.
- Tag AI use with Created Using Generative AI, or the narrower AI-Generated Text, since AO3 will not make it a warning.
- Readers can hide tagged AI fics by excluding Created Using Generative AI in the Filters panel, but untagged ones still slip through.
- AO3 bans scraping for commercial AI, yet copies taken before its blocks still circulate, and locking is no guarantee.
- If a clone copies your fic, never hand it your AO3 email, and file the takedown yourself.
