manifest.jsonPaste, upload, or drag & drop — processed locally
🌿
Paste your dbt manifest.json to visualize the lineage
Or click Load Sample to see a demo
Visualize dbt lineage from manifest.json
Upload your dbt manifest.json and see model dependencies rendered as an interactive DAG — sources, staging, intermediate, and mart layers laid out clearly. Understand blast radius before you change a model.
Frequently Asked Questions
- Where do I find my dbt manifest.json?
- dbt writes it to the target/ directory of your project on every compile or run: target/manifest.json. Any dbt version's manifest works for lineage purposes.
- Is my manifest uploaded to a server?
- No — the file is parsed in your browser. That matters because manifests contain your model SQL and database schema names.
- What does data lineage tell me?
- Lineage shows which upstream sources feed each model and which downstream models depend on it, so you can assess the impact of changes and trace data quality issues to their origin.
- Why are my model layers (staging/marts) not grouped as expected?
- Layering is inferred from your model naming and folder conventions (stg_, int_, marts). If your project uses different conventions, the DAG still renders — only the visual grouping differs.