Archive of Our Own

Are you a paralegal interested in helping the Legal Committee carry out its legal advocacy mission? Do you have legal experience, preferably trademark-specific, especially in the EU and US? Would you like to assist AO3 users by resolving complaints? The Organization for Transformative Works is recruiting!

We're excited to announce the opening of applications for:

• Legal Committee Paralegal - closing 22 April 2026 at 23:59 UTC
• Legal Committee Trademark Specialist - closing 22 April 2026 at 23:59 UTC
• Policy & Abuse Volunteer - closing 22 April 2026 at 23:59 UTC

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don't see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist our email address in your e-mail client. If you do not receive the auto-reply within 24 hours, please check your spam filters and then contact us.

If you have questions regarding volunteering for the OTW, check out our Volunteering FAQ.

Legal Committee Paralegal

The Legal committee is responsible for carrying out the OTW's legal advocacy mission and providing internal legal support and guidance to the OTW as an organization. We provide confidential legal advice to every part of the OTW organization, respond to fans' requests for general assistance and information, and create educational materials. We also file briefs in lawsuits and advise lawmakers about how to take fans’ needs and interests into account in creating and interpreting the law. And we're looking for a few new members!

We are looking for a paralegal to assist with managing standard questions, tracking issues, and ensuring we adhere to deadlines. If this describes you, please click through to the application form. Please note that you must be over 18 years of age to apply for this role. All applicants will be asked to upload their resume.

Applications are due 22 April 2026

Apply to be a Legal Committee Paralegal at the volunteering page! If you have further questions, please contact us.

Legal Committee Trademark Specialist

The Legal committee is responsible for carrying out the OTW’s legal advocacy mission and providing internal legal support and guidance to the OTW as an organization.

We are currently looking for a Trademark Specialist, who will be responsible for trademark registration applications and maintenance and trademark enforcement, generally dealing with platforms and attempts to monetize AO3 via apps or merchandise.

If you have legal experience, preferably trademark-specific, especially in the EU or US, and can effectively communicate legal issues to non lawyers, click through for the job description and to apply. Please note that you must be over 18 years of age to apply for this role. All applicants will be asked to upload their resume.

Applications are due 22 April 2026

Apply to be a Legal Committee Trademark Specialist at the volunteering page! If you have further questions, please contact us.

Policy & Abuse Volunteer

The Policy & Abuse committee (PAC) is responsible for addressing questions and concerns about potential violations of the AO3 Terms of Service. We determine whether reports are about legitimate violations of the Terms of Service, and what to do about them if they are. PAC volunteers correspond directly with AO3 users and collaborate on projects both within PAC and with other OTW committees.

Our main goals as a committee are:

• to adhere to the AO3 Terms of Service
• to make our reasoning and processes as clear and transparent as possible
• to handle all user reports consistently, no matter which volunteer is doing the work
• to keep every case we work on completely confidential

We are seeking people who can:

• Commit to working on cases regularly
• Be patient with rephrasing explanations
• Ask for help when needed
• Collaborate both inside the team and with other committees
• Act in accordance with established rules, policies, and procedures
• Treat confidentiality and user privacy as a priority

You must be 18+ in order to apply for this role. While English proficiency is required, we welcome applicants who are fluent in other languages, especially Brazilian Portuguese (Português brasileiro), Chinese (中文), French (Français), Indonesian (Bahasa Indonesia), Japanese (日本語), Polish (Polski), Russian (Русский), Spanish (Español), Turkish (Türkçe), or Ukrainian (Українська).

Applications are due 22 April 2026

Apply to be a Policy & Abuse Volunteer at the volunteering page! If you have further questions, please contact us.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

Our February releases included new admin tools for our Support and Policy & Abuse teams, as well as a bunch of challenge and collection fixes and a host of small updates and improvements. We also upgraded to Rails 8 and Elasticsearch 9!

Many thanks to first-time contributor Shel!

Credits

• Coders: Bilka, Brian Austin, Danaël/Rever, FlyingFalcon, Hunter Ada Smith, james_, Jennifer He (DisappearEagle 无鸢), marcus8448, Richard Hajek, Scott, slavalamp, varram
• Code reviewers: Bilka, Brian Austin, james_, sarken
• Testers: ana, Bilka, choux, hvalrann, Lute, mumble, ömer faruk, pk2317, therealmorticia, Yuca

Details

0.9.457

On February 2, we deployed a major Rails update.

• [AO3-7231] - Updated the framework the Archive runs on to Rails 8.0.

0.9.458

On February 9, we introduced a way for our Support team to add information to the support form without disabling the form, and deployed a bunch of miscellaneous fixes and improvements.

