JSON to Zod Schema Converter

Q: Do I need the `zod` package installed to use this?

Not to use this converter — everything runs in your browser. You do need `zod` installed in your own project to actually use the generated schema code (the output starts with `import { z } from "zod";`).

Q: How does it decide between `.optional()` and `.nullable()`?

A field becomes `.optional()` when it's missing entirely from some sample objects in an array, and `.nullable()` when it's present but its value is `null` in some samples. A field can be both if it's sometimes missing and sometimes `null`.

Q: What happens with arrays that mix types, like numbers and strings?

The element schema becomes a `z.union([...])` covering every type observed in the array, e.g. `z.array(z.union([z.string(), z.number()]))`.

Q: Are duplicate nested object shapes merged?

Yes. If two differently-named fields (e.g. `billing` and `shipping`) have structurally identical shapes, they reuse the same generated schema constant instead of producing two near-duplicate declarations.

Your json

Paste any JSON and get back Zod schema declarations (z.object(...)), inferred entirely in your browser — nothing is uploaded. Arrays of objects are structurally merged: a field present in every sample stays required, a field missing from some samples becomes .optional(), a field that is sometimes null becomes .nullable(), and a field whose value type varies becomes a z.union([...]). Repeated nested shapes (like two differently-named address objects with the same fields) are deduplicated into a single shared schema constant. Copy the output straight into a TypeScript project that has zod installed.

JSON to Zod Schema Converter

FAQ

Do I need the `zod` package installed to use this?

How does it decide between `.optional()` and `.nullable()`?

What happens with arrays that mix types, like numbers and strings?

Are duplicate nested object shapes merged?

See also