Zod architecture

A TypeScript-first schema library where the validator and the static type come from one declaration.

What is Zod?

Zod lets you declare a schema once and get both runtime validation and a static TypeScript type out of it. That single-source property is the point of the library, and it is what makes its internals unusual.

The repository is also mid-migration. Version 3 and version 4 live side by side, with v4 split between a core and the APIs built on top of it. Which parts are shared? What does a v3 user import versus a v4 user? Where does type inference happen relative to parsing? Those are awkward questions to answer by browsing folders.

The map on this page is JigsawML's read of the Zod repository. It separates the two major versions and the tooling around them, and lets you open any area to see which files belong to it.

Key components in the Zod architecture

JigsawML identified and labelled these components automatically by analysing the Zod repository. Open the interactive map to expand any of them and read the underlying code.

  • Zod V3

    The version 3 implementation, still shipped for projects that have not migrated.

  • Zod V4 Core

    The version 4 foundation — the parsing engine and base schema machinery.

  • Zod V4 APIs

    The schema constructors and combinators users call, built on the v4 core.

  • Build Tooling

    Bundling, type generation, and the release pipeline for the published package.

  • Interop Compatibility

    Adapters and shims that keep Zod usable alongside other tools and versions.

  • Documentation Site

    The sources for the documentation site kept in the repository.

  • External Services

    Registries and outside systems referenced by the build and docs.

Explore the Zod architecture map

The map is live and interactive - pan, zoom, drill into a component, and ask questions about how Zod fits together. No login required.

Open the Zod map

How this map was generated

JigsawML ingested the public repository, resolved its dependencies, and grouped the code into architectural components using AI agents and a knowledge graph. Nothing here was drawn by hand. The same process runs against private repositories and cloud accounts, and re-runs on every commit so the map never goes stale.

Map your own codebase

Other open-source architectures