• [AO3-6983] - It was already possible for our Support team to temporarily close the support form and replace it with a message to users, e.g. about a known site-wide issue the development team was already working to solve. Additionally, they can now add a temporary message to the form without disabling the form entirely.
• [AO3-3245] - Trying to open the posting form to add a work to a closed collection (only possible by manually typing in the appropriate URL) would lead to an error message that looked like the form had already been submitted. The URL now redirects to the collection with a more helpful error message.
• [AO3-7246] - We added a "Parent" link to comments, so you can quickly jump to the specific comment that is being replied to.
• [AO3-7260] - Passwords must now be between 8 and 72 characters long. (The previous minimum was 6 characters.)
• [AO3-7274] - Comment previews for Policy & Abuse admins were previously truncated after the first 100 characters, and admins had to click on the preview to access the full comment. Now the preview includes the first 1,000 characters, which is much more useful.
• [AO3-7279] - When a collection is set to "revealed" or "non-anonymous", the collection is placed in a queue that runs when resources are available to change the status of potentially thousands of works. This means the moderator often has enough time to quickly change the setting back if a checkbox was ticked in error. We now make sure the process really only runs if the revealed or non-anonymous option is still wanted when the servers are ready to work through the queue.
• [AO3-7240] - In our ongoing internationalization efforts, we prepared the text in the help pop-ups for Rating, Warning, and Fandom tags for translation.
• [AO3-7047], [AO3-7281], [AO3-7287], [AO3-7288] - Code clean-up, database performance improvements, and system updates.

0.9.459

Our February 17 deploy included various small fixes and updates.

• [AO3-4031] - Draft works include a message at the top, warning the creator that unposted drafts will be automatically deleted after a certain time. If you had a draft with multiple chapters, this message would not be displayed! Now it appears everywhere it should.
• [AO3-5367] - If someone bookmarked a mystery work, i.e. a work in an unrevealed collection, the bookmark would show up in bookmark searches that matched elements of the mystery work. Since we don't want information about a mystery work to be guessable in this manner, we now make sure searching bookmarks doesn't give away information about unrevealed works.
• [AO3-5870] - A blockquote in a comment would awkwardly overlap with the commenter's user icon, so we've taken steps to make sure it stays within its own boundaries.
• [AO3-5963] - You can't request an invite with an email address that is already used by an existing account. If an existing account updates their email address to one that's waiting in the request queue, we now make sure that request is deleted.
• [AO3-7206] - Downloads of a work in progress with only one chapter posted were missing that chapter's title, summary, and notes, displaying only the information entered for the work as a whole. Now all data is present and accounted for!
• [AO3-7254] - We've added a limit to how many times a specific comment can be reported to the Policy & Abuse team for review.
• [AO3-7263] - Under certain circumstances, an admin would get a 500 error trying to access a user's preferences page. Now they can access it even under those circumstances.
• [AO3-7289] - When a user tried to create a skin with faulty CSS, the parser would just throw an error 500 instead of telling the user which part was stressing it out. It now helpfully points to the problem in the CSS code.
• [AO3-7210] - The help pop-up that provides information about creating skins is now prepared for translation.
• [AO3-6853], [AO3-7048] - Code clean-up and database performance improvements.

0.9.460

A bunch of gem updates went out on February 21.

• [AO3-7036] - When reviewing comments held in moderation, to either approve or reject, there was no "Thread" link to get the URL for a specific comment, e.g. to report it to the Policy & Abuse team. Now there is!
• [AO3-7278] - AO3 admins from the Open Doors team can now track invitations in the admin area.
• [AO3-7236] - Prepared the text in a couple of skins-related help pop-ups for translation.
• [AO3-7265], [AO3-7297], [AO3-7298], [AO3-7299], [AO3-7300] - Code clean-up and database performance improvements.

0.9.461

On February 28, we upgraded to Elasticsearch 9.

• [AO3-7282] - Upgraded the search engine that powers, among other things, work searches and filtering from version 8 to 9.

I. AO3 IS EXITING OPEN BETA

In early April, we announced that AO3 is exiting open beta!

AO3 has grown and changed a lot since open beta launched in 2009! We've gone from 347 users to over 10 million and from 6,598 works to over 17 million. We've also introduced many features in that time, including the tag system and tag wrangling, additional privacy settings that allow creators to restrict their works or comments to logged-in users, downloads for offline access to fanworks, and more.

Since AO3's software has been stable for a long time, this change is mostly cosmetic and doesn't indicate everything is finalized or perfectly working. Our volunteer coders and community contributors will still be adding to and improving post-beta AO3 every day.

