JSON to Zod Schema

A TypeScript type is checked by the compiler and erased by the time your code runs — it cannot stop a malformed response from reaching your handler. A Zod schema is the runtime half of the same shape: call .parse() on it and a response that does not match throws, instead of a wrong value quietly propagating three functions deep before something breaks.

Targets the Zod 3 chain API

Output uses z.object(), z.array() and chained modifiers such as .optional() — the API in every current published example. If your project pins an older Zod version, check the chain methods it exposes before assuming this output compiles unchanged.

Shape, not constraints

The inferred schema checks that a field is a string, not that it is an email or under 200 characters. A single example cannot tell this tool a string field is always an ISO date — that is a constraint you add by hand once you know it, the same way it would be if you wrote the schema from scratch.

{"id":1,"tags":["a","b"]} produces z.object({ id: z.number(), tags: z.array(z.string()) }). A field seen as both a string and a number across an array's items comes out as z.union([z.string(), z.number()]), naming the real shape rather than picking one arbitrarily.