b2KIT

Fake Data Generator

Generate realistic fake data (names, emails, addresses, dates) in JSON, CSV, or SQL format.

Tested tool guide Tested browser tools Checked August 16, 2026

What Fake Data Generator does and how it behaves

Fake Data Generator produces synthetic records containing data-shaped values such as names, email addresses, postal addresses, and dates, then expresses those records as JSON, CSV, or SQL. It is useful when an application, import flow, or database needs plausible input without copying real people's details. The important surprise is that realistic-looking does not mean real, verified, deliverable, unique, or mutually consistent. Treat every generated value as a test fixture and inspect the selected format before using it in code or a database.

How the result is produced

1

Synthetic record construction

For each requested record, the generator fills the selected data categories with synthetic values, such as a name, email address, street address, or date. Those values are meant to resemble common application data. They should be treated as independent test material unless the displayed result clearly shows a relationship between fields, such as an email derived from a generated name.

2

Format-specific output

The output choice changes serialization, not the fact that the records are fabricated. JSON is suitable for fixtures and API bodies, CSV represents tabular rows and requires careful handling of commas, quotes, and line breaks, and SQL is intended for database seeding. Before running SQL, compare its table, column, identifier, and literal syntax with the target database and schema.

Good uses

  • Populate a development database with disposable customer-shaped records while keeping names, addresses, and contact details separate from production data.
  • Create JSON fixtures for testing an API endpoint, form workflow, search screen, pagination component, or record-list interface.
  • Produce a CSV or SQL dataset for checking import mappings, required columns, date handling, quoting behavior, and test migrations.

Limits and checks

  • Generated names, addresses, and emails are values generated for testing, but they may coincide with a real person, mailbox, domain, or address. Their appearance does not establish that a person, mailbox, domain, or deliverable location exists.
  • Do not assume values are unique, repeatable between generations, or relationally consistent unless the generated result and available settings explicitly demonstrate those properties.
  • Check CSV delimiters, headers, quoting, encoding expectations, and date interpretation before importing. Review SQL identifiers, column order, escaping, and database-dialect compatibility before execution.

Common questions

Can I use the generated email addresses or postal addresses as real contact data?

No. A generated email address can have valid-looking syntax while its domain or mailbox is absent, unrelated, or controlled by someone else. A generated street address can also resemble a deliverable location without being one. Do not send messages, ship items, make identity decisions, or use generated records as evidence about a person.

Which output format should I choose?

Use JSON when the consumer expects structured values, CSV for a flat table accepted by spreadsheet or import software, and SQL only when you intend to review and execute database statements. CSV does not preserve rich types by itself, and SQL compatibility depends on the target schema and database dialect, so neither should be treated as universally portable.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools