Are these real people?

No. Every profile is entirely fictional, assembled from built-in name lists. Any resemblance to a real person is coincidental.

Can the emails or phone numbers reach anyone?

No. Emails use example.com domains and phone numbers use the 555 exchange reserved for fiction, so they cannot reach a real inbox or line.

What fields does each profile include?

Each fake user has a full name, a username, an email, a phone number, a street address, and a date of birth — enough to populate a typical user table or signup form for testing.

How do I get the data into my tests?

Click "Copy as JSON" to copy the whole batch as a JSON array, then paste it straight into a seed script, fixture file, or mock API. Each user is an object with the standard fields.

Why use 555 phone numbers and example.com emails?

The 555 exchange and the example.com / example.org domains are reserved by convention for fiction and documentation. Using them guarantees your test data can never accidentally email or call a real person.

Is this safe to use under privacy laws like GDPR?

Because the data is entirely synthetic and matches no real individual, it contains no personal data, making it ideal for demos, screenshots, and shared test environments without privacy concerns.

Is any data fetched or uploaded?

No. Everything is built locally in your browser — no API is called and nothing is transmitted.

What is the Random User Generator?

Generate random fake users — name, username, email, phone, address and date of birth — for test fixtures and mock data. Uses reserved 555 numbers and example.com emails so they reach no one. Runs in your browser. It runs free in your browser on Gera Tools, with nothing uploaded.

Random User Generator

Name: Random User Generator
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

Generate complete fake user profiles — name, username, email, phone, street address, and date of birth — for test fixtures, mock data, demos, and seed scripts. Copy the whole batch as JSON in one click, then drop it straight into your code.

How it works

For each profile the tool assembles fields from built-in lists and patterns using the browser’s random generator: it pairs a random first and last name, derives a username and an email from that name on an example.com-style domain, builds a phone number on the reserved 555 exchange, composes a street address from random street and city parts, and picks a plausible date of birth. Because every value is synthetic and uses ranges reserved for fiction, no email can reach an inbox and no number can ring a real line. The whole batch can be exported as a JSON array for easy import into tests.

Example output

Generating one user produces a record like:

{
  "name": "Sophia Bennett",
  "username": "sophia.bennett",
  "email": "[email protected]",
  "phone": "(555) 247-8810",
  "address": "418 Maple Avenue, Springfield",
  "dob": "1992-08-14"
}

Field	Safe-by-design reason
Email	`@example.com` is an IANA-reserved domain — email servers will not deliver to it
Phone	`555` is the exchange reserved for fictional use in North American media
Name / address / DOB	Fully synthetic, assembled from built-in word lists with no real-person mapping

No API is contacted — everything is built in your browser and nothing is uploaded.

Why these safe-by-design conventions matter

The 555 exchange has been reserved for fictional use in North American fiction and documentation since the 1990s, which is why films and television shows use it for any on-screen number. The example.com, example.org, and example.net domains are reserved by the Internet Assigned Numbers Authority (IANA) under RFC 2606 specifically so they can appear in documentation, examples, and test code without routing to real mailboxes.

Using these conventions in test data means your development and staging environments can never accidentally send a real email or call a real number during testing, even if an email or SMS feature is triggered by a test action.

Common use cases

Seed scripts — generate 50 or 100 users and paste the JSON array directly into a database seed file. The data is varied enough to test UI components that display user lists, search, and filters.

UI mockups — paste a batch into a design tool to show realistic name lengths, email lengths, and address formatting without using any real person’s data.

API testing — use generated profiles as request bodies when testing user-creation endpoints, profile update flows, and validation edge cases.

GDPR-safe demos — because the data is entirely synthetic and matches no real individual, it carries no personal data obligations and is safe to use in screenshots, screen recordings, and shared staging environments.

Privacy compliance note

Synthetic test data generated here contains no personal data under GDPR, CCPA, or similar frameworks because it does not relate to an identifiable natural person. It is safe to share across development teams, include in public documentation, and use in demos without redaction.