9314JIUsi
Test data · Local generation

Random Names, Emails, Phones, Addresses — 200 Records a Tap

Stop hand-typing fake users into signup forms. Each record arrives fully assembled: name, email, phone, street address — ready to paste into fixtures, demos and QA runs.

Console

1–200 records
First names only; surnames shared
Phone and address follow the country
Defaults to example.com (RFC 2606 test-reserved)
Same seed, same batch — replayable data

Everything runs in this browser only — nothing is uploaded, no account needed. Settings (count, domain, seed) stay in this device's localStorage; clearing site data or switching devices loses them. The footer button wipes them.

Output belt

No records yet

      
      
      
    

Why fake data at all

Last month I typed my real phone number into a staging signup form seven times to test a validation fix. The insurance spam calls started two days later. Lesson learned the annoying way: never burn real details on test runs, even for an internal demo.

This page assembles the four essentials per record: names drawn from 400+ common male names, 640+ female names and 249 surnames, all inlined and offline-capable; emails default to example.com, the RFC 2606 test-reserved domain that can never reach a real inbox; phones use the North American 555 block (reserved for fiction, never assigned); addresses combine random street numbers, cities and postcodes.

Seeds: your teammate sees the same batch

The classic pain with random data is "my record #17 differs from yours". Type a seed like demo-0817 and both sides generate identical output, because the generator (xorshift128) is pinned by that seed — same seed, same sequence. Seeds shine in bug reports: "seed demo-0817, record 3 fails email validation" — reproduction cost drops to zero.

Three exports, three consumers

JSON parses straight into an array of objects with fields first/last/gender/email/phone/street/city/state/zip. CSV ships with a UTF-8 BOM so Excel opens it cleanly. Plain text gives one line per person for quick eyeballing. I have watched someone hand-type fake records from a screenshot into a fixture file and transpose two ZIP digits — do not be that person.

InputCount 1–200 (default 50); gender mixed/male/female; country US/UK; email domain up to 60 chars (invalid characters stripped); seed up to 40 chars or empty
OutputJSON array (9 fields) / CSV (with BOM) / plain text (one line per person) / in-page table view; clipboard copy or file download
DefaultsCount 50; gender mixed; US format; domain example.com; seed empty (true random); ?n=&g=&c=&d=&seed= URL params prefill the form
ProcessingBrowser-local: inlined name banks (~9KB) + xorshift128 random sequence, zero requests zero uploads; settings stored in this browser's localStorage only
Limits200 records per run; banks hold 404 male / 639 female / 249 surnames; domain ≤60 chars; seed ≤40 chars
Known boundsRecords are randomly assembled, map to no real individuals, but common combinations like James Smith exist in the wild by coincidence; phones and postcodes are format-valid but not dialable; no non-Latin name generation

FAQ

Are these records about real people?

No. Names, phone numbers and street addresses are randomly assembled from built-in word banks; number ranges and street numbers are invented and do not map to real individuals. Emails default to the example.com domain — reserved for testing by RFC 2606, so nothing can ever reach a real inbox.

What does the seed do?

The same seed (any short string) regenerates the exact same batch. Use it so a teammate can reproduce your dataset bit-for-bit: same seed, same 50 records. Leave it empty for true randomness every run.

How many records can I generate at once?

200. That is plenty — test data earns its keep by covering scenarios, not volume. If you need hundred-thousand-row loads for stress tests, reach for a dedicated data factory instead.

Why does the CSV open cleanly in Excel?

The exported file starts with a UTF-8 BOM, which Excel reads automatically — no garbled columns on double-click. Older Excel builds that still misread it can use Data, From Text and pick UTF-8.

What is the difference between US and UK format?

Phones and regions. US records use (555) 123-4567 style numbers, 5-digit ZIPs like 90210 and two-letter states like CA. UK records use 07xxx xxxxxx mobiles, alphanumeric postcodes like SW1A 1AA and counties like Kent. Street suffixes differ too: Street/Blvd vs Lane/Close.

Is anything uploaded to a server?

No. Generation, assembly and export all run inside this device's browser — zero uploads, zero requests. Settings live only in this browser's localStorage and will not follow you to another device; the footer button clears them in one click.