Random city generator

How it works

Two constructions hide under the same title. The first is a catalogue: the tool stores city names and returns one. That construction is a picker with a built-in list you did not paste. The second is an assembler: it combines stems, suffixes, and sometimes a region flavor into a name that looks like a place. “Riverford” can be a real town on a list, or a toy built from “river” and a common ending. Read which construction you are in. The button will not confess unless the page says so.

A computer algorithm usually does the draw. Repeats happen when the catalogue is small or the assembler has a short stem list. If the fifth name is the first name with a different suffix, the pool is thin. That is a list problem. It is not a property of geography.

People type random.city generator with a dot in the middle when they mean this same job: a generator of a city, as a name. The dot is punctuation in a query, not a special mode. You still need to know whether the result is a real gazetteer hit or an invented label.

Real gazetteer versus invented names

A gazetteer hit is a name that exists as a settlement on some map the list copied. It still may not be the settlement you had in mind: many names repeat across countries. “Springfield” is a name, not a unique pin. If you needed a unique pin, you needed country and region beside the name, and a list that stores those columns. A bare string is not a pin.

An invented toponym is a costume of a city. It is useful for a game map, a novel, a tabletop setting, a dummy shipping city in a test that must not match a live address. It is a poor quiz answer. It is a poor destination. Do not ask a travel agent to quote a fare to a name you generated from stems.

Catalogue draw: one stored settlement name, sometimes with a country field. Assembler: stems and endings, a plausible label, not a booking. Needed columns: country, region, and script, if the job is a fixture.

Forbidden use: pretending the name is a reservation or a legal domicile. If the page mixes both constructions in one stream, label your copy. A test file that thinks “Riverford” is always fictional will break when a real Riverford is in the catalogue. A fiction bible that thinks every generated name is real will send a character to a place you cannot describe. Keep the origin next to the name.

What to copy, and what to leave

Copy a generated city into a scene, a game, a dummy form, or a classroom prompt. Do not copy it into a visa, a tax form, or a live shipment as if it were your town. Do not attach a generated name to a real household. If a map plots a catalogue name, that plot is a map feature. It is not proof that you live there.

A generated city will not hold your mail. It will only give the next sentence a place-shaped word. Save the name with the construction and the date you drew it if the team will reuse the fixture. Tomorrow’s click is a different string. If you are generating a setting, one accepted name is enough to start. Extra clicks after you already wrote a street are how a story grows a second capital by accident. Stop when the name is in the draft.