Bulk fake data generator — test records as a CSV table

Tick the columns you need, choose US, UK or Indian style, and the tool builds up to 1,000 rows of clearly fictional test records that you can copy or download as fake-data.csv.

Live demo · real result from this tool

Press Generate to create a result.

Processed on your device — nothing is uploaded.

How to use the bulk fake data generator

  1. Choose the Data style: United States, United Kingdom or India. It sets the names, address layout and phone ranges.
  2. Set the number of Rows, from 1 to 1,000 (25 by default).
  3. Tick the columns you want: Name, Email, Phone and Address are on by default; Company and Date of birth are off.
  4. Press Generate, then copy the table or download it as fake-data.csv.

What it does and when to use it

Development and test environments should not hold copies of real customer data. Privacy rules discourage it, and a leak from a test server is still a leak. This tool gives you rows that look like a customer list but describe nobody, so you can fill a staging database, try an import, test a CRM, build a mail-merge template, or teach spreadsheet skills.

Every row has a numeric ID starting at 1, which helps when you import into a table with a primary key. If you only need one field, the single-purpose tools give more control: the fake name generator offers name formats and gender, the fake address generator builds full one-line addresses, and the fake date generator handles any date range and format. For login data, add passwords from the bulk password generator.

How it works

Each row is built from random choices made with crypto.getRandomValues:

  • Name: a first name and a surname from lists for the chosen country, with first names drawn evenly from female and male lists.
  • Email: first.last@ the name, at example.com, example.org or example.net.
  • Phone: a US 555-01xx number or a UK Ofcom drama number, in national format.
  • Address: street, city, region, postcode and country, built the same way as the address generator.
  • Company: a word and a suffix, such as “Brightpath Ltd”.
  • Date of birth: a random day 18 to 80 years before today.

Worked examples

  • Defaults, US style. The header reads ID | First name | Last name | Email | Phone | Street | City | Region | Postcode | Country. One run gave Luke | Clark | luke.clark@example.org | (294) 555-0161 | 5726 Elm Place | Columbus | OH.
  • UK style with Company and Date of birth, no Email. The table ends with Country | Company | Date of birth, and a row looked like Archie | King | 01632 960200 | … | Brightpath Ltd | 1962-11-28.
  • India style. The Phone column disappears and the note says “Phone column left out: India has no reserved fictional number range.”

Limits and tips

  • Name lists are short, so names repeat in large tables. Use the ID column, not the name, as the key.
  • Company suffixes are not matched to the country, so a US row can show “Pvt Ltd”.
  • Label the dataset as test data wherever you store it.

Frequently asked questions

Is any of this data about real people?
No. Names are combined at random from built-in lists of common first names and surnames, and addresses use real towns with random house numbers and postcodes. A combination can still match a real person by chance, so never present a row as someone's actual details.
Can the emails or phone numbers reach anyone?
Emails use example.com, example.org and example.net, which are reserved by RFC 2606 and never receive mail. US and UK phones come from regulator ranges kept for fiction. That makes the data safe for testing sign-up flows and notifications without bothering anyone.
What is this data not for?
It is not for creating fake accounts, getting around identity checks, pretending to be someone else or misleading a business. Using fictional identities that way can be fraud. Use it only for software testing, training, demos and mock-ups.
Why is there no phone column for India?
India has no published range of fictional numbers, so any realistic number could ring a real person. The tool leaves the column out and says so under the table.
How old are the people in the Date of birth column?
Each date is a random day between 18 and 80 years before today, written as YYYY-MM-DD, so every record is an adult.

Written by the ToolsRift team · Last updated

Pages are drafted with AI assistance and checked by automated tests. How we write and check pages.

Was this tool useful?

Report a problem

Start typing to search every tool.

↑ ↓ to moveEnter to openEsc to close