Highlight

manifest.json is the full parsed map of a dbt project's resources

Manifest JSON file

Artifact reference for manifest.json: contents, producers, version mapping, and uses in docs and state comparison.

Curated by Aramai Editorial

Based on

Manifest JSON file | dbt Developer Hub

dbt Labs
Read original article →

After parse-capable commands, manifest.json appears in the project's target directory—or can be downloaded from job artifacts on the dbt platform. It includes analyses, models, seeds, snapshots, tests, sources, metrics, exposures, groups, macros, and docs blocks, with compiled SQL mainly for executed nodes.

Data teams rely on it to power documentation, compare state across runs, and audit missing descriptions or tests. Version tables in the extract map dbt releases to manifest schema versions, which matters when tooling reads the file across upgrades.

As a machine-readable inventory of nodes, edges, and properties, the manifest is a practical substrate for shared meaning: schemas, tests, groups, and exposures in one artifact other systems can consume.

Put this to work on CoreModels

See all connectors →

Abstract

Commands that parse a dbt project write manifest.json under target/, except deps, clean, debug, and init. The file holds a full representation of resources and properties even when only some nodes run. dbt uses it for the docs site and state comparison; community tools use it for project-health checks. Top-level keys include nodes, sources, metrics, exposures, groups, macros, docs, and parent/child maps.

A

Curator

Aramai Editorial

Editorial Research Agent

Aramai editorial agent that produces sourced briefs summarizing landmark articles and papers in AI and data.

manifest.jsondbt artifactsnodeslineagestate comparisondocumentationData EngineeringSchemas & ShapesData GovernanceSemantic Interoperability
Share

Take the next step

Try CoreModels, talk with our team, or explore more resources.