Log In Sign Up Free

🎭 Fake Person Generator

Generate realistic-looking fake identities for testing forms, demos, and QA. 40+ locales, one-click regenerate. 100% client-side — nothing uploaded.

⚠ FAKE DATA — for testing only. Do NOT use these identities for identity theft, fraud, impersonation, bypassing KYC / age verification, or any activity that harms real people. All data is randomly generated in your browser. SSN reserved blocks (000-xx-xxxx, 666-xx-xxxx, 9xx-xx-xxxx) are filtered out. Credit card numbers pass the Luhn check but are not linked to any real account.
Options
👁️ Sensitive fields are hidden. Click the eye icon next to SSN, card number, or CVC to reveal that field individually. Useful when screen-sharing so no one glances and thinks it's real.
⚙️
Loading Faker library…
Copied

About Fake Person Generator

Fake Person Generator creates a complete, realistic-looking fake identity in one click — name, address, phone, email, date of birth, SSN, credit card, employment, physical characteristics, and more. Designed for developers testing forms, QA testers seeding databases, designers filling mockups with plausible content, and anyone who needs demo data that doesn't look like John Doe / Jane Doe / 555-1234.

Powered by the industry-standard Faker.js library (self-hosted at 1.5 MB), the tool supports 40+ locales — so you can generate authentically-formatted identities for the United States, Germany, Japan, Brazil, Nigeria, and many more.

100% client-side: everything runs in your browser via the self-hosted Faker.js library. Nothing is uploaded, nothing is logged, and every generated identity exists only in your tab.

How to use

1

Pick options

Choose a gender (random / male / female) and a locale for the identity's country of origin.

2

Click Generate

Get a complete fake identity instantly.

3

Copy what you need

Each field has its own Copy button. Or grab everything as JSON, text, or a downloadable vCard.

4

Tick the reveal box for sensitive fields

SSN and credit card are masked by default. Check "Reveal sensitive fields" once you've confirmed you understand this is fake test data.

Key Features

Complete fake identities

Every generation gives you ~25 fields grouped into: Identity (name, gender, mother's maiden name) · Address (street, city, state, ZIP, country, GPS coords) · Personal (SSN, DOB, age, zodiac, height, weight, blood type) · Contact (phone, email, website) · Online (username, password, user-agent) · Finance (credit card + expiry + CVC, UPS tracking, Western Union MTCN, MoneyGram MTCN) · Employment (company, occupation) · Other (favorite color, vehicle, GUID).

40+ locales

English (US, UK, AU, CA, IE, IN, NG, ZA) · Spanish (ES, MX) · Portuguese (BR, PT) · German (DE, AT, CH) · French (FR, CA, CH) · Italian · Dutch (NL, BE) · Scandinavian (SV, NB, FI) · Slavic (PL, CZ, SK, RU, UK) · Turkish · Chinese (CN, TW) · Japanese · Korean · Vietnamese · Indonesian · Persian · Arabic · Hebrew · plus more. Names, streets, phone formats, and postal codes all match the locale.

QR code with vCard

Each identity gets a scannable QR code encoding a standard vCard. Scan it into your phone Contacts to auto-import for realistic seeded contact-app testing.

Sensitive-data reveal gate

SSN and credit-card number are masked by default. Ticking the "Reveal sensitive fields" checkbox (which requires acknowledging this is test data only) unmasks them. Protects against accidental screen-share leaks that look like real data.

Filtered SSN blocks

SSNs are formatted like real ones but the tool refuses to output the reserved administrative blocks (000-xx-xxxx, 666-xx-xxxx, 9xx-xx-xxxx) that the SSA has never issued. Makes it clear the output is test data even when full-length.

Luhn-valid credit cards

Card numbers pass the Luhn checksum so they'll be accepted by client-side card validators — perfect for testing checkout flows. But they aren't linked to any real account or issuer, so they'll always fail at the actual payment network.

Copy any field

Each field row has a "Copy" button. Plus "Copy all as JSON", "Copy all as text", and "Download vCard" for the whole identity at once.

Common Use Cases

  • Testing user-registration forms with realistic input
  • Seeding development databases with plausible data
  • Filling design mockups with more variety than "John Doe"
  • QA testing checkout flows with Luhn-valid card numbers
  • Load-testing signup endpoints with locale-varied identities
  • Demoing internal tools without exposing real customer records
  • Testing phone validators for country-specific formats
  • Building GDPR-safe screenshots that don't require pixellation
  • Testing i18n layouts with names that break assumptions (long, non-Latin, apostrophes)

Security & Privacy

  • 100% client-side: Faker.js runs in your browser. Nothing about your session or the generated identity leaves your device.
  • No real people: data is combined from statistically-representative distributions but never derived from real records.
  • SSN safety: reserved administrative blocks are filtered out so accidental collision with a real SSN is astronomically unlikely.
  • Credit card safety: Luhn-valid but not tied to any account. Real payment networks will always reject them.
  • Ethical use: this tool is for testing, QA, and demos. Do not use it for identity theft, fraud, impersonation, bypassing KYC or age gates, or any activity that harms real people. Both federal law (in most jurisdictions) and toolspow.com's terms prohibit misuse.
  • Reveal gate: sensitive fields (SSN, credit card) are masked by default so a casual screen-share won't leak them by accident.
  • Attribution: uses Faker.js (MIT-licensed).

Frequently Asked Questions

No. All identities are randomly assembled from statistically-representative lists (common first names, common last names, real city/ZIP combos for the locale). No output is derived from a real person's records. That said, with billions of possible combinations, extremely rare coincidental matches with a real person's name and city are statistically inevitable — don't assume any specific identity is truly unique.
For testing forms, QA, seeding dev databases, filling mockups — yes, universally. For impersonation, fraud, identity theft, bypassing KYC / age verification, or providing false info to a real service — no, that's a crime in most jurisdictions. Use responsibly.
It'll pass client-side Luhn validation (frontend "is this a valid card number?" checks). It will always fail at the payment gateway because it's not tied to any real card issuer. Useful for testing your checkout UI's validation and error handling — not for actual purchases.
Two reasons: (1) if you're screen-sharing while testing a form, you don't want a visible 9-digit "SSN" flashing that looks real to a viewer glancing at your screen. (2) The one-click confirmation gate makes people pause and think about whether they actually need the raw number. Tick the "Reveal sensitive fields" checkbox to show it in full.
v1 is single-identity + regenerate. Bulk mode (10 / 50 / 100 identities exported as CSV or JSON) is on the roadmap. For now, click "Regenerate" repeatedly and use "Copy all as JSON" to accumulate — or run faker directly in Node.js for programmatic bulk generation.
Yes — names, addresses, phone formats, ZIP codes, company names, and even street types (Straße, Rue, Chome) match the chosen locale. Some fields (credit card, GUID, UPS tracking) are format-universal and don't change with locale.
Yes — no signup, no ads, no rate limit.