JSON to Zod Schema

01 Zod Validator Mapping Matrix

02 Schema Generation Pipeline

03 Where Zod Beats Plain TypeScript Types

TypeScript checks shapes at compile time only, it disappears at runtime. Zod (v3+) fills the gap with a schema that also validates incoming data, then infers a TS type from itself. Reach for it at every untrusted boundary.

• 🛂
  API ingress validation Any handler receiving JSON from the outside world should parse it through a Zod schema first. The result is fully typed; failures throw or return a discriminated SafeParseResult. Pairs naturally with Hono, Fastify, Express, and Elysia adapters.
• 🧭
  Next.js Server Actions inputs Server Actions receive FormData or POST bodies. A Zod schema at the top of every action turns "string-soup from the browser" into a typed object, with field-level errors ready to surface in the form UI via useFormState.
• ⚙️
  Env var schema validation A boot-time z.object({ PORT: z.coerce.number(), DATABASE_URL: z.string().url() }).parse(process.env) turns environment misconfiguration into a precise startup error instead of an undefined-variable surprise three layers deep.
• 🪝
  Third-party webhooks Stripe, GitHub, Shopify all evolve their payloads. A Zod schema at the webhook entrypoint gives you a loud, typed failure when the sender adds or renames a field, far better than a silent undefined deep in your handler.
• 🧪
  tRPC, react-hook-form, and form libraries tRPC uses Zod natively for input/output. react-hook-form's zodResolver wires browser validation to the same schema your server uses. One schema, two enforcement points.

04 Worked Examples

{"id":"u_1","email":"a@x.io","createdAt":"2026-05-20T10:00:00Z"}

import { z } from "zod";
export const UserSchema = z.object({
  id: z.string(),
  email: z.string().email(),
  createdAt: z.string().datetime(),
});
export type User = z.infer<typeof UserSchema>;
// equivalent to: { id: string; email: string; createdAt: string }

const Range = z.object({
  start: z.number().int(),
  end:   z.number().int(),
});

const Range = z.object({
  start: z.number().int(),
  end:   z.number().int(),
}).refine((v) => v.start < v.end, {
  message: "start must be < end",
  path: ["end"],
});

const event = StripeEventSchema.parse(rawJson); // throws ZodError on mismatch

const result = StripeEventSchema.safeParse(rawJson);
if (!result.success) {
  logger.warn({ issues: result.error.issues }, "stripe webhook schema mismatch");
  return new Response("ok", { status: 200 }); // never make Stripe retry on shape changes
}
const event = result.data; // fully typed

05 Related Tools

Zod schemas often sit between pure types and full schema declarations. These tools round out the workflow.