What Is a Ship Name? A Fandom Naming Field Guide
A source-backed guide to pairing names, portmanteaus, fandom conventions, and when a two-name blend is the wrong format.
A ship name is a stable label for a pairing. It can be a blend of two names, but it does not have to be.
That distinction matters. A generator can produce letter combinations; a community decides whether a label is recognizable, searchable, and worth using.
The short definition
In fandom, "ship" comes from relationship. Fanlore's overview of shipping describes shipping as supporting, imagining, discussing, or creating fanworks about a relationship. A ship name is the label used for that pairing.
Fanlore's pairing-name history documents several naming systems:
- parts of two character names;
- a slash or x between names;
- an ampersand for a non-romantic archive relationship;
- one label or complete relationship format for a poly or group ship;
- acronyms;
- words connected to the characters or their story;
- fandom-specific systems such as names ending in "shipping."
So Taylor + Travis = Tayvis is one kind of ship name, not the definition of every ship name.
Ship name, pairing name, and portmanteau
These terms overlap but are not identical.
| Term | Practical meaning |
|---|---|
| Ship | The relationship or pairing itself |
| Pairing name | Any established label for that pairing |
| Portmanteau or name blend | A new form made by combining material from both names |
| Slash notation | On AO3, names separated by / mark a romantic or sexual relationship |
| Ampersand notation | On AO3, names separated by & mark a platonic or other non-romantic relationship |
Merriam-Webster defines a portmanteau as a word formed by combining spellings and meanings from other words or word parts. A name blend uses the same construction idea, although it combines identity signals rather than dictionary meanings.
This is why a result can be a valid blend but a poor pairing name. It may combine letters correctly while hiding one source, sounding awkward, or colliding with an existing term.
Six naming systems found in fandom
1. Name blends
The beginning of one name joins the end of another:
- Taylor + Travis → Tayvis
- Daniel + Olivia → Danivia
Blends are compact and work well in tags. Their weakness is ambiguity: a smooth new word may no longer reveal both sources.
2. Slash, ampersand, or x notation
The full names stay visible:
- Character A / Character B
- Character A & Character B
- Character A x Character B
This format is usually clearer for a new reader. AO3's Tags FAQ says slash and ampersand are not interchangeable: slash is romantic or sexual, while ampersand is platonic or otherwise non-romantic. Fanlore notes that communities also differ on punctuation and order; its relationship-page guidance follows the convention favored by the relevant fandom instead of imposing one universal standard.
3. Initials and acronyms
Initials are useful when full names are long, but they can be impossible to discover without context. Before choosing one, search the acronym together with the fandom or project name.
4. Group or poly names
A three-to-five-person ship may use one concept, one label containing a fragment from every member, or a complete full-name relationship tag. A group blend should never silently drop a participant. When a compact blend becomes unreadable, a full-name slash, ampersand, or x format is clearer.
5. Concept names
Some pairings use a place, quote, event, role, color, object, or shared theme. These names can be memorable because they carry story meaning, but outsiders may not know who the pairing includes.
6. Fandom-specific systems
Some communities maintain their own naming grammar. Fanlore documents "___shipping" names, numerical systems, and labels derived from canon vocabulary. A general-purpose name combiner cannot infer those conventions from two names alone.
What a generator can and cannot do
Shipname can test visible structure:
- how much of each source name remains;
- whether one source dominates;
- whether the result contains difficult character runs;
- whether the join is compact;
- whether the result is short enough to scan.
It cannot determine whether a community already uses another name, whether name order carries meaning, or whether a concept name would be more appropriate. The public engine regression checks make this boundary visible: non-Latin inputs are generated but flagged for language review.
The exact generation and weighting rules are documented in How the Shipname Works.
A decision rule that works
Use a blend when all four statements are true:
- Both sources remain recognizable.
- The result can be read aloud without a private explanation.
- It does not conflict with the relevant community's established label.
- It is easier to use than writing both names.
Use slash, ampersand, x notation, or full names when clarity matters more than novelty, while preserving each platform's relationship meaning. Use a concept name when the community already recognizes one or when the names themselves do not blend cleanly.
Research notes
This guide treats Fanlore as a record of fan practices, not as a rulebook. Naming conventions change between communities and over time. The structural examples were checked with Shipname engine 2026.08.24-2.
Sources reviewed
- Fanlore: Shipping
- Fanlore: Pairing Name
- Fanlore: Help for relationship pages
- AO3: Tags FAQ
- Merriam-Webster: Portmanteau
Last reviewed: August 24, 2026
Change note: Replaced an unsourced example list with a sourced taxonomy and explicit generator limits.