Are these real people?

No. Every field is randomly combined from generic word pools entirely in your browser. The names, addresses, phone numbers, and emails are fictional and any resemblance to a real person is coincidental.

Is the email tied to the generated name?

Yes. The email is derived from the first and last name with a sample domain, so each profile is internally consistent, which is exactly what you usually want for test fixtures.

Can I export the profiles as JSON?

Yes. Use the copy-as-JSON button to grab the whole batch in a structured array, ready to drop into seed scripts, fixtures, or a mock API.

Are the phone numbers callable?

No. Phone numbers use reserved or clearly fictional ranges and formats, so they will not connect to a real subscriber. Use them only as placeholder display values.

Is anything sent to a server?

No. Generation happens fully client-side. No profile data leaves your browser and nothing is stored or logged.

What is the Fake Person Profile Generator?

Generates a full fake person profile including name, date of birth, address, phone, email, and job title. Ideal for populating test databases and demo UIs with realistic but entirely fictional placeholder data. It runs free in your browser on Gera Tools, with nothing uploaded.

Fake Person Profile Generator

Name: Fake Person Profile Generator
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

Get one useful tool a week

Like this tool? Enter your email and we'll send you one genuinely useful Gera tool a week — plus a link to come back to this one. No spam, one-click unsubscribe any time.

Seeding a database or building a demo screen is far easier with believable-but-fake people. This generator produces complete fictional profiles — name, age, address, phone, email, and job — that are internally consistent and safe to use as placeholder data.

How it works

Each profile draws a first and last name from name pools, then derives a matching email such as [email protected] so the record is self-consistent. A date of birth is generated within a realistic age range and the age is computed from it. Address, phone (using fictional ranges), and a job title are picked independently. The whole batch can be copied as a JSON array, ideal for fixtures and seed scripts.

When developers need fake profiles

Unit and integration tests. Most test frameworks discourage using production data in test databases for privacy and reproducibility reasons. Fake profiles give each test run a clean, predictable dataset with no PII.

Demo and staging environments. Sales teams, designers, and QA testers all need to log in and see a realistic application state. Populating a demo environment with ten or twenty coherent profiles — not “Test User 1” through “Test User 10” — makes demos more convincing and catches layout issues with real-length names and addresses.

UI development. A design that looks fine with “John Smith” may break badly with “Bartholomew Achterberg-Visser.” Generating a varied batch up front surfaces edge cases in truncation, avatar initials, and sorting logic before they reach production.

GDPR and data-minimisation compliance. Development and testing environments legally should not contain real customer data. Fake profiles let teams build realistic fixtures without any regulatory exposure.

Load and performance testing. Scripts that simulate concurrent user actions — logins, form submissions, API calls — need unique identifiers per simulated user. Bulk-generated profiles provide realistic seed data for k6, JMeter, or custom scripts.

What internal consistency means here

A generated profile’s email ([email protected]) is derived from the name fields, so the record makes sense as a whole. The age is computed from the date of birth so the two fields always agree. Phone numbers use clearly non-callable formats (e.g. reserved ranges or obviously fictional number patterns) so they cannot accidentally connect to a real subscriber.

Tips for using the JSON output

The copy-as-JSON button produces a plain array of objects you can paste directly into:

Prisma / Sequelize seed scripts — createMany({ data: profiles })
MongoDB seed — insertMany(profiles)
Mock REST API servers (e.g. json-server) — paste as the db.json users collection
Postman environment variables — generate one profile, paste the object as a pre-request script variable to drive dynamic test data

Increase the count before copying to populate a whole table at once, then re-generate when you want a fresh cohort with new names and addresses.