How fandoms decide a ship name
Research Desk · Last updated August 2026
Ship names are agreed rather than invented. Somebody uses one, other people repeat it, and after enough repetition it is simply what the pairing is called. No generator, including this one, can produce that. What a generator can do is build candidates for a pairing that does not have a name yet.
That distinction is the most useful thing on this page. If your fandom already has a name, use it. If it does not, the rest of this explains the three shapes those names take and what makes one spread.
The portmanteau
A piece of one name joined to a piece of the other, cut where the names naturally come apart. This is the format most people mean by ship name, it is what the blender on this site builds, and it accounts for most of the names in our library.
Examples: Percabeth, Dramione, Zutara, Taekook
The trait name
Built from what the characters are rather than what they are called. These cannot be traced back to the two names by any tool, including ours, because none of the source letters are in them. If you have been trying to work out how one of these was blended, that is why.
Examples: Wolfstar, Bumbleby
The paired label
Both names kept side by side, joined by a slash, an ampersand or a multiplication sign. It is the older convention and remains standard on archives, because it sorts predictably and cannot be misread. Communities regularly use a paired label for tagging and a blend for conversation, and neither is a downgrade.
Examples: Name/Name, Name x Name
Why trait names break every naming tool
A trait name contains none of the letters of either character's name. Ours are Wolfstar and Bumbleby, and if you hand either of them to a blend checker it will report that it cannot resolve them. That is the correct answer, not a failure, and it is the reason the ship name library labels every entry by type rather than assuming everything is a portmanteau.
It also means a naming tool can never be a complete account of how pairings get named. A blender searches the space of names built from the two names. Trait names come from somewhere else entirely, from what the characters are, and there is no algorithm for noticing that one of them is a werewolf.
What actually makes a name spread
Two properties, and they are the same two that hold for a couple name or a wedding hashtag. A reader who does not already know the pairing should be able to recover both names from it, and should be able to say it without stopping to work out where the seam is.
Our blender measures the first directly, as source coverage, and flags the spelling patterns that usually break the second. That is as far as software can honestly go. The third factor, whether a community adopts it, is not a property of the name at all.
Archive tags are a separate decision
Naming a pairing and tagging a work are different jobs and often want different formats. A blend is the better word for a conversation, a post title or a hashtag. A paired label is the better tag on an archive, because it sorts predictably, cannot be confused with another pairing, and matches whatever convention that archive already runs on.
Check what the archive and the fandom already use before you invent anything. A tag that nobody searches for is not a tag.
Shipping glossary
Ship
Short for relationship. As a noun it is a pairing somebody wants to see together; as a verb, to ship two characters is to want that.
Ship name
The name a community uses for a pairing, usually a blend of the two names but not always.
OTP
One True Pairing. The pairing a particular person cares about most, in a given fandom or across all of them. It is a personal label rather than a community verdict.
BroTP
A pairing somebody wants to see as a close friendship rather than a romance. The name is built the same way; only the intent differs.
OT3
The same idea as OTP for three characters instead of two. Names for these are harder to build, which is what the three name combiner is for.
NOTP
A pairing somebody actively does not want. Worth knowing because it explains why a name can be in wide circulation and still be unpopular.
Canon
A pairing that happens in the source material itself, rather than one readers want to happen.
Fanon
A pairing or detail that a community treats as settled even though the source never established it.
Common questions
Who decides a ship name?
Nobody in particular. Somebody uses a name in a post or a tag, other people repeat it if it is easy to say and easy to recognise, and after enough repetition it becomes the name. There is no vote and no authority, which is why the process looks arbitrary from outside.
Can I change a ship name my fandom already uses?
Almost never, and it is usually not worth trying. The value of a ship name is that it makes your posts findable by people looking for that pairing. A better-constructed alternative that nobody searches for does the opposite of what a ship name is for.
What if a pairing has two competing names?
It happens often, especially early on, and usually one wins within a few months. Until then, using both in a post is the practical answer. Two names in circulation is also the clearest evidence that no blend is objectively best, since the community itself has not agreed.
What does OTP mean?
One True Pairing, the pairing somebody cares about most. It describes a person's preference rather than a community consensus, so two people in the same fandom can have different OTPs without either being wrong.
Why do some fandoms use x instead of a slash?
Different communities settled on different separators. The slash is the older convention in English-language fandom, while the multiplication sign is common in anime and manga fandoms. Both mean the same thing: these two, as a pairing, without merging the names.