Random person generator

How it works

The tool holds fields and fills them. A given name comes from a name list. A family name comes from another. An age comes from a range. A city, a job title, an email pattern, or a phone pattern may be attached so the row looks like a contact card. There is no census behind the button. The mixer does not check whether the combination matches someone alive. It has fields, not neighbors.

Quality is the lists and the consistency rules. A United States–style phone next to a city in another country is a broken fixture. An age of eight next to a job of “surgeon” is a joke or a bug, depending on whether you wanted a joke. A useful tool lets you lock a locale and a plausible age band so a test database does not hide software errors behind cartoon rows.

A short name pool, or names put back after a draw, will echo. Two “Alex Kim” rows can be honest. If your demo cannot stand two similar names, you need a larger pool or a uniqueness rule on the full line, not a lecture about chance. The generator is a mixer. It is not a population.

Fields that look real, and fields that must not

A first name and a city are usually enough for a novel, a game NPC, or a layout mock. A full street line, a government id pattern, and a date of birth together start to look like someone you could impersonate. Do not generate that bundle unless you are filling a private test system, and even then keep it obviously fake: reserved domains, impossible id checksums, or a label that says sample. A profile that could pass a checkout as a stranger is the wrong object.

Name the job: fiction, UI mock, test database, or classroom prompt. Turn on only the fields that job needs. Extra fields are extra ways to look like a real person. Lock a locale so names, phones, and addresses share a country.

Read the row. If it names a living public figure by accident, discard it. Copy once if you need a fixture. The next click is a different person-shaped row. Email and phone fields are costumes. Do not send mail to a generated address to “see if it bounces.” Do not call a generated number. Those channels may belong to someone. A pattern that looks like a number is still a pattern until you have a reason to believe it is yours to use.

Teachers can use a generator to invent a character for a writing prompt. That works when the class can see the origin. The moment you present the row as a neighbor, a witness, or a customer who exists, you have left the tool’s job. Keep the origin visible wherever truth matters.

Fiction, fixtures, and the line you do not cross

Skip the generator when you needed a real contact. Skip it when you needed a legal name on a form. Skip it when the assignment was to interview a person. A generated profile is not consent. It is not a background check. It is not a user you may bill.

A random person is a stack of list items in a trench coat. Do not send the coat to a real address. If you are seeding a database, mark the rows as generated so the next person does not moderate them as users, ship parcels to them, or email them a reset link. Pretty sample data is still sample data. Unlabeled sample data becomes an incident.