How to Name a Fandom Ship (and Not Step on the Tag)
Naming a fandom ship? Check the existing tag first, pick a format, and mind the ordering rules. A practical guide to fandom ship names and tagging etiquette.
Here's the thing nobody tells new fans: in fandom, naming a ship is less like naming a baby and more like joining a filing system. The name you choose decides whether anyone ever finds your fic, your art, or your 2 a.m. meta post.
So the etiquette matters. This guide covers the formats, the order rules, and the one check you should run before inventing anything. New to the whole concept? Our explainer on what is a ship name covers the basics first.
Rule zero: check whether the ship already has a name
Before you blend anything, search. Look up the pairing on AO3 (the tag wranglers there keep relationship tags organized, and the canonical tag tells you the fandom's settled form) and scan the pairing's tag on Tumblr or your platform of choice.
Three outcomes:
- There's one dominant name. Use it when posting. You can dislike it; use it anyway. Tags are infrastructure, not self-expression.
- There are two or three competing forms. Pick the one with the most works behind it for your main tag; mention alternates in your post text for the searchers.
- Nothing exists. Congratulations — it's a rare pair and the naming rights are yours. The rest of this guide is for you.
The three formats you'll choose between
The slash (or ×) format
Character A/Character B. The oldest format in fandom, straight from early fanfiction archives. It's formal, unambiguous, and archive-friendly — AO3's canonical relationship tags use it. Downside: it's clunky in conversation and useless as a hashtag.
The blend
The portmanteau. Dramione, Reylo, Spirk. Short, taggable, hashtaggable, fun to say. This is the format most people mean by "ship name," and the one our fandom ship name generator builds. Downside: a blend can collide with another fandom's blend, or accidentally read as a real word.
The concept name
A phrase tied to the pairing's story — a shared object, a scene, a motif. Some ships are known almost entirely by concept names because their character names refuse to blend. Downside: opaque to newcomers, and often less searchable than a blend.
Plenty of big ships run two formats at once: slash for the archive, blend for the timeline. That's not indecision, it's best practice.
Name order is not always random
In some fandoms — the convention traveled from Japanese fan culture — the order in a pairing label implies the dynamic: the first-named character is cast in the more dominant or pursuing role. Whole etiquette systems exist around not reversing an established order.
Western fandoms are split. In many, order means nothing and the blend is arranged purely for sound. In others, reversing the order marks a different ship with a different dynamic, and fans will correct you, sometimes gently.
The practical move: when you're new to a fandom, mirror the order you see in the canonical tag until you know the local rules. It costs you nothing.
Building a name for a rare pair: a worked example
Suppose your pairing is two side characters: Odette, a cartographer, and Bram, a lighthouse keeper. No tag exists. Watch the process:
- Try the blends. Odette + Bram → Odam? Reads like a surname, fine. Bram + Odette → Bramette? Charming, slightly comic. Both are candidates.
- Check the blend's other lives. Search "Odam" and "Bramette." One is a place name, the other gets zero results — Bramette is claimable.
- Consider a concept name anyway. Cartographer + lighthouse = maps and light. Lamplight as a concept name is prettier and more evocative than either blend. You might tag Bramette and title the ship Lamplight.
- Write it down somewhere public. A fandom wiki page, a pinned post, the first fic's author note. A name only becomes "the" name when other fans can find and copy it.
The same process works for self-inserts and OC pairings — a yumeship has the same tagging needs as any rare pair.
Small etiquette, big goodwill
- Don't tag ships that aren't in the work. Tag-stuffing with popular pairings to farm views gets your post found by people who will resent it.
- Tag the pairing, warn for the content. Ship name plus content warnings is the pairing's social contract; the name alone isn't.
- Don't coin a rival name for an established ship to make a point. It won't replace the tag, and it reads as a shot in a ship war.
- Credit isn't required for using a name. Ship names are communal property. Nobody can own "Dramione," and nobody should try.
Frequently asked questions
Should I invent a new ship name or use the existing one?
Use the existing one for anything you post. Established ship names are how readers find work — tagging a new name for an established ship mostly means tagging yourself into an empty room. Invent freely for rare pairs with no settled name, or for your own use; just don't expect the fandom to migrate.
What does name order mean in a ship name?
In many fandoms the first-named character in a pairing label signals who "leads" the dynamic — it started as a Japanese fandom convention and spread widely. In Western character×character tags, order often means nothing beyond the tag's history. Check how your fandom treats it before assuming a blend's order is neutral.
What's the difference between Kirk/Spock and Spirk?
They name the same pairing in two formats. The slash format (Kirk/Spock) is the formal tag — it's what archive sites use because both full names stay searchable and unambiguous. The blend (Spirk) is the nickname format: shorter, friendlier, and better for hashtags, conversation, and titles.
What if my ship name is already used by another fandom?
Collisions are common — short blends are a finite resource. In practice, context separates them: tags, fandom names, and character names around the ship name do the disambiguating. If your fandom has an alternative established form (a concept name, say), many fans use that as the public tag instead.
More edge cases are answered in our ship name FAQs.