Text & web utilities

Dummy names and email data generator

Create reproducible fictional name and reserved-domain email fixtures in text CSV or JSON format.

Your settings

Calculated on your device. Your inputs aren’t sent to us.

Your result

Ready when you are

Enter your inputs and select Generate result.

Report an issue

Try it, understand it

Explore the result

Use the same seed to compare output formats for the same synthetic records.

Worked example comparison
ExampleOutputWhat to notice
Ten text recordsSynthetic records10A compact name-and-email list is ready to copy.
Two JSON recordsSynthetic records2Stable IDs and reserved-domain emails form a JSON array.
Two CSV recordsSynthetic records2The same seed gives the same names in row form.

Check your understanding

Can these records be used to contact people?

No. They are fictional fixtures using reserved example-domain addresses.

Why do some names repeat?

A limited fictional pool keeps the output clearly synthetic; IDs and emails distinguish records within the batch.

Behind the tool

How this tool works

Generate synthetic records for layout testing, import fixtures or demonstrations. The seed controls the fictional name sequence, while sequential IDs and email suffixes keep records distinct inside the batch. Names intentionally use clearly fictional family labels rather than being presented as harvested user identities.

THE OUTPUT RULESeeded name selection + unique sequential record IDs and example.com emails

A worked example

A ten-record batch has IDs 1 through 10 and emails user000001@example.com through user000010@example.com. Keeping the seed and count unchanged reproduces the same name sequence.

Good to know

Up to 500 records, with a small fictional name pool. Names can repeat. IDs and emails restart in each batch and are not globally unique. No real contact details, deliverability checks, demographic realism or account creation.

Synthetic fixtures should be unmistakably synthetic

A demonstration table needs realistic structure without pretending to contain real people. These records use a small fictional name pool and example.com email addresses. Sequential suffixes make the email values unique within a batch, while the name labels make their sample purpose clear.

The seed controls the name-selection sequence. Keeping it stable helps reproduce a layout bug or compare import behavior after a code change. The CSV to JSON converter provides a separate way to inspect the records in another structured format without retyping them.

Repeatable batches do not create globally unique identities

Every batch starts its IDs and email sequence again, so two batches can contain the same values. This is useful for deterministic fixtures but inappropriate as a production identity system. Names can repeat even within one batch because the pool is intentionally small.

No addresses are fetched from a directory and no verification email is sent. The tool does not claim demographic realism or create accounts. Choose JSON for object fixtures, CSV for row-based imports or text for a simple demonstration list, then check how the receiving system handles fields and encoding.

A few questions, answered

Can these records be used to contact people?

No. They are fictional fixtures using reserved example-domain addresses.

Why do some names repeat?

A limited fictional pool keeps the output clearly synthetic; IDs and emails distinguish records within the batch.

Find your calculator

Start typing to explore the library.