Inference rulesEach object becomes a model, with an id added when none exists; nested objects and object arrays become foreign keys and two-sided relations where the relation is unambiguous, otherwise they fall back to Json columns; scalar arrays target PostgreSQL.Runs locally — no fixed size limit (bounded by browser memory)

Sample JSONJSON

Paste or type JSON

Generated schemaPrisma

Paste or type JSON

JSON → Prisma model · runs locally · no upload

JSON to Prisma Schema Generator

Sample JSON → model · automatic id · foreign keys & relations · Json fallback

🔒Your data is processed locally in the browser — never uploaded, never stored

No upload, no storage

JSON is processed in memory and never sent to a server.

Share via URL fragment

Share links encode data in the # anchor — never sent to a server.

Remember last edit

Optionally keep your last input locally; clear it with one click.

Why generate a Prisma schema from JSON

Models with primary keys

One model per object, with an autoincrement id added when your sample has none.

Foreign keys and relations

Nested objects become one-to-one and object arrays become one-to-many — both sides plus the foreign key column, ready to migrate.

Json fallback instead of guesswork

Nesting referenced from several places or hidden inside a union is not forced into a relation. It becomes a Json column, so you never get a schema that fails to migrate.

A complete schema file

Includes the datasource and generator blocks, not just a fragment. Scalar arrays target PostgreSQL, with a header note on switching to MySQL.

Runs locally — no upload

Generation happens entirely in your browser. Nothing is uploaded or stored.