For more information on AO3 exiting open beta, check out the announcement for details.

II. ELSEWHERE AT AO3

In March, we celebrated AO3 reaching 17 million works! \o/

Beyond exiting beta, Accessibility, Design & Technology also performed two important upgrades in March: updating Elasticsearch to version 9 and Ruby on Rails to version 8.1. With these two upgrades, AO3 is on the latest version for two of its most important pieces of software. They also published January’s release notes.

Systems published a postmortem on early March's AO3 downtime.

Open Doors announced the import of SlasHeaven, a Spanish-language slash fanfiction and fanart archive, as part of their Online Archive Rescue Project.

In February, Policy & Abuse (PAC) received 5,674 tickets, which is over 2,000 fewer tickets than the previous month and marks the first decrease in PAC's backlog since 2024. PAC also coordinated with Communications on a news post describing various spambots seen on AO3 and how we're combating them. Also in February, Support received 3,031 tickets, and User Response Translation completed 42 requests from PAC and Support.

Tag Wrangling announced 31 new "No Fandom" canonical tags in their March round-up. On the @ao3org Tumblr, they announced changes to Critical Role fandom tags, creating an overarching fandom metatag for the Exandrian Universe and having specific campaigns or other media split into subtags. They hope these changes will help users better tag and filter for the works they want to see.

In February, Tag Wrangling wrangled over 543,000 tags or approximately 1,200 tags per wrangling volunteer.

III. ELSEWHERE AT THE OTW

Communications has updated the OTW News by Email service! You can now subscribe specifically to recruitment posts. If you're already subscribed to OTW News by Email and would like to change what emails you receive, please contact Communications via their contact form.

In March, Fanlore ran a monthly editing challenge inviting users to ​​archive external links on a page.

Legal answered a number of questions about pending and newly enacted laws around the world, as well as dealing with internal requests from OTW committees.

TWC released No. 47 of Transformative Works and Cultures, a special issue on Gaming Fandom edited by coeditors Hayley McCullough and Ashley P. Jones.

IV. GOVERNANCE

Board and Board Assistants Team continued work on ongoing and newer projects, including making progress on the OTW website project with Communications, supporting Accessibility, Design & Technology with their documentation, and supporting Finance with streamlining messaging policies. They also began preparing for the next public Board meeting scheduled for April 18.

In March, Development & Membership caught up on their recurring donation gifts and put in more regular procedures for them going forward. In conjunction with Communications and Translation, they're now preparing for April's Membership Drive by getting graphics and new gifts ready.

V. OUR VOLUNTEERS

Volunteers & Recruiting conducted recruitment for three committees this month: Communications (News Post Moderation), Translation, and User Response Translation.

From February 21 to March 22, Volunteers & Recruiting received 160 new requests and completed 159, leaving them with 66 open requests (including induction and removal tasks listed below). As of March 22, 2026, the OTW has 992 volunteers. \o/ Recent personnel movements are listed below.

New Committee Chairs/Leads: Becca Bun and Jules Moon (Fanlore), Rebecca Tushnet and Stacey Lantagne (Legal)
New Communications Volunteers: LinnK, Jahnavi, and 3 other Social Media Moderators
New Fanlore Volunteers: 1 Policy & Admin and 1 Social Media & Outreach
New Open Doors Volunteers: Andrea T and 4 other Import Assistants; Kathy and 1 other Technical Volunteer; adyn, Seren, Claire M, and 2 other Administrative Volunteers; and 1 Liaison
New Organizational Culture Roadmap Workgroup Volunteers: 1 Volunteer
New TWC Volunteers: 1 Symposium Editor
New Volunteers & Recruiting Volunteers: miffmiff, PippaLane, and 2 other volunteers

Departing Committee Chairs/Leads: 1 Open Doors Chair, 2 Fanlore Chairs, and 1 Internal Complaint and Conflict Resolution Lead
Departing AD&T Volunteers: 1 Senior Volunteer and 1 Liaison
Departing Fanlore Volunteers: 1 Social Media & Outreach
Departing Finance Volunteers: 1 Bookkeeper
Departing Open Doors Volunteers: 1 Technical Volunteer
Departing Policy & Abuse Volunteers: 1 Volunteer
Departing Tag Wrangling Volunteers: 4 Tag Wranglers and Soppon (Tag Wrangling Supervisor)
Departing Translation Volunteers: Ito, Polyxeni Foutsitsi, and 3 other Translators; 1 Chair Trainee; and 1 Volunteer Manager
Departing User Response Translation Volunteers: 1 Translator
Departing Volunteers & Recruiting Volunteers: 2 Volunteers

For more information about our committees and their regular activities, you can refer to the committee pages on our website.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

NOTE: This is a living document and will be updated in response to changes and new types of spam as observed by OTW volunteers.

LAST UPDATED: March 30, 2026

As AO3 continues to grow, there has been an increase in the amount and variety of spambots that attempt to harass or scam users. Spambots may try to imitate other users and even AO3/OTW volunteers to appear more realistic. This post shares a brief update on how we're working to combat this issue, what types of spam we've seen, and what you can do if you encounter spam comments on AO3.

What We're Doing

Protecting our users from scammers and bots targeting AO3 is important to us, and we are actively working to combat spam on the site in a variety of ways—both visible and not. We will not share a detailed list of every change we've made (so as to not provide spammers with information about how to circumvent these measures), but some examples include introducing comment rate limits for logged-in users, changing the default comment setting on new works to "Registered users only", spam checking comments and comment edits from new users, and making a variety of improvements to the admin tools used by our Policy & Abuse volunteers to handle reports and remove spam comments.

We continue to consider and undertake additional technical changes to help prevent and improve our response to spambots. However, it is important to us that any anti-spam measures we implement do not substantially harm users who are browsing or attempting to comment normally. Many more aggressive anti-spam measures would make AO3 less accessible, particularly for users using assistive devices such as screen readers.

In addition to taking technical steps to help address the issues, we continue to post updates about spambots and other important changes to AO3 on our Tumblr, Bluesky, and Twitter/X. We encourage you to follow us on these platforms to stay informed about what's going on.

Types of Spam Comments

Below is a list of different types of spam comments that have been posted on AO3 over the last year. We intend to maintain this list and add new types of spam to it as they are identified; however, this list may not include every type of spam comment that could possibly be received. We encourage you to remain vigilant and follow internet safety best practices.

If you're not sure if something is a spam comment, you're welcome to contact Policy & Abuse for assistance. Before doing so, we encourage you to click through the links below to learn more about each type of comment and use your best judgement to determine if a comment appears to be genuine or could be a scam.

• Art Commission Spam: These comments come from both guests and registered accounts who pretend to be artists who want to make comics or illustrations for your fanfic. They may ask questions or praise your work to try and get you to reply to them, before convincing you to contact them off AO3 (often via Discord). They will try to scam you into paying for their art, which is either AI-generated or does not exist at all. (First reported August 2024, news post published December 2024)
• Deprecated Fandoms Spam: These guest comments claim that AO3 will be "deleting works to conserve server space". There is no such thing as a deprecated fandom and there is no limit on the number of fanworks that can be posted to a specific tag. (First reported May 2025, Tumblr announcement May 2025)
• AI Use Accusation Spam: These guest comments will accuse you of using AI in your work. They may mention a particular AI generator or AI detection service, or claim that they "saw you remove the AI prompts from your work". (First reported April 2023, Tumblr announcement November 2025)
• Harassing Spam: These guest comments will accuse you or another user of promoting discriminatory beliefs, deceiving fans, or similar behaviors. They often suggest that you "consider adding more diverse characters" to "repair the trust you've lost with your audience". (First reported October 2025, Tumblr announcement November 2025)
• Praise and Unsolicited Suggestions Spam: These guest comments will compliment your writing but then offer ridiculous suggestions for how to make your work better. Similar to the harassing spam, they may ask you to add a minority character to your work or threaten to publicly expose you if you don't do what they want. (First reported October 2025)
• Special Character/Keysmash Spam: These comments are usually long and consist entirely of emojis or nonsense, keysmash-style sequences of characters from a variety of non-Latin scripts or languages (e.g., Chinese, Cyrillic, Thai, etc). (First reported November 2025)
• Reporting To Authorities Spam: These guest comments threaten to report you or your work to the authorities or your employers. They also may allege security concerns like your email being compromised or spyware on your computer. (First reported December 2025, Tumblr announcement December 2025)
• Disparaging Spam: These guest comments insult you or your writing, claiming that you "wasted your talents" or "have no life". They may also threaten suicide or tell you to delete your work. (First reported December 2025)
• PowerShell Spam: These comments present you with a piece of code to enter into your computer's terminal/command line. While they claim that the purpose of the code is for your protection or security, the code in these comments would actually delete all documents from your hard drive. (First reported January 2026)
• Doxxing Threat Spam: These guest comments claim that they know where you live, have seen you in person, and/or threaten to meet you face-to-face. They often say that they have or will post your personal information (name, address, etc.) online or that they are stalking you in real life (e.g. "left a gift in a briefcase near your house"). (First reported January 2026, Tumblr announcement January 2026)
• Spam Impersonating OTW Volunteers: These guest comments claim to be AO3/OTW volunteers and say that there has been a data breach or that AO3 and other sites (such as Reddit) have been sending out fraudulent password reset emails. (First reported January 2026, Tumblr announcement February 2026)
• Downtime Spam: These guest comments claim that the March 2026 AO3 downtime was caused by hackers and AO3 has a virus that will destroy your device, and encourage reformatting your device or deleting all your works. (First reported March 2026)

None of the accusations these spam comments make are true. The bots are merely spamming false accusations in order to alarm or harass AO3 users. It is generally safe to ignore these comments once you've removed and/or reported them as outlined below.

What You Can Do

Do not engage in conversation with spam commenters. Do not provide your email or social media contact information to a commenter who asks for it. Scammers try to get you to talk to them privately, because it is often easier to deceive or manipulate people in a one-on-one conversation.

Do not click on any links, run any code commands on your computer, or search out and harass any users named in these comments. Scammers often copy the username of a real AO3 user on their guest comments to make them look more real. Pay attention to the "(Guest)" indicator which will appear next to the name of anyone who comments while not logged in.

For spam comments on your own work, the best way to handle them depends on whether they are from registered accounts or guests. Refer to the instructions below on how to handle Spam from a Guest User or Spam from a Registered Account.

If you see a spambot comment on someone else's work, you can report the comment as spam to Policy & Abuse (even if it's a guest comment) as you would a comment on your own work. You can also let the creator know the comment is from a bot and that they should mark it as spam.

Please don't report comments that have already been deleted. As part of handling a report about spam comments (whether from guests or registered accounts), we will remove other comments made by the same bot. If the comments have been deleted, the bot has already been actioned and no further reports are needed.

Spam from a Guest User

If you receive a spambot comment on your work which is posted by a guest:

1. Go directly to the comment on your work, either by clicking on the link in your email or in your AO3 inbox.
   
   Note: The "Spam" button only appears when viewing a guest comment directly on your work. This is because the AO3 comment inbox is merely a copy of the work's comments—deleting a comment from your AO3 inbox does not delete the comment from the work itself.
2. Click on the "Spam" button to mark the guest comment as spam, remove it from your work, and help train our automated spam-checker to reject similar spam comments in the future.
   
   Note: Marking guest comments as spam does not submit a report to the Policy & Abuse committee, but unless you are receiving dozens of guest spam comments in a short time period, there is no need to submit a separate report.

To prevent future guest spam comments, you may also want to consider disabling anonymous commenting or restricting your work to registered users only.

If you are reporting multiple guest comments, please submit only one report and include all comment links in your report description. (You can get the direct link to a specific comment by selecting the "Thread" button on the comment and copying the URL of that page.)

If you are receiving dozens of guest spam comments in a short time period, we recommend turning on comment moderation and providing us with a link to the unreviewed comments section of the affected work(s) instead of reporting the comments individually.

Spam from a Registered Account

If the spam comment is posted by a registered AO3 account:

