Free dbt Lineage Visualizer: Explore Your Entire dbt Project in the Browser

Somewhere between model number twenty and model number two hundred, a dbt project stops fitting in anyone's head. You open a mart, see six ref() calls, and each of those has its own ref() calls. A lineage graph turns that maze into a picture you can read in a minute. Here is how to get one for free, without installing anything and without connecting to your warehouse.

Open the dbt Project Visualizer

What a dbt lineage visualizer actually shows

dbt already knows your dependencies: every ref() and source() is a line in the graph. A visualizer reads those calls and draws them. Raw sources sit on the left, staging models come next, then intermediate models, marts and finally reporting tables. An arrow from A to B means B selects from A.

The value is not the drawing itself. It is that you can click one model and see everything it is built from, and everything that would break if you changed it.

Why a browser-based option is useful

The usual ways to see dbt lineage need setup. dbt docs needs dbt installed and a working connection to your warehouse. Hosted platforms need an account and often a paid plan for the deeper views. A browser-based visualizer needs neither: you drop the files and read the result.

That matters in a few common situations: you were handed a repository by a client, you are reviewing a pull request on a laptop with no credentials, or your security team does not allow you to paste company SQL into a hosted service.

How to explore your project in four steps

1. Open the visualizer and add your models

Open the dbt project visualizer and drag your dbt models folder onto the page, or choose the folder or a ZIP of the repository. A pop-up confirms how many SQL files were read. The tool reads up to 3,000 files of 5 MB each, and skips hidden folders, node_modules and target folders.

2. Read the graph by layer

Colour shows the folder a model lives in, so staging, intermediate and marts are easy to tell apart. Dashed cards are sources: tables your SQL reads but never creates. Each card shows the model name, its type and how many columns the tool found.

3. Click a model

Click any card and its path through the project lights up in blue while everything else fades. Use Upstream to see what it is built from, Downstream to see what depends on it, or Both for the full neighbourhood. A details bar lists the direct parents and the number of models affected downstream.

4. Trace a column

Open the Columns tab, choose a model and click a column. You see the source columns it comes from and the columns that depend on it, each marked as copied or calculated with the expression shown. This is column-level lineage read straight from your SQL, and it is best effort: aliases, casts, CASE and functions are followed, but macros that generate columns are not.

A small example

Say a dashboard shows revenue that looks too low. In the visualizer you open the reporting table, click the revenue column and follow it back. It calculates from an order_amount column in a staging model:

select
  order_id,
  customer_id,
  amount * 1.0 as order_amount
from {{ source('shop', 'orders') }}
where status <> 'cancelled'

Now the cause is visible: the staging model filters out cancelled orders before any mart sees them. Nobody had to grep the repository.

What it does not do

Being clear about limits makes the tool easier to trust. It does not read docs blocks, and it shows only the descriptions and tests written in your schema YAML files. Jinja that builds table or column names in loops cannot be followed, and the graph will be incomplete there. A SELECT * is expanded only when the source table is defined with its columns in your files. Anything it cannot read is listed under Issues, so gaps are visible rather than silent.

It also does not run dbt, show query results or read your warehouse. If you need descriptions and test results next to the graph, keep using dbt docs alongside it.

Save and share the result

Open Export to save the graph as a PNG or JPG, copy it into a document or slide, or copy a share link. The link carries the SQL inside the address itself, so nothing is stored on a server and a teammate sees the same graph.

Try it on your own project

The fastest way to judge a lineage tool is to point it at a project you know. Drop your models folder into the free dbt lineage visualizer, click your most important mart, and see whether the upstream path matches what you expect. For a step-by-step walkthrough, read how to use the dbt project visualizer, and to understand what the arrows mean, see how to understand dbt model dependencies.

Open the dbt Project Visualizer

Related tool pages

  • SQL Lineage Analyzer for a Folder of SQL Files: Upload a folder of SQL files or a dbt project and get table and column lineage across every file, a run order and impact analysis. Free, runs in your browser.
  • dbt Lineage Viewer for Your SQL Models: Drop your dbt models folder and see the lineage graph from sources through staging to marts, with column links. No dbt run, no warehouse. Free, private.
  • SQL Column Lineage Tool: See which source columns build every column of a view or table across many SQL files. Trace to the raw table or forward to dependants. Free, in your browser.
  • SQL File Dependency Analyzer: Find out which SQL file must run before which, from the tables each file creates and reads. Get a run order, circular dependencies and tables nothing uses.
  • SQL Impact Analysis: What Breaks If a Table Changes: Pick a table and see everything downstream that depends on it, and every upstream source it is built from. Works across a whole folder of SQL files, free.
  • SQL File Lineage Tool: Free SQL file lineage tool: drop a folder of .sql files and see which file feeds which table, column by column. Nothing is uploaded.

Also try

How to use the dbt Project Visualizer: step by step

  1. Open the dbt project visualizer and drop your models folder or a ZIP.
  2. Click a model, then choose Upstream, Downstream or Both.
  3. Open Columns to trace a column, then Export to save or share.

When to use the dbt Project Visualizer

  • See the whole dbt DAG at a glance
  • Explain a project to a new teammate
  • Check what a model change would break
  • Trace a mart column back to its source

Example

Input: your dbt models/ folder: staging, intermediate and marts

Output: A graph from sources through staging to marts, with every column traced

Frequently asked questions

Is there a free dbt lineage visualizer?

Yes. The dbt Project Visualizer on Data Utility is free, needs no sign-up and runs in your browser. You drop your models folder and it draws the lineage graph.

Do I need dbt installed or a warehouse connection?

No. The tool reads your .sql model files as text, follows ref() and source(), and never connects to a database.

Does it work with dbt Core and dbt Cloud projects?

Yes, because it reads the SQL files in your repository. It does not connect to dbt Cloud.

Is my dbt project uploaded to a server?

No. The files are analysed in your browser and are not sent anywhere.

Tip: Drop the models folder rather than the whole repository. A smaller input draws faster and keeps package code out of your graph.