Khoisan Name Generator

Khoisan names carry click consonants and Dutch or English spellings into passport queues every week.

Start with a sentence about the khoisan name

Khoisan is a cover term for several unrelated language families spoken across southern Africa. San and Khoe communities in Namibia, Botswana, South Africa and Angola use names from Khoekhoe, Ju, Taa and other tongues. Colonial registers and mission records fixed many of these names in Dutch or English spelling from the 1800s onward.

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-one are one word and nine are two words.

Describe who the name is for

Optional. A place, a decade, a family, or the register you’re writing in. One specific detail steers the list better than a paragraph of backstory.

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.

Five runs, printed in full

Nothing below has been edited except the trailing explanation. Most of these lines came back as a name, a dash and a sentence describing it, and the sentence is cut here so the set can be read as a list.

Small town: ǀNunu, ǁKhami, ǂGorases, ǀAris, ǁUbisa, ǂNais, ǀGâis, ǁAros.

Coastal family: ǁKhamǃgôab ǂNūǀgâub, ǃAruǁgâb ǀHōǂgāǁgôab, ǂNūǃgôas ǁKharaǀgâub, ǁGāǃnôab ǂKhamǀgāǁgôab, ǃNūǁgôab ǀGāǂnūǁgâub, ǂHōǃgâb ǁNāǀgōǁgôab, ǁNāǃgôas ǂGāǀnūǁgâub, ǃGāǁnâb ǀHūǂgāǁgôab.

Modern city: !Nauǁgaras, ǁGaroes, !Naiǁgâub, ǂNūǁgaras, !Hūǁgābes, ǁAruǂgāeb, !Gâiǁnâus, ǂGaoǁgaras.

Grandparent: ǁKhamab, ǀGamǃgâ, ǁNâuǀgôab, ǀAruǁgûs, ǁKharaǃnâb, ǃNûǀgôas, ǁAruǀgôab, ǀGamǁnâs.

Two languages: ǁGaroes, Tsamkxao, ǂNūkhoes, Gǀaokxao, ǁAeb !Garus, ǂKhamtama, Gǁaokhoes, ǁNansero.

The shape of forty names

Of the forty names, thirty-one are one word and nine are two words. Every one of them arrives 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.

Khoekhoe speakers in Namibia and South Africa have long used names built from verbs, animals and weather. A name like ǀUib reflects the ǀ click, a dental sound written with a vertical bar in most orthographies. Mission schools in Namaqualand recorded these names in a Dutch-influenced alphabet during the nineteenth century. Juǀʼhoansi names from the Kalahari often describe an animal, a plant, or the condition of the mother at birth. Taa, spoken around the Botswana-Namibia border, has one of the largest click inventories of any language. A dairy cow called Buttercup stays Buttercup, but the Gaelic Name Generator builds names from Irish and Scottish roots. Many San families also carry Afrikaans or Setswana names alongside a Khoisan one, used in different settings. The full traditional name might only appear at a wedding or a funeral, never on a form. Short forms replace the full name in daily speech; a three-syllable name becomes two, then one. Stress usually falls on the first syllable in Khoekhoe names, though Ju names often stress the second.

Khoekhoe click names lead with a click letter and end in a vowel, as in ǀNarimab. Ju animal names describe a creature or its habit, as in ǀAo Nǃao. Mission-era names pair a biblical first name with a Khoisan surname, as in Katrina ǁGaroës. Place-derived names come from a spring, pan or ridge near the birth, as in ǂKhabetsi. The Cow Name Generator works from breeds and pasture, not the click consonants Khoisan naming relies on. Short everyday forms trim the click and keep the vowel, as in Nari from ǀNarimab. Anglicised spellings drop the click mark and double a vowel, as in Xau for ǀXau. Compound names stack two plain words, as in ǁGaroës ǀNarimab. Each register sounds different: clicks are sharp, mission names are soft, place names are flat. Pick the register that matches how the name will actually be used.

Where it goes wrong, run by run

