TypeScript catches type errors at compile time. But APIs, databases, and user forms return data at runtime — where TypeScript's static guarantees simply do not apply. Zod fills this critical gap.
The Compile-Time vs Runtime Gap
You define a TypeScript interface for an API response. The interface says userId is a number. At runtime, the API returns userId as a string. TypeScript cannot catch this. Your application crashes or silently processes wrong data. This is the gap Zod closes.
What Zod Adds
Runtime validation: data is checked against the schema when it arrives, not when the code is compiled. Detailed error messages: when data fails validation, Zod tells you exactly which field failed and why. TypeScript type inference: z.infer extracts the TypeScript type from the schema automatically — no duplicate type definitions.
Convert any JSON object to a complete Zod schema in seconds with the JSON to Zod Converter. Paste an API response and get production-ready TypeScript instantly — including email, URL, and date detection.
The Three Killer Integrations
tRPC uses Zod schemas for procedure input/output — one schema serves TypeScript inference, runtime validation, and API documentation. React Hook Form with zodResolver connects form validation directly to a Zod schema. Next.js API routes validate request bodies against Zod schemas before processing.