Dev
Mock User Data Generator
Auth flows need user objects with UUIDs and roles. Frontend dashboards need arrays of users to populate tables before the backend exists. Integration tests need consistent, structured records to reproduce bugs. The mock user data generator handles all three: set a count, choose JSON or CSV, and get complete fake user profiles ready to paste into your fixture file, seed script, or API client. Each generated user includes a UUIDv4 as the primary key, a full name, an email address, an age, a role (admin, user, moderator, editor, or viewer), and an ISO 8601 creation timestamp spread across the past three years. The format selector determines the output shape — JSON produces a formatted array of objects ready for a seed script or Postman collection variable; CSV produces a header row followed by data rows, directly importable via PostgreSQL's COPY command or MySQL's LOAD DATA INFILE without any pre-processing. Count goes from 1 to 20 per batch. All fields are entirely fictional. The UUIDs are properly formatted v4 identifiers, emails are syntactically valid but have no live inbox, and names do not correspond to real people. Safe for staging environments, client demos, and public repos.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Set the count field to the number of fake user profiles you need, from 1 up to your desired batch size.
- Choose JSON for API testing, seed scripts, and Postman fixtures, or CSV for spreadsheet imports and database COPY commands.
- Click Generate to produce the full set of user profiles with UUIDs, names, emails, ages, roles, and timestamps.
- Copy the output and paste it directly into your fixture file, database import tool, or API client.
Use Cases
- •Seeding a local PostgreSQL development database with 50 varied user rows via COPY or a seed script
- •Populating a React admin dashboard with fake user table data before the backend API is ready
- •Testing JWT authentication endpoints in Postman that require valid user objects with UUIDs and roles
- •Generating a CSV import file to stress-test a bulk user upload feature in a staging environment
- •Mocking role-varied user arrays in Storybook component stories to validate RBAC permission UI states
Tips
- →Generate a batch of 3-5 users first to confirm the output structure matches your schema before scaling to larger counts.
- →When seeding a relational database, generate users first and note the UUIDs — use them as foreign keys in related mock tables.
- →CSV output includes a header row, so you can import it directly into pgAdmin's import tool or Google Sheets without editing.
- →For RBAC testing, generate two separate batches and manually set one batch's role to admin so you have a clean split for permission tests.
- →Paste JSON output into JSONLint or your editor's JSON formatter before importing — catching malformed output early prevents confusing test failures.
- →If your frontend uses pagination, generate 50+ users and slice the array in your seed script to simulate realistic multi-page data sets.
FAQ
what fields does the mock user data generator include
Each generated user includes a UUIDv4 as the ID, a full name, an email address, an age between 18 and 65, a role (admin, user, moderator, editor, or viewer), and an ISO 8601 creation timestamp spread randomly across the past three years. These cover the fields most commonly expected by authentication systems and user management APIs.
can I use the generated user data in a public staging environment or demo
Yes — all names, emails, and identifiers are entirely fictional and randomly generated, so no real personal data is involved. Avoid importing the data into any system that sends outbound email or SMS, since generated addresses may accidentally match real inboxes.
how do I import mock user data CSV into PostgreSQL or MySQL
Select CSV from the format dropdown, generate your users, then copy the output into a .csv file. PostgreSQL accepts it via the COPY command: \copy users from 'file.csv' with csv header. MySQL accepts it via LOAD DATA INFILE. Both commands read the header row automatically so column mapping requires no extra configuration.
how do I test role-based access control with the generated data
Generate two separate batches: one small batch where you manually set the role to admin in the copied JSON, and one larger batch with default role values for regular users. Use the admin batch to verify privileged actions are allowed and the user batch to confirm they are blocked. The role field in the output takes one of five values: admin, user, moderator, editor, or viewer.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.