A fake data generator creates records that look real but don't describe anyone. Developers and testers need sample data to fill a database, try out a form or demonstrate a product, and using real customer details for that is a privacy risk. Tick the fields that you want, say how many records you need, and this fake data generator builds them in CSV or JSON. You can create up to 5,000 records at once and download them as a file. Every email address uses example.com, a domain reserved for documentation, so a test can't accidentally send a message to a real person.
How to use the fake data generator
- Enter the number of records that you need.
- Choose CSV or JSON.
- Tick the fields to include.
- Press Generate.
- Copy the output or download it as a file.
What each field contains
| Field | Example | Notes |
|---|---|---|
| Name | Mary Patel | Random first and last name |
| mary.patel42@example.com | Always example.com | |
| Phone | (415) 555-0142 | Uses the fictional 555-01xx range |
| Address | 1234 Oak Street, Salem | Invented street and town |
| Company | Patel Labs | Invented business name |
| Date | 2004-08-17 | ISO format, year-month-day |
| ID | a UUID-style value | Random hexadecimal |
Why use example.com?
The domains example.com, example.net and example.org are set aside for use in documentation and examples, and you don't need permission to use them that way. That makes them ideal for test data. Random addresses at real mail providers can belong to real people. If a test system sends a welcome email to one of those, someone gets a message that they never asked for. It can also damage your sender reputation. With reserved addresses, that can't happen.
A worked example
Suppose that you're building a customer table and want to check that the page handles paging properly. Enter 250 records, choose CSV and tick Name, Email and Company. The output begins with a header row of name, email and company, followed by 250 lines of data. Download it and import it into your database or spreadsheet. If you need another set, press Generate again and you'll get different records. For an API mock, switch the format to JSON, and you'll get an array of objects that you can paste into a fixture file.
CSV or JSON?
Use CSV when the data is going into a spreadsheet or being imported into a database table. Each record is one line and it's easy to view. Use JSON if you're working with an API, a front-end project or a test fixture, as it maps straight to objects in your code. Both formats contain the same records, so choose whichever fits the next step in your work.
Common uses for test data
- Filling a development database so that pages look realistic.
- Testing forms and imports with many different values.
- Checking performance with thousands of rows.
- Taking screenshots and making demos without showing customer details.
- Teaching spreadsheets, SQL or data cleaning.
Why not just copy production data?
Real records contain personal details, and copying them to a test system exposes them to more people and to weaker security. Privacy laws in many places also limit how personal data can be used. Made-up records avoid the problem altogether. They also let you share a demo or a bug report freely, as nothing in them relates to a real customer.
Limits to keep in mind
This data looks plausible, but it doesn't model real-world patterns. Names and towns come from short lists, so they'll repeat in large sets. A random combination could by chance match a real person's name or a real address, so don't treat the records as verified. Don't use made-up details to sign up for services, to mislead anyone or to get around identity checks. It's meant for testing your own software.
Testing edge cases
Random records are good at showing how a system copes with volume, but they're less useful for finding unusual bugs. After you import a set, edit a handful of rows by hand. Try a very long name, an apostrophe, an accented letter, an empty field and a date at the end of a month. Those are the values that tend to expose problems with validation and with database columns that are too short. Keep this edited file with your project so that you can run the same checks after every change, and compare the results over time.
Common mistakes
- Expecting every value to be unique. Add your own check if your database needs it.
- Testing only with neat data. Add a few awkward values by hand too, such as very long names.
- Leaving test records in a live system. Delete them before launch.
Related developer tools
Convert your output with the CSV to JSON converter, go the other way with the JSON to CSV converter, and break a large export into parts with the CSV splitter.
What next
Use this often? Add Fake Data to your Home screen.
Frequently asked questions
What is a fake data generator for?
It creates made-up records for testing software, filling databases and building demos.
Are the emails real?
No. Every address uses example.com, a domain reserved for documentation.
How many records can I make?
Up to 5,000 at a time.
Can I export to JSON?
Yes. Choose CSV or JSON before you generate.
Is the data unique?
Not always. Names come from short lists, so they can repeat.
Sources
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.