Dummy JSON data generator

Create reproducible demo records with fictional labels and example addresses.

Your files are processed here, on your device

We do not send your file or text contents to a processing server. No account is needed and there is no daily operation quota. Individual tools have size limits to protect your device’s memory.

A connection is needed to load the site and its resources. Hosting may receive technical visit data. Favorites store only tool identifiers in this browser.

How we handle your data →

How to use this tool

  1. Choose 1–1,000 records.
  2. Enter an integer seed to reproduce the sample.
  3. Generate, inspect the schema, then copy or download JSON.

An example you can verify

Prepare three demonstration records without entering personal data.

Example input

Count: 3. Seed: 42.

SettingsFixed schema: id, name, email, score and active.

Expected result

Three JSON objects. The first has id 1, name "Demo 001" and email "[email protected]".

Matching seed and count reproduce the entire sample. score and active are synthetic values rather than real people or measured results.

Dummy JSON data generator: uses and practical guidance

Dummy data helps test a table, import routine or interface without using personal records. This generator creates JSON objects with a fixed schema: id, name, email, score and active. Names are numbered Demo labels, and email values use example.com, a domain reserved for examples. No contacts, accounts or external services supply the data. The sample is intended to show column, filter and state behavior rather than represent real people or a measured statistical distribution. Keep its demonstration purpose clear when using the output in screenshots or shared test documents.

Count determines the number of objects. Identifiers start at one, and labels use at least three digits for readability. Score is a synthetic integer from zero through one hundred, and active is a boolean. These columns mix strings, numbers and booleans to help check whether an importing interface respects types. Postal addresses, telephone numbers, dates and passwords are not generated. Edit a copy of the JSON or use a generator designed for another schema when additional fields are needed, rather than assigning real-world meanings to the supplied demonstration fields.

The seed reproduces a sample exactly. Matching count and seed produce the same objects in the same order. Changing seed alters synthetic score and active values without changing numbered labels or identifiers. The procedure is deterministic and does not provide cryptographic randomness. Do not use its values for credentials, drawings or decisions requiring a secure random source. For reproducible testing, retain seed, count and schema version together so the origin of data in a screenshot or error report can be explained. This also helps distinguish a changed interface from a test that happened to use different generated input.

Supported settings are one through one thousand records and integer seeds from zero through 4,294,967,295. Output is an indented JSON array available to copy or download without sending it to a server. For CSV, save JSON and continue with the corresponding conversion tool. Check how the destination interprets booleans and codes before declaring an import correct. Separately generated samples can repeat names and identifiers, so combining them does not create global uniqueness. Email values are example strings; the tool does not create accounts or guarantee delivery. Clearly label test data in demonstrations, retaining the original generated file when exact reproduction of a reported behavior is needed.

Settings and limits

Choose 1–1,000 records and an integer seed from 0 to 4,294,967,295. Every record includes id, name, email, score and active. Addresses use example.com and do not represent real accounts. Matching count and seed produce the same JSON. This is not for passwords or cryptographic randomness.

Frequently asked questions

Can I choose the columns?

This version uses a fixed testing schema. Edit generated JSON or convert it using JSON to CSV.

Guides