What Are Orphaned Works on AO3, and Why Would an Author Give Up Their Byline?

When reading on AO3, you may come across works whose author is listed as orphan_account, or as a pseud followed by (orphan_account). These works are usually called orphaned works.

The term can sound a little bleak, but it does not mean AO3 has abandoned the work. It means the author has chosen to remove the work from their own account while allowing it to remain on AO3.

What are orphaned works?

AO3’s Orphaning FAQ explains orphaning in a fairly direct way: if you no longer want a work to be associated with your account, but you do not want to delete it from AO3, you can orphan it. The work is then permanently transferred to AO3’s special orphan_account.¹

In other words, orphaning changes the relationship between the work and the author’s account. It is not mainly about whether the work continues to exist.

Deleting a work removes it from AO3.
Posting anonymously hides the author’s identity in public, but the original account still controls the work.
Orphaning keeps the work on AO3 while separating it from the author’s account.

All three options can involve an author not wanting their name attached to a work, but the consequences are very different. Orphaning is the one that is permanent and irreversible.

What is orphan_account?

orphan_account is a special AO3 account used for orphaned works. AO3 requires every work to be connected to a creator account; when an author orphans a work, that work is moved under the AO3-controlled orphan_account.²

When orphaning a work, the author can choose whether to keep the original pseud attached.

If the pseud is removed, the work will display as being by orphan_account. If the pseud is kept, the byline may look something like some name (orphan_account). That pseud no longer links back to the original author’s AO3 account, but if the name itself is distinctive, people who already know the fandom may still be able to guess who wrote it. AO3’s Chinese FAQ also points out this risk.³

So “orphaned” does not always mean completely unidentifiable. It can sever the account connection, but it cannot erase every clue.

What does the author still own after orphaning?

One common misunderstanding is that orphaning is a copyright waiver.

It is not.

AO3’s Orphaning FAQ states that copyright remains with the original creator after a work is orphaned. Other people do not gain permission to repost, translate, make a podfic, or copy large parts of the work just because it is now an orphaned work. Without permission, those actions may still be infringement or plagiarism, and they may also violate AO3’s Terms of Service.⁴

What the author gives up is control at the AO3 account level.

Once a work has been moved to orphan_account, the original author can no longer edit it, delete it, or reclaim it. AO3’s Chinese FAQ is blunt about this: orphaning is permanent and irreversible, and orphaned works cannot be taken back.³

That is why AO3 repeatedly warns users not to treat orphaning as a light or temporary action. If you only want a work off your profile for a while, or you are not sure what you want yet, orphaning is usually not the right first move.

What happens to the work after orphaning?

AO3’s FAQ says orphaned works keep their existing tags, summary, notes, and other work content. Work settings also remain, such as whether the work is restricted to logged-in users or whether comments are moderated. Existing links remain too, including Related Works, Inspired By, Translation, Gift links, and series connections.⁵

That sounds like “the work stays as it was,” but it also means the author should check the work carefully before orphaning it.

If the body text, author’s notes, summary, tags, or comment replies contain identifying information you no longer want public, remove that information before orphaning. AO3 warns that orphaning does not automatically remove those details. If someone else’s comments or bookmarks contain identifying information, administrators may not be able to remove it either.⁶

Orphaning is not a one-click way to wipe every trace. It only separates the work from your account.

Why would an author give up their byline?

There is no single reason. AO3 does not require authors to explain why they orphan a work, and readers should not treat an orphaned work as an invitation to dig.

Common reasons might include:

• the author no longer wants early works to appear on their profile;
• the author no longer wants a fandom or ship connected to their current account;
• the work is tied to a past period of their life, and they no longer want notifications about it;
• the author wants to clean up their account without breaking old links;
• the work still matters to readers, and the author would rather not delete it.

These reasons do not have to be dramatic. They do not necessarily mean the author hates the work. Sometimes orphaning is simply a way to put some distance between the author and an earlier version of themselves.

From a reader’s point of view, orphaning can feel bittersweet. You can still read the work, but you may not know who to thank, and you cannot follow the byline back to more works by the same author. From the author’s point of view, that separation may be exactly the point. The work remains; the account steps away.

How is orphaning different from anonymous posting or deletion?

If an author only wants to hide their name for a while, an anonymous collection is usually a better fit than orphaning.

AO3’s Collections FAQ explains that when a work is added to an anonymous collection, the work appears as Anonymous, and the author’s pseuds are hidden until the collection reveals creator identities.⁷ The key difference is control: an anonymous work still belongs to the original account. The author can still manage it or restore the byline.

What should readers and fan creators keep in mind?

For readers, the most important thing is to respect the status of the work.

Do not try to publicly “unmask” the original author of an orphaned work. Even if you remember, or can guess from old rec lists, screenshots, or comments, that does not mean the information should be brought back into public circulation. If an author chose to orphan a work, they likely did not want that work to keep leading people back to their current account.

For fan creators, remember this too: an orphaned work is not public-domain material.

AO3’s FAQ is clear that copyright remains with the original creator after orphaning. Without permission, you should not repost, translate, make a podfic, or copy large sections of the work. You may be able to write an inspired-by work, sequel, or remix, but that is different from reusing the original text. AO3 also suggests that if an author wants to allow translations or podfic after orphaning, they can put blanket permission in the work’s notes or tags before orphaning it.⁴

That is why some authors write blanket permission statements in their profiles or notes: they tell later readers what kinds of fan activity are allowed, and under what conditions. If an orphaned work has no such permission attached, do not assume the author has agreed.

Letting the work stay

AO3 does not reduce the question to “keep your name on the work or delete it.” It recognizes a middle situation: an author may no longer want to be tied to a work, but may also not want that work to disappear from fandom.

This is not a perfect solution. Once it is done, it cannot be undone. It also cannot guarantee total anonymity, because traces may remain in the work, comments, bookmarks, or fandom memory. But it does offer an option that is meaningfully different from deletion.

If you are simply reading an orphaned work, you do not need to invent a story about why it was orphaned. You can read it as a work that still belongs in the archive. You can also understand that orphan_account byline as a boundary: the work is still here, but the author has stepped outside it.