a khoisan name that is very old and very tired returned ǂKx’ao ǁGaro, ǀGam ǂNûi, ǁXam ǃKao, ǂKhaba ǀGōa, ǀAe ǁGam, ǃNau ǂKx’ao, ǁGū ǀXam, ǂNū ǁKha. The eight share no ending at all. The sentence supplied a feeling and the output supplied names, and the two never met. Plausible is not the same as chosen.

a khoisan name for something that guards a door returned !Gâuǁnâ, ǀNūǀgôab, ǁKharaǃgâb, ǂNûiǁgâǀgôas, ǀGamǃnāǁnâs, ǁNāuǀgôab, ǂGāǁnâb, ǀǀNôaǃgâb. The eight share no ending at all. The prop took over. All eight are about the thing in the sentence and none of them is about the thing being named.

Two prompts, two opposite failures. The first supplied a mood and no subject, so the eight names fit the category and nothing narrower. The second supplied one concrete noun, and that noun became the entire brief. A sentence that works sits between them: it names the thing, not a feeling and not a prop.

Which of the three to use

Three routes get a khoisan name. Only one of them is a name generator.

What mattersBy handA general chatbotThis generator
Time for eight namesTwenty minutes or moreOne prompt, then editing2.6 s per set, instant on a repeat
Same prompt, same eightOnly if you write it downNo, the wording driftsYes
Explains the choiceYou doYes, at lengthNo
CostYour timeA subscriptionFree, no account
Checks trademarksNoNoNo

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 which name belongs to your family, your clan, or your region. It doesn't know the naming rules of a specific community, because those rules aren't written down in one place. A name that reads well in a list may be wrong for a person of a different age or gender.

What to change on the rerun

Compare a khoisan name for a girl born in a small town in the 1950s with the two prompts in the section above. The difference is not length or politeness: this one names a place and a use, and the output follows: ǀNunu, ǁKhami, ǂGorases, ǀAris, ǁUbisa.

You type something like a Nama woman born in Keetmanshoop who works with livestock. The generator reads that sentence for concrete words: Nama, woman, Keetmanshoop, livestock. It ignores your tone, your punctuation, and any opinion you add about the name you want. Place names steer the result toward the languages actually spoken there. A job word like livestock pulls in names connected to cattle, herding, or the veld. Eight names come back. Some are single words, some are two-word phrases. A short description gives broad results; a longer one narrows the field. If you mention a grandparent's name, the output may echo its shape without copying it. Nothing you type is stored, and you can paste the list straight into a document.

Questions before you start

Are these names actually used in Namibia and Botswana?

Yes, though many people carry two names, one Khoisan and one Afrikaans or English. The Khoisan name is often the family name, used at home and at ceremonies. The other name appears on school records, job applications and passports.

Why do some names have exclamation marks and bars?

Those marks stand for click consonants, which are ordinary sounds in these languages. Latin script has no standard letter for a click, so writers borrowed punctuation. Different countries and schools settled on different marks for the same sound.

Can I use a Khoisan name for a character in a novel?

You can, and the generator gives you eight options to start from. Check the name with a speaker if the character is meant to be from a specific community. Getting the click wrong in dialogue reads as a mistake to anyone who speaks the language.

What happens to the click when I type the name into a form?

Some systems accept the character, and some strip it out and leave a gap. A passport might print ǀNarimab, Narimab, or Narimap depending on the software. Keep a plain-spelled version of the name for forms that reject click marks.

How is the name stressed when spoken?

Khoekhoe names usually carry stress on the first syllable, including the click. Ju names often shift stress to the second syllable, especially in two-word names. Short forms keep the stress of the full name, which is why they sound familiar.

Daniel Reyes, site author
Daniel Reyes

Daniel works on brand naming for small companies and writes about given names as a hobby. He covers business and people names here, with an eye on what a name has to survive once it is printed on something.

On the business lists he checks the practical failures first: whether the domain and handle are plausibly free, whether the name survives being spelled out over a phone call, and whether it still reads on a van door. For the people lists he works from usage rather than taste.

Articles: 72