JSON random generator

Processed locally
app.generate.view

You can also load data via #data={"name":"Ada"} or #url=... It is cleared from the address bar after it is read.

Generate test JSON by depth or from a sample shape. For frontend mocks, demo data, or as input to code generation, you do not need to type from scratch. Choose a random structure, or a fixed template such as an API response, package.json, or a ChatGPT request.

Quick placeholders

Start with data that has the right shape, then swap in real fields. Depth and items per level are adjustable so you do not generate huge nesting.

Opening the page generates a sample. After Clear, auto-generation stops until you click “Regenerate.”

Generated locally

Random output exists only on this page. Do not use random strings as security tokens or lottery seeds.

After generating, copy immediately to Format, Schema, or entity generation.

Then use other tools

Format, emit a Schema, or emit entity classes right away. A good first draft for demos and unit-test fixtures.

Building data that strictly follows a JSON Schema needs a dedicated faker pipeline. This page does not solve full constraints.

Example

Shapes you might get
{
  "id": 42,
  "name": "item-7",
  "enabled": true,
  "tags": ["a", "b"]
}
What you can do next
 Format to inspect structure → generate types → use Schema as an API draft. Generated data is only a starting point. 
Is this cryptographically secure random?

Use it for mocks and demos, not as a security token or lottery seed.

Can it generate fully from my Schema?

It follows page options and samples. Strict Schema-based generation needs a dedicated faker pipeline.

Why is it empty after Clear?

Clear stops auto-generation so a new sample does not appear right after you deleted one. Click “Regenerate” for new data.

Templates vs random?

Templates output a fixed structure for demos. Random structure can change each time, which is better for stress-test placeholders.

Recommended workflow

  1. Pick a template or random, then adjust depth / items per level.
  2. Click “Regenerate” until the shape is close to your API.
  3. Copy to the formatter and replace with real field names and enums.
  4. Then generate a Schema or entity classes and add them to tests.

Random JSON only guarantees “there is nesting and types,” not that it matches your business rules.