This tool is optional. No one is required to use it, but it's here if you want to know which of your AO3 fics were scraped. Locked works were not 100% protected from this scrape. Currently, I don't know of any next steps you should be taking, so this is all informational.
Most people should use this link to check if they were included in the March 2025 AO3 scrape. This will show up to 2,000 scraped works for most usernames.
Or you can use this version, which is slower but does a better job if your username is a common word. This version also lets you look up works by work ID number, which is useful if you're looking for an orphaned or anonymous fic.
If you have more than 2,000 published works, first off, I am jealous of your motivation to write that much. But second, that won't display right on the public version of the tools. You can send me an ask (preferred) or DM (if you need to) to have me do a custom search for you if you have more than 2,000 total works under 1 username. If you send an ask off-anon asking me to search a name, I'll assume you want a private answer.
In case this post breaches containment: this is a tool that only has access to the work IDs, titles, author names, chapter counts, and hit counts of the scraped fics for this most recent scrape by nyuuzyou discovered in April 2025. There is no other work data in this tool. This never had the content of your works loaded to it, only info to help you check if your works were scraped. If you need additional metadata, I can search my offline copy for you if you share a work ID number and tell me what data you're looking for. I will never search the full work text for anyone, but I can check things like word counts and tags.
Please come yell if the tool stops working, and I'll fix as fast as I can. It's slow as hell, but it does load eventually. Give it up to 10 minutes, and if it seems down after that, please alert me via ask! Anons are on if you're shy. The link at the top is faster and handles most users well.
On mobile, enable screen rotation and turn your phone sideways. It's a litttttle easier to use like that. It works better if you can use desktop.
Some FAQs below the cut:
First off! If you're seeing an old version of this post, you may not have seen that we now have our first tool to poison AO3 fics! This is still experimental, and it's likely we'll find issues with it as people start using it! But if you want something like Glaze and Nightshade but for fic, this is what we have right now. Before you decide to use it, please read all the info you can--most importantly, using the poison in its current state makes your fic inaccessible to certain users. All the TTS tools I've tried work with this as long as your readers know to save the fic in a certain way! But people who need to download an offline copy to adjust the colors and can't do that with an AO3 site skin will NOT be able to download your work with the current version of the poison. For downloading EPUBs, it preliminarily looks like Calibre can support "unpoisoning" the fic so it's readable again.
"What do I need to do now?": At this time, the main place where this dataset was shared is disabled. As far as I'm aware, you don't need to do anything, but I'll update if I hear otherwise. If you're worried about getting scraped again, locking your fics to users only is NOT a guarantee, but it's a little extra protection. There are methods that can protect you more, but those will come at a cost of hiding your works from more potential readers as well.
"I know AO3 will be scraped again, and I'm willing to put a silly amount of effort into making my fics unusable for AI!": Excellent, stick around here. I'm currently trying to keep up with anyone working on solutions to poison our AO3 fics, and I will be reblogging information about doing this as I come across it.
"I want my fics to be unusable for AI, but I wanna be lazy about it.": You're so real for that, bestie. It may take awhile, but I'm on the lookout for data poisoning methods that require less effort, and I will boost posts regarding that once I find anything reputable.
"I don't want to know!": This tool is 100% optional. If you don't want to know, simply don't click the link. You are totally welcome to block me if it makes you feel more comfortable.
"Can I see the exact content they scraped?": Nope, not through me. I don't have the time to vet every single person to make sure they are who they say they are, and I don't want to risk giving a scraped copy of your fic to anyone else. If you really want to see this, you can find the info out there still and look it up yourself, but I can't be the one to do it for you.
"Are locked fics safe?": Not safe, but so far, it appears that locked fics were scraped less often than public fics. The only fics I haven't seen scraped as of right now are fics in unrevealed collections, which even logged-in users can't view without permission from the owner.
"My work wasn't a fic. It was an image/video/podfic.": You're safe! All the scrape got was stuff like the tags you used and your title and author name. The work content itself is a blank gap based on the samples I've checked.
"It's slow.": Unfortunately, a 13 million row data dashboard is going to be on the slow side. I think I've done everything I can to speed it up, but it may still take up to 10 minutes to load if you use the second link. It's faster if you can use desktop or the first link, but it should work on your phone too.
"My fic isn't there.": The cut-off date is around February 15th, 2025 for oneshots, but chapters posted up to March 21st, 2025 have been found in the data so far. I had to remove a few works from the dataset because the data was all skrungly and breaking my tool. (The few fics I removed were NOT in English.) Otherwise, from what I can tell so far, the scraper's code just... wasn't very good, so most likely, your fic was missed by random chance.
Thanks to everyone who helped with the cost to host the tool! I appreciate you so so so much. As of this edit, I've received more donations than what I paid to make this tool so you do NOT need to keep sending money. (But I super appreciate everyone who did help fund this! I just wanna make sure we all know it's all paid for now, so if you send any more that's just going to my savings to fix the electrical problems with my house. I don't have any more costs to support for this project right now.)
(Made some edits to the post on 27-May-2025 to update information!)
Darcy Lewis, slightly bratty daughter of billionaire Tony Stark, gets assigned chronic bachelor Clint Barton as protection after someone threatens the Starks’ lives.
Always the wild child, Darcy isn’t about to make her bodyguard’s job any easier.
And Clint? He’s too stubborn to give up, no matter how hard she pushes.
Rating: T
Tags: Canon divergent, Iron Man 2, Bodyguard AU, angst, fluff, bickering, slow burn, enemies to lovers
Relationship: Clint Barton/Darcy Lewis
Word count: 2,863
Link: Chapter seven of ??? Or start at the beginning
casually catching up on my ao3 comment inbox since I finally posted an update, so if I reply to your comment from 3 years ago, please note that was just yesterday to me.
Darcy Lewis didn’t know what the end of the world was going to look like, but she hadn’t expected this. All Natasha Romanoff knew was that Darcy Lewis was the only SHIELD-vetted scientist who’d picked up her call after half the world turned into dust. That was a good enough reason to want to protect her… right? — A ‘choose your own ending’ Post-Snap snapshot.
Rating: T
Tags: Canon compliant post-Infinity War (angsty ending is Endgame compliant), Pre-relationship, Developing relationship, Slow burn, Feelings realization, Protective Natasha Romanoff, Doctor Darcy Lewis, Angst, Hurt/comfort
Relationship: Natasha Romanoff/Darcy Lewis
Chapter word count:
Link: Chapter six of six/seven Or start at the beginning