Generate random person

How it works

The generator holds lists: given names, family names, and whatever extra fields the page offers. It draws from those lists and prints a row that looks like a person-shaped record. A second click is a second row. There is no interview. There is no check that the combination exists in the world. “Maya Chen, librarian” is a costume of a record. It is not a claim that such a librarian sits at a desk.

What you get is what the lists contain. A list of English given names will not emit a writing system it does not have. A list without surnames will not invent a legal family name. A page that adds an email pattern is still patterning: it is not creating an inbox. Read the fields. If a field is missing, the tool does not have it. Do not fill the gap by guessing a government number.

Most pages use a computer algorithm that is hard to predict by eye. That is enough for a mock user, a game non-player, a fiction sketch, or a form that needs a name to look occupied. It is the wrong object if you need a real occupant, a real payroll identity, or a disguise for a purchase.

Fields that look like a person

A useful dummy has stable columns. Name is the minimum. Age or a date of birth is a second column if your form needs one. A job title, a city, or a phone-shaped string may exist as decoration. Keep the country and the script consistent inside one row. Mixing a phone pattern from one country with a postal pattern from another makes a fixture that tests nothing except your tolerance for noise.

Name: given name and family name from lists you accept. Age or birth date: a number in a range you set, not a biography. Role: a job title from a short list, if the demo needs a role. Contact-shaped fields: patterns, not live inboxes or live lines.

Repeats happen when the name lists are short. Two “Alex Kim” rows in a demo file are a small-pool problem. For unique-looking users, you want more name parts, a numeric suffix used only in the test system, or sampling that does not immediately reuse a full line. For a load test, repeats may not matter. Say which job you wanted.

Age is a draw from a range, not a life. Do not treat a generated age as medical data. Do not treat a generated job as employment. If you are testing software, broken fixtures hide bugs: a form that accepts “Librarian” in a country field will look fine until a real user types a country. Keep each field in its type.

What you must not do with a dummy

Copy a generated person into a demo account, a design mock, a story, or a classroom example. Do not submit it as a government identity. Do not use it to open a bank account. Do not attach it to a real photograph of a stranger. Do not use it to harass, to impersonate, or to pass a check that asked for a living person.

A collision is possible. A generated name can match a living person by accident. If you publish the dummy outside a private test, avoid pairing that name with extra details that would look like a dossier. Inside a private staging database, label the rows as generated so the next teammate does not moderate them as customers.

A generated person has fields. A person has a say, and this button is not that say. Save the row if your team will reuse it as a fixture. Tomorrow’s click is a different dummy. Memory of “it was a teacher named Sam” is not a record. The printed line is the record. When the test is over, do not leave dummy people in a production list where staff might email them.