Dummy JSON Generator
Print a JSON array of invented objects for mocks. These are not real people. Emails use the example.test domain.
Rated 4.7 out of 5 based on 428 reviews
How to generate sample JSON
- Set Rows from 1 to 200. That is how many objects land in the array.
- List field names, separated by commas or new lines. Known keys get typed values. Unknown keys get short filler text.
- Generate. The output is pretty-printed JSON with two-space indent.
- Paste into a mock server or a test. Do not treat names or emails as real contacts.
Dummy JSON records
Pretty-printed array of invented objects
| Format | JSON array, two-space indent |
|---|---|
| Known fields | id, name, email, city, age, status, score, first, last |
| Email domain | example.test, not a working inbox |
| People | Invented first and last names from a small list |
| Rows | 1 to 200 objects |
| Not production data | No census, CRM export, or live users |
A pretty JSON array
The result is one JSON array. Each element is an object whose keys match the field list you typed. Indent is two spaces so you can read it in the box. The page does not minify. It does not wrap the array in an extra data key. Copy the whole output, including the square brackets.
Known fields and invented values
id is 1, 2, 3 in row order. name is an invented first and last pair. first and last split that idea. email looks like a mailbox but always uses @example.test, a domain reserved for examples. city picks a city label from a tiny list. age is an integer in a working-age band. status is active, pending, or closed. score is 1 through 100. Any other field name gets a short dummy sentence with the period stripped.
Not real people
Names come from a small invented pool. Matches to a living person are coincidence, not a scrape. Do not use this output as a mailing list. For a plain column of names without JSON syntax, use dummy names. For the same rows as a table file, use dummy CSV.
JSON mocks versus CSV mocks
Pick JSON when a client expects [{...},{...}]. Pick CSV when a spreadsheet or a bulk import wants a header row. Both pages share the field list idea. They do not share output shape. JSON preserves types: id and age are numbers, not quoted strings. Nested objects and arrays are out of scope. Keep the mock flat.
When you need prose instead
Field values that are not in the known list become short filler clauses. For full paragraphs of lipsum, switch to lorem ipsum. Mix the two in a design: JSON for a table component, lorem for a sidebar.