1. Select the "Thread" button on the spam comment. This will take you to the specific comment page.
2. Scroll to the bottom of the page and select Policy Questions & Abuse Reports.
3. In the "Brief summary of Terms of Service violation" field, enter "Spambot".
4. In the "Description of the content you are reporting" field, enter "This is a spambot, their username is USERNAME." (replace USERNAME with the account's actual username)
5. Optionally, you may also choose to block or mute the account.

Please don't report multiple spam accounts in one report. Each account is actioned separately and listing more than one account per report delays our response to you.

Closing

In general, please follow internet safety best practices and be cautious of unsolicited advertisements or harassing comments on your work. For some advice on other ways you can protect your AO3 account, take a look at this internet security guidance from our Policy & Abuse volunteers.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

We're excited to announce that we're exiting open beta! We've come a long way from when we announced and launched AO3 open beta in 2009.

At launch, there were just 347 AO3 accounts and 6,598 works. While we started growing very quickly, we were originally much more limited in what we could do.

Did you know that AO3 invitations were originally sent out manually by individual AO3 volunteers? During our initial rapid growth, we were still only sending out about 1200 invitations per day, and eventually tapered off to 50 per day. Today, we send around 6,000 invitations every 12 hours. Our old news posts also include fun stats about what AO3's user base and works looked like in 2009, which you can compare to the stats post we recently shared in January to see how far we've come.

What's Changed Since Then

Since 2009, AO3 has grown and changed a lot. We've introduced many features over the years through the efforts of our volunteers and coding contributors, as well as the contractors we've been able to hire thanks to generous donations from our users. While there are a lot of additions we're proud of, some of our favorites include:

• Our tag system and tag wrangling
• Orphaning, which allows creators to disconnect works from their account or delete their account while leaving their works online
• Downloads that provide offline access to fanworks in AZW3, EPUB, MOBI, PDF, or HTML format
• Privacy settings for works that let creators restrict access to registered AO3 users and control who can leave comments
• Chapter-by-Chapter and Entire Work modes for multi-chapter works

Looking at where we are now in 2026, we recently celebrated 10 million registered users and 17 million fanworks! We're grateful for all the fans that have accompanied us all this time—all of our accomplishments are thanks to you!

Some recent improvements we've made include adding new options to bookmark and collections filtering and updating all of the buttons at the bottom of the forms for posting, previewing, or editing a work to make them more user-friendly.

What's Next for AO3 and How You Can Help

As the AO3 software has been stable for a long time, the change is mostly cosmetic and does not indicate that everything is finalized or perfectly working. Exiting beta doesn't mean we'll stop continuing to improve AO3—our volunteer coders and community contributors will still be working to add to and improve AO3 every day. For one, it’s likely you’ll continue to see references to us being in beta for a while as we update our documentation.

If you'd like to see what issues are being worked on, check out our project on Jira. This is a public list of all the bugs and features that are on the to-do list for our coders.

If you're familiar with coding and would like to contribute your time, we welcome contributions from anyone! Take a look at our Contributing Guidelines and other documentation on GitHub. All contributors are credited in our release notes.

If you're interested in helping AO3 but don't have any coding ability, consider volunteering for one of the other teams that work on AO3 or contributing to AO3 in some other way.

If you have a feature request or bug to report, please contact AO3 Support. Support handles communication between users and the various teams involved with AO3. The Support team helps to resolve technical problems experienced by users and passes on users' feedback to the relevant committees.

For all the fans who were part of our beta journey from 2009 until today, here's a badge for you, as a small thank you for your support! You're welcome to display this badge on social media, your AO3 profile, or any other website of your choosing. For example, if you want to display the badge in your AO3 profile, add this HTML tag: <img src="https://media.archiveofourown.org/news/ao3-updates/2026-04-leaving-beta/badge-english.png" alt="Circular badge with the words 'I was here for beta' with an AO3 logo"> into the "About Me" section in your profile. If you’d like more information on how to embed images, refer to our Posting and Editing FAQ or our guide on how to format HTML on AO3!

We are deeply appreciative and grateful for all the support we've gotten from fans since we were founded, so let us be the first to say: Welcome to Post-Beta AO3!

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

Omegas are the glue that holds us all together, providing the essential social lubricant needed for our society to function—and yet they are often maligned and treated as lesser-than. This April, we are changing part of our logo to highlight omegas as part of our commitment to the inclusion and wellbeing of our omega volunteers and users.

We believe that visibility is important. As we post this, we're home to over 2,900 omega characters and counting. AO3 is one of the only spaces online where omegas are in the limelight, and we are proud to offer this safe space.

Volunteers at the OTW are never required to state their designations, though many choose to do so. Regardless of their decision or subgender, we aim to support our volunteers to the best of our ability; our policies on short breaks and hiatuses are written to help volunteers maintain their privacy and focus on their needs. Here are some words from our volunteers on the subject:

• "As someone in a leadership position at the OTW I have always felt supported by my fellow volunteers in all matters relating to my designation. Going on break regularly is a non-issue because my alpha chair assistants hold down the nest without taking advantage of my absence, and the only comments I get from my committee are people asking whether I've had enough rest when I return." — Choux, Communications Chair (Ω)
• "Everyone gets to shine as a volunteer here, because our diverse leadership brings invaluable insight. I’m proud to volunteer for the OTW, this being one of many reasons." — orphan_account, Support Volunteer (β)
• "Fandom unites us in a way that transcends bounds. I’m incredibly proud to be a part of an organization that champions its volunteers regardless of subgender, with no tolerance for alpha posturing." — Tal, Tag Wrangling Supervisor (α)
• "As an older omega, it is a rare thing to find a volunteer community so consistently supportive. Three years of service, and the whole OTW has always had my back." — Remi, OTW Tumblr Mod (Ω)

As part of this commitment, our Tag Wrangling Committee recently canonized several tags to better represent experiences had by people of all subgenders! Here are some our omega volunteers have chosen to highlight:

• Omegaverse Bitching | Turning into an Omega
  • Consensual Omegaverse Bitching | Turning into an Omega
  • Omegaverse Alpha Bitching | Alpha Turning into an Omega
  • Omegaverse Beta Bitching | Beta Turning into an Omega
• Omegaverse Studding | Turning into an Alpha
• Female Omegaverse Alpha Characters
• Male Omegaverse Omega Characters
• Heat Suppressants
• Scent Blockers

Finally, a word from our Board President:

Dear gentlebeings at AO3, on this serendipitous day of 2026, the Board of Directors are pleased to announce that:

All our volunteers have enjoyed perfect health of body, and tranquillity of mind; we don't feel the treachery or insecurity of omegas in heat, nor the possessiveness or aggression of alphas in ruts. We have no occasion of bribing, lubricating, or alphasplaining, to procure the favour of any great omega, or of their beta and alpha supporters. We don't need protection against dishonesty or oppression: there is neither insurance company to destroy our health, nor politician to ruin our equal rights movement; no reporter to watch our words and actions, or forge accusations against us for our designations.

Gracefully yours,

Anh Pham
President of the OTW Board of Directors (Ω)

Happy April Fools! On this day and every other day of the year, AO3 is proud to host all your efforts towards making omegas just that little bit more real! To celebrate, we've changed our site header superscript to "omega" instead of the usual "beta". If you’d like to learn more, you can visit the Fanlore article on the topic.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.

ETA: We’re happy to announce that we’ve exited Open Beta! This is not part of this April Fools’ post and is a real, separate announcement.

SlasHeaven, a Spanish-language slash fanfiction and fanart archive, is being imported to the Archive of Our Own (AO3).

In this post:

• A bit of background explanation
• What this means for creators who had work(s) on SlasHeaven
• And what to do if you still have questions

Background explanation

SlasHeaven was founded on May 19, 2004, by the programmer and main promoter of the archive, Ayesha, and two collaborators, Maryam and Aura. This began after a massive deletion of fanfiction slash written in Spanish at a popular platform and with the conviction that we needed a place where we could publish in our language without restrictions. And so this website was born, a place dedicated exclusively to slash fanfiction written in Spanish.

SlasHeaven’s archivist made the decision to move the archive to AO3 after web configuration issues made it untenable to continue maintaining the archive themselves.

The purpose of the Open Doors Committee’s Online Archive Rescue Project is to assist moderators of archives to incorporate the fanworks from those archives into the Archive of Our Own. Open Doors works with moderators to import their archives when the moderators lack the funds, time, or other resources to continue to maintain their archives independently. It is extremely important to Open Doors that we work in collaboration with moderators who want to import their archives and that we fully credit creators, giving them as much control as possible over their fanworks. Open Doors will be working with Maryam and Aura to import SlasHeaven into a separate, searchable collection on the Archive of Our Own. As part of preserving the archive in its entirety, any fanart currently hosted by SlasHeaven will be hosted on the OTW's servers, and embedded in their own AO3 work pages.

We will begin importing works from SlasHeaven to AO3 after March. However, the import may not take place for several months or even years, depending on the size and complexity of the archive. Creators are always welcome to import their own works and add them to the collection in the meantime.

What does this mean for creators who had work(s) on SlasHeaven?

We will send an import notification to the email address we have for each creator. We'll do our best to check for an existing copy of any works before importing. If we find a copy already on AO3, we will add it to the collection instead of importing it. All works archived on behalf of a creator will include their name in the byline or the summary of the work.

All imported works will be set to be viewable only by logged-in AO3 users. Once you claim your works, you can make them publicly-viewable if you choose. After 30 days, all unclaimed imported works will be made visible to all visitors.

Please contact Open Doors with your SlasHeaven pseud(s) and email address(es), if:

1. You'd like us to import your works, but you need the notification sent to a different email address than you used on the original archive.
2. You already have an AO3 account and have imported your works already yourself.
3. You’d like to import your works yourself (including if you don’t have an AO3 account yet).
4. You would NOT like your works moved to AO3, or would NOT like your works added to the archive collection.
5. You are happy for us to preserve your works on AO3, but would like us to remove your name.
6. You have any other questions we can help you with.

Please include the name of the archive in the subject heading of your email. If you no longer have access to the email account associated with your SlasHeaven account, please contact Open Doors and we'll help you out. (If you've posted the works elsewhere, or have an easy way to verify that they're yours, that's great; if not, we will work with the SlasHeaven mods to confirm your claims.)

