Productivity

Fixture rows. example.com emails. Not a production dataset.

Pick 1–100 rows and CSV / TSV / JSON. Names come from a short in-page list; emails use example.com / test.dev; phones use 555- patterns. This is not Faker.js, not census data, and not a password manager. Collisions happen — regenerate.

Columns: first_name, last_name, email, phone, company, job_title, address, city, state, zip, username, password. Phones use fictional 555-style patterns; emails use reserved-style domains — not for real outreach.

When to use this — and when not to

Use it for UI mocks, seed CSVs, and “give me 25 rows” fixtures. Columns: first/last, email, 555-phone, company, title, US-looking address, username, placeholder password. Cap is 1–100. Formats: CSV, TSV, JSON.

Do not treat this as Faker, census data, or a password manager. Emails use example.com / test.dev / similar. Do not mail them. Do not load them into production CRM.

What the generator actually does

Math.random() over short in-page arrays (first names, last names, ten US cities, ten job titles). Collisions are expected. Row count and format may persist in localStorage. Nothing is sent to DroidXP.

Worked example

Count 2, JSON — you will see something in this shape (values change each click):

[
  {
    "first_name": "Alex",
    "last_name": "Patel",
    "email": "alex.patel042@example.com",
    "phone": "555-381-2044"
  }
]

Pretty-print with a local JSON tool if you want; the noindexed JSON formatter on this site is a utility, not the publication.

Mistakes people make

  • Importing rows into a live mailing list.
  • Reusing placeholder passwords on real accounts.
  • Assuming uniqueness — the dictionaries are small.

Related

Regex tester · About

Frequently asked questions

Real people?

No. Built-in word lists and random digits.

Uploaded?

No. Generation is in this tab.

Row cap?

100, so the page stays usable.

Locale coverage?

US-looking cities and English given names. Not a locale pack.