The sentence is the whole input
Tyranid names in the fiction lean on Latin and Greek roots filtered through a biological vocabulary. Brood, hive, fleet and swarm give the naming a small set of English anchors to build around. Games Workshop writers kept the register cold, so the names read as catalogued rather than spoken.
The field takes a sentence. Five prompts into it produced 40 names, and the shape of those 40 is the first thing worth knowing. Of those, thirty-two are one word and eight are two words.
Describe what you’re naming
Optional. A people, a landscape, a mood, or the setting it belongs to. The more specific the culture, the more consistent the eight names come back.
Pick a filter if you have one. It narrows the register, not the meaning.
Names, one per line. Nothing is stored.
Names are generated on the server and shown once. Reloading clears them.
Forty names it actually produced
Nothing below has been edited. Each group is one run of the tyranid name generator, quoted in the order it came back.
Northern coast: Kragthrax, Skarnvold, Drakkhelm, Grimnacht, Thrakgorn, Varkstjorn, Hjarnskold, Brakkvandr.
Old order: Sza'thraxis, Vael'koruun, Ith'zaraq, Nhor'velith, Xa'ulthraen, Serr'vokai, Ombra'zyth, Kael'voruun.
Drowned city: Vael'Uthar, Sinkhollow, Mor'Drevan, Nhal'Therix, Gor'Shael, Ythra'Kol, Drevan'Ulm, Xa'Rethis.
Border post: Kharzhak Nullgate, Vurthax Deadwatch, Szaakryn Hollowspine, Morgrax Stillspore, Tethrakh Ashgate, Yulvash Kineater, Grathuun Emptyweb, Xolvaar Lastsentry.
Small court: Xul’thraa, Vaskra’neth, Kryll’saan, Morgaalith, Zhaa’krun, Tessek’vaal, Qor’malaan, Yrr’shaa.
The pattern in forty names
Of the forty names, thirty-two are one word and eight are two words. Twelve of them arrive with a description attached.
No closing word repeats more than three times, which is why the set reads as forty separate names rather than one name with variations.
Tyranid naming grew out of a specific period of Games Workshop writing in the late eighties and nineties. Designers pulled from Latin taxonomy, Greek prefixes and the sound of insect genera read aloud. Hive Fleet Behemoth set the template, and later fleets followed the same heavy, clipped shape. Tyranids get hive fleet designations while God of War characters carry Greek and Norse myth names, so the God of War Name Generator differs. Fleet names took biblical and monstrous references, then stripped them of any human context. Brood names leaned harder on the Latin, so terms like gaunt and genestealer entered the vocabulary. The fiction treats naming as a human act, which is why the names sound like a catalogue entry. Adeptus Biologis records in the setting explain the names as classifications, not self-descriptions. That framing lets a name be ugly, because nothing in the fiction has to say it comfortably. Writers kept the register consistent across codexes, novels and rulebooks for over thirty years.
Fleet-classical names carry a Latin weight and a hard opening consonant, as in Behemoth. Brood-taxonomic names read like a genus entry, clipped and unfriendly, as in Termagant. Swarm-compound names glue two short roots together, giving Ripper Swarm its blunt sound. Bio-mechanical names borrow from industrial vocabulary and land colder, as in Carnifex. Vowel-heavy names slow the reader down and suit larger organisms, as in Hierophant. For a different register entirely, the Mech Name Generator handles names built from metal and function. Guttural names stack consonants and work best for small, fast broods, as in Gargoyle.
Four runs that went wrong
a tyranid name that is very old and very tired returned Kaelthrax the Sleepless, Vael'ghar the Weary, Mor'keth the Dimming, Sythraan the Slow, Ur'ghaal the Hollow, Ny'thra the Waning, Draal'vex the Still, Oth'mura the Last Breath. No ending repeats across the eight. None of the eight is wrong, and none of them is about your subject in particular. That is the failure mode worth recognising.
a tyranid name for something that guards a door returned Vorr'khal, Ghol'thrax, Sythraak, Dro'vannok, Karruthix, Maug'laan, Xyth'rekk, Bel'kharok. No ending repeats across the eight. Every one of those names belongs to the prop. Swap the subject for anything else and the same eight would still come back.
Read the two prompts again and the two failures are exact opposites. One gives the model a tone to imitate and nothing to name. The other gives it a single object to name and no tone at all. Both return eight plausible names, and neither returns eight names for your subject in particular.
How the alternatives stack up
Three routes get a tyranid name. Only one of them is a name generator.
| What matters | By hand | A general chatbot | This generator |
|---|---|---|---|
| Time for eight names | Twenty minutes or more | One prompt, then editing | 1.5 s per set, instant on a repeat |
| Same prompt, same eight | Only if you write it down | No, the wording drifts | Yes |
| Explains the choice | You do | Yes, at length | No |
| Cost | Your time | A subscription | Free, no account |
| Checks trademarks | No | No | No |
A first run takes a few seconds. The same sentence again returns in milliseconds, because the backend caches each set by prompt, so a set you liked is reproducible tomorrow and a set you did not like costs nothing to replace.
The generator can't tell you whether a name already belongs to a published fleet or character. Games Workshop has used hundreds of names across codexes, novels and campaign books. A name that sounds right to you may sit close to something already in print, and only a search will tell you.
Rewriting for a better set
a tyranid name with hard northern consonants is the prompt that produced the set above. It works because it commits to something you could point at, and the eight that came back are Kragthrax, Skarnvold, Drakkhelm, Grimnacht, Thrakgorn.
You type a sentence about the creature, fleet or brood you have in mind and press the button. Eight names come back in a list, ordered without explanation and with no notes attached. Words like swarm, chitin, fleet and brood steer the output toward the established register. Adjectives get picked up more often than verbs, since descriptions of organisms tend to be static. A description focused on colour or size tends to produce flatter names than one focused on behaviour. Proper nouns you type are treated as suggestions, not as material to copy directly. Long descriptions don't produce longer names, and short ones don't produce shorter ones. The tool ignores punctuation, so commas and dashes in your sentence change nothing about the result. Meaning in your sentence matters less than the shape of the words you chose to write it with.
What gets asked
Can I use these names in a published novel or game?
Games Workshop holds trademarks on specific names used in its own publications. A name the generator produces isn't automatically clear of those marks, so check before publishing. For personal campaigns and fan work the question rarely comes up in practice.
How many names do I get per run?
Each run returns eight names in a single list with no ranking. Each sentence is cached, so running it again returns the same eight. Reword one part of the sentence and you get a different set. There's no way to request more than eight at once.
Do I need to know the lore to use it?
Knowing the fiction helps you judge whether a name fits a fleet or a brood. The tool doesn't check your description against any canon, and it won't correct you. A reader who knows the setting will spot a name that breaks the register faster than you will.
What if I want names for a different faction?
The register here is specific to Tyranids, and other factions use different conventions. Space Marine names lean on Latin and Gothic forms, while Eldar names use longer vowel runs. Running a description through this tool for an Ork will produce something that sounds wrong.
Are the names checked against existing publications?
No, and that check isn't something the tool can do. Names in print span decades of codexes, novels and campaign supplements. Searching the name yourself is the only reliable way to know if it's already in use.
