# dbt manifest, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** The manifest.json file dbt writes after a run, describing every model, test, source and the dependencies between them. Lineage tools read it to learn project structure without parsing every file. It is a design-time view of the project. The OpenLineage dbt integration parses manifest.json, run_results.json and optionally catalog.json to build lineage events.

## Definition

The manifest.json file dbt writes after a run, describing every model, test, source and the dependencies between them. Lineage tools read it to learn project structure without parsing every file. It is a design-time view of the project.

## Example from a real tool

**Example.** The OpenLineage dbt integration parses manifest.json, run_results.json and optionally catalog.json to build lineage events.

## Related terms

- [dbt exposure](/glossary/dbt-exposure/): A dbt declaration that something outside the project, such as a dashboard, depends on certain models.
- [ref() in dbt](/glossary/ref-in-dbt/): The dbt function one model uses to point at another, as in ref('model_a').
- [dataset (OpenLineage sense)](/glossary/dataset-openlineage-sense/): In OpenLineage, any named collection of data a job reads or writes: a table, a file, a topic.

## Where to read more

- [The Lineage Depth Matrix](/matrix/)
- [All glossary terms](/glossary/)

## Sources

- openlineage.io/docs/integrations/dbt: https://openlineage.io/docs/integrations/dbt (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/glossary/dbt-manifest/
