How the rows are built
The generator picks from 14 fields: id, uuid, firstName, lastName, fullName, email, username, phone, age, city, country, company, jobTitle and active. Each row is assembled from small built-in lists, so the values are plausible but obviously fictional. Related fields within a row agree with each other: a row with the first name Ava and last name Khan has fullName "Ava Khan" and an email beginning ava.khan.
| Field | How the value is made |
|---|---|
id | Sequential: 1, 2, 3 and so on |
uuid | A random version 4 UUID from crypto.randomUUID() |
email | first.last at example.com, example.org or example.net; a number is added (ava.khan2) if the address was already used in the run |
username | Lower-case first name plus a number from 1 to 999, made unique within the run |
phone | The format +1-XXX-555-01YY: an area code from 201 to 989 and a number in the reserved fictional range 555-0100 to 555-0199 |
age | Whole number from 18 to 75 |
active | true or false with equal odds |
Worked example
Selecting id, fullName, email and city with 2 rows and the JSON format gives an array of two objects, shaped like this (the names, domains and cities differ every time):
[
{ "id": 1, "fullName": "Ava Khan", "email": "ava.khan@example.com", "city": "Lima" },
{ "id": 2, "fullName": "Leo Rossi", "email": "leo.rossi@example.org", "city": "Berlin" }
]Choosing CSV instead gives a header line id,fullName,email,city followed by one line per row. A value is wrapped in double quotes only when it contains a comma, a double quote or a line break. Columns always come out in the order of the checkbox list, not the order you ticked them. The row count is capped between 1 and 1,000.
Limits to plan around
- It is random, not seeded. There is no seed option, so the same click never reproduces the same data. Save the output if you need a fixed fixture for a test.
- Names repeat, emails and usernames do not. There are 50 first names and 50 last names, so only 2,500 distinct full names exist and a large run will repeat some.
emailandusernameare made unique within one run by adding a number when needed (ava.khan, ava.khan2, ...), so they are safe for a unique-constraint column. Separate runs can overlap, andidrestarts at 1 each time. - Addresses are safe to use in tests. Every email uses example.com, example.org or example.net, domains reserved by RFC 2606 for documentation, so mail to them goes nowhere. They are still not real inboxes, so use them for display and database tests rather than sign-up flows that send a confirmation.
- Phone numbers are fictional. They follow a US-style format and always end in 555-0100 to 555-0199, the range set aside for fiction. The area code is random.
- Names and places are English-centric, with a few international entries, and every phone starts with +1 whatever the country.
For a single identifier, use the UUID generator. For filler prose rather than records, try the Lorem Ipsum generator, and paste the result into the JSON formatter or convert it to a table with JSON to CSV.