Fake Identity Generator for Database Seeding

Populate a database with thousands of realistic, fictional records ready to load straight in.

Switches to that country's generator page.

Illustrated avatar, not a real person

Your random person

Leah C. Greenfelder

5701 Cemetery Dr, Allentown, PA 18101

Fictional test data. Not a real person.

Personal

SexFemale
Geo coordinates40.57328, -75.48751

Phone

Phone835-555-0148
Country codeUS

Birthday

BirthdaySeptember 16, 1950
Age75 years old
Tropical zodiacVirgo

Online

Email addresslgreenfelder74@example.org
UsernameLeahGree527
PasswordICF3Y7UWY8
Websitenew-goodwill.us
Browser user agentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Physical

Height5' 7" (170 cm)
Weight184.5 pounds (83.7 kg)
Blood typeO-
Hair colorBrown
Eye colorAmber

Tracking numbers

UPS tracking1Z 757 934 39 0568 276 1

Other

Favorite colorgrey
Vehicle2008 Rivian Mustang
License plateWT72KNQ
GUID6fa64084-e21d-41ac-bd3e-e520bb85960f

This is randomly generated fictional data for software testing, QA, and privacy. It does not describe a real person. Any resemblance to a real individual is coincidental.

Empty tables make for unconvincing demos and untested queries. Seeding a database with realistic fictional records lets you test performance, build representative dashboards, and exercise relationships at scale before any real data exists.

The bulk generator exports up to 100,000 records as SQL INSERT statements, CSV or JSON, with the exact fields you choose. Each export mints its own seed, so for a fixture you need to regenerate byte-for-byte in CI, call the JSON API with your own seed instead — the engine underneath is fully deterministic.

How the generator helps with database seeding: Export up to 100,000 records at once; Ready-to-run SQL INSERT statements, CSV or JSON; Pick exactly which fields to include; Deterministic — reproduce the same dataset from a seed.

What a generated identity gives you for database seeding

FieldFormatWhy it's safe
NameLocale-aware first + lastRandomly combined; describes no real person
AddressReal city + valid ZIP, random house #Not verified for delivery; coincidental matches are possible
PhoneValid national formatUS uses the 555-0100…0199 fiction range
Emailname@example-style domainFormat-valid placeholder, not a live inbox
Username & passwordDerived handle + random passwordNo account exists behind them
Birthday & physical detailsConsistent age, height, weight, blood typeRandom draws, not a person's records

Synthetic data for database seeding. Names and street details can match real ones by chance; addresses are not verified for delivery.

Popular generators

Frequently asked questions

What format should I use to seed a SQL database?

Export as SQL INSERT statements to load directly, or CSV/JSON if your tooling imports those. The bulk generator escapes values safely so the SQL is injection-safe.

Sources

  1. ISO 3166 — Codes for country names and subdivisions — ISO
  2. ITU-T E.164 — International telephone numbering plan — ITU
  3. Universal Postal Union — Addressing and postal code standards — Universal Postal Union