Are these real people or real email addresses?

No. The names are drawn at random from a fixed pool of common first and last names, so any full name that looks like someone you know is coincidence. Every email uses a reserved example domain that cannot receive mail, which means a test run that accidentally sends email will not reach a stranger.

Will the CSV survive a comma inside a value?

Yes. Any value containing a comma, a quote or a line break is wrapped in quotes and its internal quotes are doubled, which is what RFC 4180 asks for and what Excel, Google Sheets and every sane parser expect. Values that need no quoting are left bare, so the file stays readable.

Is the SQL safe to run?

The values are escaped by doubling single quotes, numbers are written bare and booleans as TRUE or FALSE, so the statement is valid standard SQL. The table name is stripped down to letters, digits and underscores, because an identifier cannot be quoted safely the way a value can. Read it before you run it against anything you care about.

Why Indian names and cities?

Because most fake data tools produce American names, and a demo full of them looks wrong to anyone building for an Indian audience. The pools here lead with Indian names and cities and keep a mix from elsewhere, which is closer to a real user table and also catches the layout bugs that only show up with longer names.

Is the data generated on a server?

No. It is assembled by JavaScript on this page using your browser's own random number generator. Nothing is uploaded, logged or stored, and the page keeps working with your connection switched off. Reload and you get a completely different batch.

Random Data Generator

About this test data

Good test data is boring data that holds together. A row where the email has nothing to do with the name will pass every test you write and then hide the one bug that matters, because you stop believing what you are looking at. Here the email is derived from the name in that same row, the phone numbers are in a real Indian mobile range, and the dates are genuine calendar dates inside the last three years.

All the addresses use reserved example domains, so nothing you generate can reach a real inbox if a staging server ever starts sending mail. The randomness comes from the browser's cryptographic generator rather than Math.random, which matters less for fixtures than for passwords but costs nothing and removes the dull patterns a weak generator leaves behind. When the rows need keys rather than people, the UUID generator will mint up to a thousand at once.

How to generate test data

Tick the Fields you need. The column order in the output follows the order they are listed here.
Set Rows, up to 500 at a time.
Pick JSON for a fixture or an API stub, CSV for a spreadsheet or an import, SQL to paste into a database client.
For SQL, set the Table name to match your schema.
Press Generate again for a fresh batch, then Copy. Switching format keeps the rows you are looking at.