Please see the Open Doors Website for instructions on:

• importing your works to AO3
• adding your works to the new collection SlasHeaven

If you still have questions...

If you have further questions, visit the Open Doors FAQ, or contact the Open Doors committee.

We'd also love it if fans could help us preserve the story of SlasHeaven on Fanlore. If you're new to wiki editing, no worries! Check out the new visitor portal, or ask the Fanlore Gardeners for tips.

We're excited to be able to help preserve SlasHeaven!

- The Open Doors team and Maryam and Aura

Commenting on this post will be disabled in 14 days, on April 8, 2026. If you have any questions, concerns, or comments regarding this import after that date, please contact Open Doors.

AO3 Tag Wranglers continue to test processes for wrangling canonical additional tags (tags that appear in the auto-complete) which don't belong to any particular fandom (also known as "No Fandom" tags). This post overviews some of these upcoming changes.

In this round of updates, we continued to streamline creating new canonical tags, prioritizing more straightforward updates which would have less discussion compared to renaming current canonical tags or creating new canonical tags which touch on more complex topics. This method also reviews new tags on a regular basis, so check back on AO3 News for periodic "No Fandom" tag announcements.

None of these updates change the tags users have added to works. If a user-created tag is considered to have the same meaning as a new canonical, it will be made a synonym of one of these newly created canonical tags, and works with that user-created tag will appear when the canonical tag is selected.

