Fake JSON Data Generator

How the Fake JSON Data Generator works

Each row in the field list becomes a property in every record. The generator combines built-in lists of first names, last names, street names, made-up town names, companies and job titles, so the data looks realistic but is clearly fictional: email addresses use example.com and example.org, which are reserved for documentation; phone numbers use the 555-0100 to 555-0199 range set aside for fiction; IP addresses come from the documentation ranges 192.0.2.x, 198.51.100.x and 203.0.113.x; and URLs point at the example domains.

Name, email and username fields in the same record belong to the same person, so a record with Liam Chen has an email such as liam.chen@example.com. ID fields count up from 1. Integer, decimal and date fields use the range in the Setting box (min..max), and "One of a list" picks from comma-separated values. Dates are written as YYYY-MM-DD and date-times as ISO 8601 in UTC. Values are chosen with your browser's secure random generator, and the JSON is built with the browser's own JSON serializer.

How to use the Fake JSON Data Generator

1. Review the example fields. Change a field name or type, select Add field for a new one, or select Remove to delete one.
2. For integer, decimal and date fields, enter a range such as 1..100 or 2020-01-01..2025-12-31 in the Setting box. For One of a list, enter values separated by commas.
3. Set the number of records (1 to 1,000), and optionally a key to wrap the array in, such as users. Untick Pretty print for minified JSON.
4. The JSON updates as you edit. Select Generate JSON, or press Ctrl + Enter (Cmd + Enter on a Mac), for a new set of values.
5. Copy the JSON or download it as a .json file.

Example

With the fields id (ID), name (Full name), email (Email), plan (One of a list: free, pro) and createdAt (Date and time), 2 records, wrapped in the key users:

{
  "users": [
    {
      "id": 1,
      "name": "Sofia Sato",
      "email": "sofia.sato88@example.org",
      "plan": "pro",
      "createdAt": "2023-09-04T19:18:36Z"
    },
    {
      "id": 2,
      "name": "Liam Chen",
      "email": "liam.chen@example.com",
      "plan": "free",
      "createdAt": "2025-04-22T19:16:01Z"
    }
  ]
}

Common use cases

• Building a mock API response so front-end work can start before the back end is ready.
• Creating fixtures for unit tests, Storybook stories or end-to-end tests.
• Filling tables, lists and pagination in a prototype with realistic-looking records.
• Testing JSON imports, converters and validators with hundreds of records.

Common errors and how to fix them

Add at least one field

The schema is empty, so there is nothing to generate. Add a field and choose the type of value it should hold.

The generated values look wrong for my domain

Values follow the field type you pick, so choose the closest specific type rather than a generic string. Names, email addresses and countries are drawn from built-in lists.

Can this data be used as sample production data?

No. Every value is assembled at random and describes no real person, address or account. Keep generated data clearly separated from real data so the two are never confused later.

Frequently asked questions