What this tool does
Placeholder data shapes perception. When every demo user is “John Smith” or “Jane Doe”, a product quietly communicates a default identity. This generator produces gender-neutral and non-binary coded placeholder names, optionally prefixed with the Mx. honorific and accompanied by a sample email handle, so your mockups, research scripts, and seed data stay inclusive by default.
Why inclusive placeholder data matters
Demo accounts, seed data, and mockup screenshots get seen by more people than most designers realise. They appear in:
- Sales demos shown to prospective customers
- Support team training materials
- Public screenshots in app store listings and marketing sites
- Press screenshots shared with journalists
- Investor pitch decks
When every fictional user is “John Smith” or “Jane Doe”, those audiences absorb a subtle signal about who the product is designed for. Gender-neutral names avoid that signal without requiring any extra effort at the point of use.
A secondary benefit: gender-neutral placeholder personas help catch form and UI problems that gendered defaults might mask. If a form field has a title/salutation requirement, using Mx. as the test honorific reveals whether the field is actually inclusive — or whether it only accepts Mr./Mrs./Ms.
How it works
The tool draws from a curated list of genuinely unisex first names (such as Alex,
Sam, Riley, or Jordan) and a separate list of common surnames. For each entry it
pairs a random first name with a random surname, ensuring no exact duplicate
appears in a single batch. If you enable the honorific, it prefixes “Mx.” to the
full name. The optional email handle is derived from the name in lowercase with a
dot separator, using example.com as the domain.
Everything runs locally in your browser, and nothing is stored or transmitted.
About the Mx. honorific
Mx. (pronounced “mix” or “mux”) is a gender-neutral honorific used in place of Mr., Mrs., Ms., or Miss. It originated in the UK and is now recognised in many official contexts, including on UK government documents and in style guides from major publishers. It is the standard test case for ensuring a title or salutation field genuinely supports non-binary and unspecified-gender users.
When building or testing a form with a title field, always verify that Mx. is an available option — not just Mr., Mrs., and Ms. If it is not, you have found an accessibility and inclusion gap worth filing as a bug.
Tips and examples
- Use the Mx. honorific in forms and CRMs that require a title field, so you test the inclusive path rather than only Mr. or Ms.
- Pair these names with neutral avatars or initials to keep your whole demo presentation consistent.
- For research scripts, gender-neutral personas reduce the risk of participants reading assumptions into your prototype.
- A generated handle like
[email protected]is safe for screenshots becauseexample.comis a reserved domain and never resolves to a real inbox. - For larger seed data sets, combine this generator output with a faker library to fill in addresses, phone numbers, and other fields consistently.