In short, these changes only affect which tags appear in AO3's auto-complete and filters. You can and should continue to tag your works however you prefer.

New Canonicals

The following concepts have been made new canonical tags:

• All Characters Are Of Legal Age
• Black Cat/Golden Retriever Personality Dynamics
• Cannibalism as a Metaphor for Love
• Canon-Typical Cannibalism
• Characters in Love
• Classism
• Cock Stepping
• Crotch Stepping
• Crying After Sex
• Dramatic Irony
• Established Friendship
• Fealty
• Fealty Kink
• Loyalty Kink
• Pain Kink
• Thigh Kink
• Frotting | Rubbing Penises Together
• Girls in Love
• Grumpy/Sunshine Relationships
• Happy Tears
• Mating Press Position
• Moodboards
• Muscular Female Characters
• Muscular Male Characters
• Consensual Omegaverse Bitching | Turning into an Omega
• Omegaverse Bitching | Turning into an Omega
• Omegaverse Studding | Turning into an Alpha
• Omegaverse Alpha Bitching | Alpha Turning into an Omega
• Omegaverse Beta Bitching | Beta Turning into an Omega
• Relationship Wingmanning
• Consensual Spanking

In Conclusion

While some of these tags may be tags and concepts you're intimately familiar with, others may be concepts you've never heard of before. Fortunately, our fellow OTW volunteers at Fanlore may be able to help! As you may have seen in the comments sections of previous posts, Fanlore is a fantastic resource for learning more about these common fandom concepts, and about the history and lore of fandom in general. For the curious, here's a quick look at a few articles about concepts related to this month's new canonical tags:

• Aesthetic Edit
• Alpha/Beta/Omega
• Cannibalism
• Domestic Discipline
• Friendship
• Grumpy Character and the Sunshine Character
• Loyalty Kink
• Sex Position

While we won't be announcing every change we make to No Fandom canonical tags, you can expect similar updates in the future about tags we believe will most affect users. If you're interested in the changes we'll be making, you can continue to check AO3 News or follow us on Bluesky @wranglers.archiveofourown.org or Tumblr @ao3org for future announcements.

You can also read previous updates on "No Fandom" tags as well as other wrangling updates, linked below:

• Past "No Fandom" Additional Tags Updates and 5 Things Said by Wrangling Volunteers
• Past Fandom-Specific and "No Fandom" Tag Wrangling Change Posts

For more information about AO3's tag system, check out our Tags FAQ.

In addition to providing technical help, AO3 Support also handles requests related to how tags are sorted and connected.​ If you have questions about specific tags, which were first used over a month ago and are unrelated to any of the new canonical tags listed above, please contact Support instead of leaving a comment on this post.

Please keep in mind that discussions about what tags to canonize and what format they should take are ongoing. As a result, not all related concepts will be canonized at the same time. This does not mean that related or similar concepts will not be canonized in the future or that we have chosen to canonize one specific concept in lieu of another, simply that we likely either haven’t gotten to that related concept yet or that it needs further discussion and will take a bit longer for us to canonize it as a result. We appreciate your patience and understanding.

Lastly, we're still working on implementing changes and connecting relevant user-created tags to these new canonicals, so it’ll be some time before these updates are complete. If you have questions about specific tags which should be connected to these new canonicals, please refrain from contacting Support about them until at least three months from now to give us adequate time to do so.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, OTW Legal Advocacy, and Transformative Works and Cultures. We are a fan-run, donor-supported organization staffed by volunteers. Find out more about us on our website.