15 field types
Mix and match fields like first/last name, email, phone, address, company, job title, UUID, date, boolean, and number.
Up to 500 rows
Generate as many rows as you need for a realistic test dataset.
Table, JSON, or CSV
View results in a table, or switch to JSON or CSV to copy or download the data directly.
All 15 field types
| Field | Example |
|---|---|
| First name / Last name / Full name | Mary · Jones · Mary Jones |
| mary.jones76@example.com | |
| Phone | (212) 555-0142 |
| Street address / City / State / ZIP code | 742 Evergreen Terrace · Springfield · IL · 62704 |
| Company / Job title | Globex · Product Manager |
| UUID | 3f2b8c1e-9d4a-4e7b-a1c2-5f6e7d8c9b0a |
| Date (last 5 years) | 2024-03-18 |
| Boolean | true |
| Number (1–1000) | 427 |
Tick the fields you need, set the number of rows and press Generate. Use Add Field to build the exact columns your table or form expects.
Using the data: JSON, CSV, Excel and databases
- JSON: paste it into a mock API, a front-end prototype or a test fixture file.
- Excel: download the CSV and open it, or use Data → From Text/CSV for more control over column types.
- Google Sheets: File → Import → Upload → choose the CSV.
- PostgreSQL:
\copy users FROM 'users.csv' WITH (FORMAT csv, HEADER true) - MySQL:
LOAD DATA LOCAL INFILE 'users.csv' INTO TABLE users FIELDS TERMINATED BY ',' ENCLOSED BY '"' IGNORE 1 LINES;
Make sure the column names in your table match the field names in the file (or list the columns in the import command).
Why use fake data instead of real customer data?
- Privacy: copying real customer records into test or demo systems spreads personal data to places with weaker security. Fake data avoids that entirely.
- Safe demos and screenshots: you can show a full dashboard to a client or in a tutorial without blurring anything.
- Better testing: you can generate exactly the volume you need, for example 500 rows to test pagination, sorting and search.
Safe testing tips
- Never send real emails to generated addresses. If your app sends emails during testing, route them to a local mail catcher instead of a real mail server.
- Don’t mix fake and real data in the same database; keep test data in a separate environment.
- Test edge cases too: add a few rows by hand with very long names, apostrophes (O’Brien), accents (José) and empty fields, which random data may not cover.
Need unique IDs or random codes? Use the UUID Generator or the Random String Generator. Checking your JSON? Try the JSON Formatter.
Common Mistakes to Avoid
Using generated data as if it were real people
Solution:
All names, emails, and addresses are randomly generated and do not correspond to real individuals — use only for testing.
Generating too few rows to catch pagination bugs
Solution:
Generate at least 50-100 rows when testing tables, pagination, or performance with realistic data volumes.
Frequently Asked Questions
No — every value is randomly generated from generic name/word lists and does not represent real people or businesses.
Yes — switch to JSON or CSV view and use Copy or Download.
Up to 500 rows at a time. For larger datasets, generate several batches and combine the CSV files, or use a data library in your code.
In Excel, open the downloaded CSV or use Data → From Text/CSV. In Google Sheets, use File → Import → Upload and choose the file. The first row contains the column names.
No. The addresses are made up for filling forms and databases, not for sending mail. If your app sends emails in testing, use a local mail catcher so nothing reaches a real inbox.

