.pbix vs .pbip: Power BI File Formats Explained

If you have built a report in Power BI Desktop, you have almost certainly saved a .pbix file without thinking twice. But there is a second, newer format — .pbip, the Power BI Project — and it changes how the same report lives on disk. The short version: .pbix is one sealed binary file, while .pbip is a folder of readable text files you can put under version control. Here is what that means in practice and when each one is the right choice.

What a .pbix file actually is

A .pbix is a single file that packages three things together:

• The report — your pages, visuals, layout, formatting, and bookmarks.
• The semantic model — the tables, relationships, calculated columns, and DAX measures. (Microsoft renamed "dataset" to "semantic model" in 2023; older docs and menus may still say dataset.)
• The cached data — if your model uses Import mode, a compressed copy of the data is stored inside the file too. This is why a .pbix can grow to hundreds of megabytes.

Under the hood a .pbix is a ZIP archive, but it is not meant to be opened or edited by hand. The parts are binary or densely encoded, so the whole thing behaves as one opaque blob. You double-click it, Power BI Desktop opens it, you save, done. That simplicity is the format's biggest strength.

What a .pbip file actually is

A .pbip (Power BI Project) saves the same report as a folder of plain-text files instead of one binary. When you save a project named Sales, you get something like this:

Sales.pbip                      ← small pointer file you double-click
Sales.Report/                   ← the report definition (PBIR)
  definition/
    report.json
    pages/ ...
Sales.SemanticModel/            ← the model definition (TMDL)
  definition/
    tables/
      Sales.tmdl
      Date.tmdl
    relationships.tmdl
    model.tmdl

Two formats live inside that folder:

• TMDL (Tabular Model Definition Language) describes the semantic model — every table, column, relationship, and DAX measure — in readable text. Each table is typically its own .tmdl file.
• PBIR (Power BI Enhanced Report format) describes the report — pages and visuals — as JSON.

The .pbip file at the root is just a tiny pointer that tells Power BI Desktop which report and model folders belong together. By default, import-mode data is not stored in the project folder, so a .pbip checked into Git stays small and contains structure, not rows.

The headline difference: text you can read and diff

The reason .pbip exists is source control. Because the model and report are plain text, you can do things that are flatly impossible with a .pbix:

Capability	.pbix (binary)	.pbip (project)
Open in Power BI Desktop (free)	Yes	Yes
Single file to email or upload	Yes	No (it's a folder)
Stores cached Import data	Yes	No (by default)
Readable in a text editor	No	Yes
Meaningful Git diff of a measure change	No	Yes
Pull-request code review	No	Yes
Merge two people's edits	No (last save wins)	Yes (text merge)

With a .pbix, if two people edit the report and one saves over the other, the work is gone — Git sees only "the binary changed." With a .pbip, a reviewer can see that you changed one DAX measure from SUM to SUMX, on one line, and approve it. That is the whole point.

Total Margin =
SUMX (
    Sales,
    Sales[Quantity] * ( Sales[UnitPrice] - Sales[UnitCost] )
)

A change to a measure like that shows up as a clean line-level diff in a .pbip. Inside a .pbix it is invisible.

How to turn on and use .pbip

.pbip is built into Power BI Desktop, and the free version handles both formats — you never need a Power BI Pro license just to open or edit files locally. To save a project:

1. In Power BI Desktop, go to File > Options and settings > Options > Preview features and enable the Power BI Project (.pbip) save option. You can also enable Store semantic model using TMDL format so the model is written as TMDL text.
2. Use File > Save as and pick the Power BI project (.pbip) type.
3. Power BI Desktop writes the folder structure shown above.

A word on status: as of mid-2026 these formats are still maturing. Microsoft has been moving PBIP toward general availability, and PBIR is in the process of becoming the default report format while it finishes its preview run. Check the current preview labels in your build before you standardize a whole team on PBIR-based workflows.

To reopen, double-click the .pbip file at the root of the folder — not the individual .tmdl or .json files. You can still Save as back to .pbix at any time, so you are never locked in.

When to use each format

There is no universally "better" choice — it depends on how long the report needs to live and how many people touch it.

Reach for .pbix when:

• It is a quick, one-off, or throwaway report.
• You are working solo and just want a single file to attach to an email or drag into the Power BI Service.
• You want the data cached inside the file so you can hand someone a fully self-contained report.

Reach for .pbip when:

• The report is a long-lived asset you will maintain for months or years.
• More than one person edits the model or report.
• You want pull-request review, a change history, and the ability to roll back a specific edit.
• You are wiring reports into a deployment pipeline or Microsoft Fabric's Git integration, where text-based definitions are what gets tracked and promoted.

A practical pattern many teams use: build and tweak in .pbix for speed, then save the canonical version as .pbip so it can live in the repo. Both publish to the Power BI Service the same way once you are done.

A note on licensing: the format is separate from the cost

The file format on your laptop is separate from where the report runs. Power BI Desktop is free and opens both .pbix and .pbip. To publish a report to a shared workspace in the Power BI Service and let colleagues view it, you generally need a per-user license — Power BI Pro is roughly $14 per user per month at recent public pricing — or capacity-based licensing through Microsoft Fabric or Premium. Treat any figure as an approximation and confirm current rates with Microsoft. The format you saved in does not change any of that; it only changes how the report is stored and collaborated on before it ships. If you are setting up brand colors first, our free Power BI theme generator produces a theme JSON you can drop into either format.

How Instant PowerBI delivers .pbip

When you send us your raw data, we hand back a .pbip project, not a flat binary. That choice is deliberate. You get:

• A proper star schema — a clean fact table surrounded by dimension tables — defined in readable TMDL, so the model is something you can actually inspect and trust.
• DAX measures written in plain text you (or your reviewer) can read line by line, not buried in a binary.
• A report folder you can drop straight into Git if your team works that way, with branded theming already applied.
• The data embedded in the project, so the report opens in free Power BI Desktop without you needing to re-point any file paths.

Because it is a .pbip, the deliverable is transparent: you can see how every table and measure was built, change anything you want, and version it like the rest of your work. If you would rather start from a single binary, you can always Save as .pbix in one click.

---

Ready to skip the modeling work? Send us your CSV or Excel files and we will send back a finished, branded Power BI report as a clean .pbip project — fully modeled, ready to open in free Power BI Desktop, and easy to hand to your team. Get started at Instant PowerBI, or read up on building a proper star schema first.