ShipName.net is a brainstorming tool, not an authority that decides the "correct" name for a couple or fictional pairing. This page documents what the generator does, how we review its output, and where human judgment is still necessary.
The generator accepts two names and a style. It asks a language model for eight compact blends when that service is available. If the request fails or takes too long, the browser or server creates a fallback set by combining different parts of the two inputs.
That fallback matters because it keeps the tool usable, but it also exposes an important limitation: a mechanically valid blend is not automatically a good name. Users should compare the results, say them aloud, and check how they look before choosing one.
The request contains only the two names entered in the form, the selected style, and a language setting. The generation instruction asks for:
The generator does not know the people behind the names, their preferences, or the context in which a result will be used. It cannot determine whether a suggestion is already a username, trademark, fandom tag, or offensive word in every language.
When model output is unavailable, the tool applies several deterministic combinations. Assume the inputs are Alex and Jordan:
| Rule | Construction | Example |
| --- | --- | --- |
| Full forward | first name + second name | AlexJordan |
| Full reverse | second name + first name | JordanAlex |
| Half blend | first half of one + second half of the other | Aldan |
| Reverse half blend | reverse the previous source order | Jorex |
| Initial blend | first initial + the other full name | Ajordan |
| Overlap blend | remove the last letter of one and first letter of the other | Aleordan |
Duplicate results are removed in the browser. Style selection may also change capitalization or add a playful marker. These rules favor coverage over certainty: they create several starting points quickly, but some pairs naturally produce awkward joins.
When we assess examples for an article or guide, we do not call every generated string a recommendation. We use four checks.
A reader should be able to see or hear a meaningful piece of both names. A result made almost entirely from one input scores poorly even when it is pronounceable.
For Sofia + Mateo, Sofateo preserves recognizable material from both sources. A result such as SofiaM technically includes both but gives the second name too little weight.
The join should be speakable without stopping to decode it. We look for collisions such as three consonants in a row, repeated syllables, or a boundary that suggests two conflicting pronunciations.
Reading a candidate aloud is more useful than counting letters. Lima from Liam + Emma is easy to say, although it may be too close to an existing place name for some uses.
A strong result should be easy to type, remember, and recognize in lowercase. This matters for tags and usernames, where capitalization may disappear. We reject examples that require punctuation to make the blend understandable.
The final check happens outside the blending algorithm. Search the candidate, inspect it in lowercase, and ask speakers of the relevant language if the audience is multilingual. A harmless-looking join can already belong to a company, creator, fandom, or community.
Use this simple table to compare a short list rather than accepting the first result:
| Candidate | Both names visible? | Easy to say? | Easy to type? | Search checked? | | --- | --- | --- | --- | --- | | Option 1 | Yes / No | Yes / No | Yes / No | Yes / No | | Option 2 | Yes / No | Yes / No | Yes / No | Yes / No | | Option 3 | Yes / No | Yes / No | Yes / No | Yes / No |
Discard a candidate when either source is unrecognizable or pronunciation is unclear. For a private joke, the remaining checks can be relaxed. For a public username, wedding hashtag, book, product, or business, complete every check and verify availability on the platforms that matter.
The tool does not guarantee:
Generated suggestions are therefore drafts. The person choosing the name remains responsible for checking the final use.
We revise our examples when a blend is unclear, misleading, or carries an unintended meaning we missed. To report a problem, send the page URL, the two input names, the selected style, and the result to [email protected]. Do not include private information that is not needed to reproduce the issue.
For more guidance, see How to Make a Ship Name That Actually Sounds Good and our Editorial Policy.
Last reviewed: June 19, 2026