How to use Fake User Generator
- Choose how many users you need (1–1000), the locale and optionally a phone country.
- Decide whether to include password and timestamp fields.
- Pick the output format and press Generate.
- Copy the dataset or download it with the right extension for your seeding script.
Fake User Generator features
- Complete user objects: id, UUID, names, gender, username, email, password, avatar seed, role, status, phone, birth date and timestamps
- Usernames and emails derived from the generated name so records are internally consistent
- Arabic and Hindi names with Latin transliteration for usernames
- Country-aware mobile numbers in E.164 (default follows the locale)
- Toggle password and timestamp fields on or off
- Weighted statuses (mostly active, some invited/suspended/inactive) for realistic filters
- Reproducible with a seed; JSON, CSV, SQL, XML, JSON Lines or text table output
Fake User Generator example
Three Arabic users as JSON
Input:
Users: 3 · Locale: Arabic · Format: JSON · Seed: users-demoOutput:
[
{
"id": 1,
"uuid": "3953b147-4aa6-45cd-a9b8-d11b57d5ef56",
"firstName": "نايف",
"lastName": "الثبيتي",
"fullName": "نايف طارق الثبيتي",
"username": "nayefalthubaiti819",
"email": "nayefalthubaiti819@example.com",
"role": "editor",
"status": "active",
"phone": "+966508370878",
…
}
]Frequently asked questions about Fake User Generator
How are usernames and emails derived?
Both come from the generated name (first.last, first_last, optional digits), so every record is internally consistent. Emails always use reserved domains such as example.com.
Can I generate Arabic or Hindi users?
Yes — pick the locale. Names are produced in Arabic or Devanagari script while usernames and emails use a Latin transliteration, mirroring real bilingual systems.
Are the passwords safe to use?
They are random 12-character strings that satisfy typical complexity rules, intended only for seeding test accounts. Never reuse them for real logins.
What do the role and status fields contain?
Roles cycle through admin, editor, viewer, member, moderator and support; statuses are weighted towards active with some invited, suspended and inactive users so filters and permissions can be tested.
Technical notes
Passwords contain at least one lowercase letter, one uppercase letter, one digit and one symbol and avoid ambiguous characters. Creation dates fall within the last three years and last-login dates always come after creation, so time-based queries behave sensibly.