Synthetic User Profile & Mock Data Generator
Pricing
from $0.49 / 1,000 results
Synthetic User Profile & Mock Data Generator
Generate randomized, realistic-looking user profiles for test and demo data: name, email, phone, address with coordinates, date of birth, profile picture, and optional username and hashed password, filterable by gender and nationality.
Pricing
from $0.49 / 1,000 results
Rating
0.0
(0)
Developer
crawlyth forge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Features
Share
Need realistic-looking fake people for a demo, a UI mockup, or a test database seed? This actor generates fully fictional user profiles — name, contact details, address, date of birth and a profile picture — with no real individuals involved.
What this actor does
- Generates any volume of profiles in one run, each one an independently generated fictional person.
- Gender filter — male, female, or a mix of both.
- Nationality filter — restrict generated profiles to one or more supported countries.
- Optional extras — toggle profile pictures on/off, and optionally include a generated username plus hashed (never plaintext) password.
- Fields that aren't requested or that a given profile doesn't carry (e.g. coordinates when the location has none) are omitted rather than returned empty.
Output per profile
fullName,firstName,lastName,title— name components, with a salutation title (e.g. Mr, Ms)genderemail,phone,cellnationality— ISO country codedateOfBirth,agestreetAddress,city,state,country,postcodelatitude,longitude— generated location coordinatestimezonepictureUrl,pictureThumbnail— whenincludePictureis onusername,uuid,passwordMd5,passwordSha256— whenincludeLoginis on (only hashed password forms are ever returned, never plaintext)registeredDaterecordType— alwaysuser_profilescrapedAt
Input
| Field | Type | Default | Description |
|---|---|---|---|
count | integer | 100 | How many profiles to generate (1–5000) |
gender | string | any | any, male, or female |
nationalities | array | [] | ISO country codes to restrict generation to (AU, BR, CA, CH, DE, DK, ES, FI, FR, GB, IE, IN, IR, MX, NL, NO, NZ, RS, TR, UA, US); empty = any |
includePicture | boolean | true | Include pictureUrl/pictureThumbnail |
includeLogin | boolean | false | Include generated username, uuid, and hashed password fields |
Example: 500 generic test profiles
{"count": 500}
Example: female profiles from a set of European nationalities
{"count": 200,"gender": "female","nationalities": ["DE", "FR", "ES", "NL"]}
Example: login-ready test accounts without pictures
{"count": 50,"includePicture": false,"includeLogin": true}
Use cases
- QA test data — seed a staging database with realistic-looking users without using real personal data.
- UI/UX mockups — populate design prototypes with varied names, photos and addresses.
- Load testing — generate large batches of synthetic accounts for registration/login flow testing.
- Demo environments — fill a sales demo with plausible-looking sample users.
- Anonymization reference data — use generated profiles as stand-ins when documenting data models.
FAQ
Are these real people? No. Every profile is synthetically generated and does not correspond to any real individual, email address, or phone number.
Is the password field a real, usable password?
No — passwordMd5/passwordSha256 are generated hash values for test purposes only; there is no corresponding plaintext password and these fields aren't tied to any real account.
Can I get only one nationality?
Yes — set nationalities to a single ISO code, e.g. ["US"], to generate only US-styled profiles.
Why are latitude/longitude sometimes missing?
They're omitted when the generated location data didn't include coordinates for that profile.
Can I generate a mix of genders in one run?
Yes — leave gender set to any (the default) to get a mix of male and female profiles.
Is this data usable for production accounts? No — this is test/demo data only and should not be used to create real user accounts or sent to real third-party services.
Does the actor require any login or API key? No — generation requires no authentication of any kind.