Mock JSON Generator — Realistic Test Data from Schema

Guide

About Mock JSON

Generate mock JSON from preset shapes (user, post, product, address, payment, comment) or define your own schema. Pick item count (1-1000), nesting depth, and whether arrays embed inline. Output is realistic-shaped JSON suitable for stub APIs, fixture files, and Storybook stories.

Why mock JSON shape matters

Real APIs return objects with specific structure — users is an array, user.id is a string, user.address.country is two letters. A hand-rolled mock that gets the structure wrong wastes more time than not having a mock. Generated mocks based on real shapes save the setup tax.

Preset shapes

User — id, name, email, avatar, role, createdAt
Post — id, title, body, author, tags, publishedAt
Product — id, name, sku, price, currency, stock, category
Order — id, status, items[], total, customerId, createdAt
Comment — id, postId, author, body, createdAt
Address — street, city, state, zip, country, lat, lng
Payment — amount, currency, method, status, fees
Event — id, type, source, timestamp, payload

Output options

Array of items — [{...}, {...}]
Single item — {...}
Paginated — { data: [...], page, total, hasMore }
NDJSON — one object per line for streaming consumers

Common workflows

Stand up a stub API. Generate 50 users as paginated JSON, drop into a users.json file, mock-server points at it. Frontend works against fake data while backend is being built.

Fill a Storybook table. Generate 20 row objects, paste into the story file. The grid renders with realistic content.

Stress-test a list view. Generate 1000 items, set as the data prop. Watch your virtual scroller, sort, and filter handle the load.

Schema-first design. Sketch the shape in this tool, get JSON, share with backend. The schema becomes the contract.

Why generated locally

A JSON mock generator does no harmful work — but it also has no business calling a server. Local generation is faster, available offline, and produces no telemetry. Open the tool, get the JSON, move on.

Frequently asked questions

How is this different from Fake Data?

Fake Data is per-field — you pick name, email, address. Mock JSON works from a shape — you pick user and get a fully formed user object including all fields. Faster when you want a complete document.

Can I customize the shape?

Yes. Pick a preset, edit the field list, add custom fields with a type, save your schema for reuse.

How nested can JSON go?

Up to 5 levels by default. Deeper structures become hard to reason about; if you need them, build the schema explicitly.

How many items can I generate?

Up to 1000 per click. For larger fixtures, generate in batches and concatenate.

Is the output deterministic?

No. Each click produces fresh values. For deterministic mocks, use a code-based generator with a fixed seed.

Can I generate paginated API responses?

Yes — pick the Paginated wrapper preset. You get { data: [...], page: 1, total: 100, hasMore: true } structure ready for stub-server use.

How do I mock a JSON response in Jest, Python, or Mockito?

Generate the JSON body here, then feed it to your test framework. Jest: jest.fn().mockResolvedValue(json) or fetchMock.mockResponse(JSON.stringify(json)). Python: unittest.mock's Mock(return_value=json), or responses/requests-mock for HTTP. Java: Mockito's when(...).thenReturn(json). The tool provides the realistic body; the framework provides the stubbing.

How do I create a mock JSON file or server?

Generate the data, save it as data.json, and point a mock server at it — json-server data.json spins up a full REST API in one command, and Postman can serve a saved response as a mock endpoint. For a static fixture, the file alone is often enough.

Related tools

Last updated: 2026-07-04