Fake Identity Generator for Database Seeding

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

Updated

  • 100% fictional
  • Format-valid test data
  • Free, no sign-up

Switches to that country's generator page.

WS

Willie S. Padberg

9478 Lesch Trafficway
Sacramento, CA 95820
United States

Fictional test data — not a real person

Personal

SexFemale
Geo coordinates38.52198, -121.50156

Phone

Phone279-555-0196
Country codeUS

Birthday

BirthdayOctober 4, 1965
Age60 years old
Tropical zodiacLibra

Online

Email addresswpadberg22@example.org
UsernameWilliePa980
Passwordnbe77jF668
Websitepeaceful-sonar.info
Browser user agentMozilla/5.0 (iPhone; CPU iPhone OS 17_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.1 Mobile/15E148 Safari/604.1

Physical

Height5' 0" (153 cm)
Weight193.6 pounds (87.8 kg)
Blood typeB+
Hair colorRed
Eye colorGrey

Tracking numbers

UPS tracking1Z 771 303 73 3221 281 4

Other

Favorite coloryellow
Vehicle2009 Hyundai Spyder
License plateUX18QCU
GUID96cbb5a7-24bd-4182-9913-7032abef78d2

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 #Never resolves to a real residence
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

Every field is fictional and safe to use for database seeding — it describes no real person and cannot collide with a real identifier.

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.

Popular generators

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