Create fictional identities without borrowing a real person's data.
A fake name generator should make sample data easier to use without making it easy to mistake that data for a real person. This tool creates configurable fictional profiles locally in your browser. Choose a country, gender, age range, profile depth, quantity, and repeatable seed, then copy or export the fields needed for a prototype, QA scenario, demo, classroom example, or fictional character sketch.
How to use the Fake Name Generator
Begin by choosing the shape of the fictional audience you need. Select a Country, Age range, and Gender, then decide whether the result should contain a Basic, Contact, or Full profile. Choose between 1, 3, 6, and 12 identities and select Generate fake names.
The shortest useful workflow is:
- Select one country when the interface or story has a specific regional context.
- Choose an age range that matches the screen or scenario being tested.
- Use Basic depth until you know that address, employment, or payment placeholders are necessary.
- Generate one profile while designing a detail view, or several profiles while testing lists and repeated cards.
- Open View details to inspect and copy individual values.
- Export JSON or CSV only after confirming that the selected profile depth contains the fields you need.
All profile generation happens in the browser from bundled sample pools. The tool does not send the form to an AI service and does not search for a real person. Generated names can still match real people by coincidence, so the result should always be treated as fictional placeholder data.
Choose country, gender, and age without implying real demographics
The country selector includes the United States, United Kingdom, Canada, Australia, France, Germany, Spain, Japan, China, South Korea, and Vietnam, plus a Mixed countries option. A country selection changes the available name pool, display order, places, locale formatting, and fictional contact patterns.
Chinese, Japanese, and Korean names are displayed in native characters with the family name first. Vietnamese names retain diacritics and use a spaced family-first format. Other available pools display the given name before the family name.
The Gender control offers Any, Female, and Male because those are the two profile categories currently represented in the local name pools. It does not define how every name is used in real communities, and it is not a demographic model. Select Any when gender is irrelevant to the test. Select a specific option when the interface contains gender-dependent copy, honorifics, or scenarios that you genuinely need to inspect.
The Age range controls the generated age and birthday together. Available ranges are 18–24, 25–34, 35–49, 50–64, and 65–80. This makes it possible to test age-sensitive layouts or write a character within a broad life stage without manually editing every record.
These controls do not claim that the resulting set represents the population of a selected country. Mixed countries deliberately rotates through available local pools; it does not reproduce real-world population proportions, migration, regional diversity, or name frequency.
Select the smallest useful profile depth
Profile depth controls which fields appear in the details dialog, copied text, JSON, and CSV. It does not merely hide fields visually after export.
| Profile depth | Included information | Useful for |
|---|---|---|
| Basic | Name, country, gender, age, birthday, title, username, and GUID | Avatar cards, account menus, author lists, compact test fixtures |
| Contact | Basic fields plus fictional region, city, street, postal code, phone, email, and example website | Contact forms, customer tables, profile screens, address layouts |
| Full | All available fields, including employment, sample payment values, physical placeholders, education, device, and account details | Dense admin screens, end-to-end form layouts, JSON fixtures, complex demos |
Start with Basic when the purpose is uncertain. Extra fields create more information to review and a greater chance that someone will copy values they did not intend to use. Choose Contact when typography, validation, address formatting, or contact rows are part of the task. Choose Full only when the interface genuinely displays the additional groups.
The Full profile includes a known test card number and generated test-only CVC and expiry placeholders. Those values are present for interface demonstrations. They are not payment credentials and must not be used for a transaction.
Reproduce a profile set with the same seed
Every generated set has a Repeatable seed. The seed controls the local pseudo-random sequence used for names and profile fields. Reusing the same seed with the same country, gender, age range, quantity, and profile depth reproduces the current data snapshot.
This is useful when:
- a designer and developer need to discuss the same sample cards;
- a QA report should include data that another person can recreate;
- screenshots need stable names while a layout is being refined;
- a writing exercise should return to the same fictional cast;
- a fixture needs to be regenerated after the downloaded file is misplaced.
Select the shuffle icon beside the seed when you want a new code, or select New set after generation to create a fresh seed and result set together. A seed is not a password, security token, or guarantee that future versions of the site will preserve identical output after the underlying data pools or generation rules change.
Read and use each fictional profile
The result card provides a compact summary: full name, age, generated gender, country, city, occupation, and example email. Select Copy to copy the fields permitted by the current profile depth. Select View details to inspect the complete generated profile.
The details dialog keeps the identity header and main actions visible while only the field list scrolls. Fields are grouped so that a user can find one value without scanning an unstructured wall of data. Depending on profile depth, the dialog can include:
- basic identity information;
- fictional address and contact fields;
- employment and company placeholders;
- test-payment placeholders;
- username, generated password, GUID, device, education, and other sample fields.
Every displayed row has its own copy icon. Copy profile copies the currently included fields as labeled plain text. Download JSON saves the open identity as one structured fictional profile.
The page uses example.com email addresses and example website domains. Phone and address fields are assembled placeholders rather than verified contact data. A plausible-looking combination can still resemble a real person or location by coincidence; the tool does not perform collision checking.
Export fake names as JSON or CSV
The result toolbar can export the complete visible set in two formats:
- JSON preserves field names, the fictional-data marker, submitted filters, seed, and profile objects. Use it when a prototype, test fixture, or script needs structured values.
- CSV creates one row per identity and includes only fields allowed by the selected profile depth. Use it when reviewing records in a spreadsheet or importing flat sample rows into another development tool.
Copy all provides a readable labeled version when a file is unnecessary. It is better for tickets, planning documents, test notes, and prompts where human readability matters more than machine parsing.
Before importing a file, inspect the column names and destination. This generator does not know the validation rules, database schema, consent model, or security requirements of another product. Exported sample data should remain clearly separated from production user records.
A verified fake profile example
A local verification run used United States, Any, 25–34, Contact, 3 profiles, and the seed stable-demo. It returned Harper Turner, age 33, in Denver; Ella Garcia, age 28, in Seattle; and Lucy Mitchell, age 28, in New York. The same filters and seed returned the same records in a second run.
For example, Harper Turner's generated Contact profile included the birthday May 13, 1993, the example email harper.turner+891@example.com, the occupation Operations Coordinator, and the username harperturner912. This is a verified output from the current local data snapshot, not a reference to a real person. Future changes to the bundled pools or generation rules may change what the same seed returns.
Native-script checks also returned 佐々木湊 for Japan, 马梓萱 for China, and 서예준 for South Korea. A Vietnam check returned Hồ Ngọc, retaining its diacritic. These checks are useful for spotting font, truncation, wrapping, sorting, and Unicode assumptions in a product interface.
Generated information is internally coordinated at a practical display level: the selected age falls within the chosen range, a selected gender filters the available name pool, and country-specific formatting affects several fields. It is not a researched biography or culturally verified person model.
Fake name generator versus a large random-name list
The 1000 Random Names tool begins with a large visible name collection. A profile is generated only after you select an individual name. Use that page when the primary task is filling a long list, testing a grid, scanning many names, or choosing a name before creating additional details.
This page begins with complete identities. It is better when the primary task is producing a small set of configurable test users with age, contact, work, account, or export fields. It also adds gender filtering, age ranges, profile depth, batch JSON/CSV export, and a repeatable seed.
Neither workflow is universally better. A thousand-name grid is unnecessarily heavy when a login mockup needs three users. Twelve complete profiles are insufficient when a pagination test needs 1,000 rows. Choose the tool that starts closest to the task.
How this tool compares with common alternatives
Fake Name Generator is an established alternative focused on detailed identities selected by name set, country, and gender. Randommer's Random Person Generator exposes controls including country, gender, quantity, and age. Fakenamely documents larger name batches and CSV/JSON export, while Random User Generator is designed around an API for programmatic records.
Name Idea Box takes a narrower browser-tool approach. Its practical combination is profile-depth control, 1–12 immediately visible profile cards, repeatable seeded generation, individual and batch copy, and JSON/CSV export without requiring an API request from the page.
The tradeoffs are clear. This page supports eleven country pools, not every country or naming tradition. It has no public API, bulk scale beyond 12 complete profiles, custom schema builder, photo generator, real address validation, or live identity service. Use an API-oriented alternative when automation, higher volume, or backend fixture generation is the main requirement.
Responsible uses and limits
Appropriate uses include interface mockups, QA, software demonstrations, tutorials, classroom examples, fiction planning, and placeholders that would otherwise expose real user data.
Do not use generated profiles to:
- impersonate a person;
- create deceptive social or marketplace accounts;
- pass identity, age, employment, or payment verification;
- contact a generated phone number or street address;
- conduct a transaction;
- represent demographic research;
- make a claim about a real culture, person, or population.
This page creates plausible-looking combinations, not legally established identities. It does not verify uniqueness, consent, availability, cultural accuracy, or separation from every real person. Keep the fictional marker when profiles are stored as JSON, and label imported fixtures clearly in your own system.
Common questions
Does this fake name generator use AI?
No. Names and profile fields are assembled locally from bundled data pools and deterministic browser-side generation logic.
Can I generate more than 12 complete profiles?
Not on this page. It is optimized for reviewing small sets of detailed identities. Use 1000 Random Names when you need a much larger visible name list.
Will the same seed always return the same people?
The same seed and filters reproduce the current data snapshot. A future change to the name pools or generation logic can change the output, so downloaded fixtures remain the safest record for long-term use.
Are the addresses and people real?
No lookup is performed, and the combinations are generated as fictional placeholders. Individual names, streets, or places can still resemble real-world information by coincidence.
Can I use these records in production?
They are designed for examples, demos, and testing, not production user records. Review your own application's security, validation, privacy, and data-separation requirements before importing any fixture.
Why does CSV contain fewer fields than Full JSON examples?
Both exports follow the profile depth selected before generation. Choose Full and generate again when the workflow genuinely requires every available field.
