Power BI’s file format story is getting a major update. According to reporting from Neowin, Microsoft is introducing its new Power BI PBIP format, promoting PBIR to the default position, and doing both without retiring the long-standing PBIX format that most users rely on today.
For anyone who has built reports in Power BI, the trio of file extensions — .pbix, .pbir, and now .pbip — has always been a little confusing. Microsoft’s move is meant to clarify that picture, and it is aimed squarely at teams that build reports as part of a proper development lifecycle rather than as one-off desktop tasks.
What is the Power BI PBIP format?
The PBIP (Power BI Project) format marks a shift away from the single-file, binary approach that has defined Power BI Desktop files for years. Instead of compressing everything into one .pbix blob, the project format stores the report and data model as separate, individual files inside a folder structure.
That structural change is what makes the format so much more compatible with programmatic workflows. When your report components live as discrete files, they can be tracked, compared, and merged the way source code can — which is precisely what version control systems like Git are designed to handle.
The practical upshot is that a Power BI report stops being a black-box file and starts behaving more like a code project you can inspect and version.
PBIR becomes the default
Alongside the PBIP rollout, Microsoft is making PBIR (Power BI Report) the default format. PBIR is an XML-based report definition format that has been available for some time, used mainly when publishing reports to the Power BI service.
By promoting PBIR to the default position, Microsoft is signaling that the report definition — rather than the desktop-centric binary — is becoming the canonical representation of a report across the platform. This aligns Power BI more closely with how modern analytics platforms treat their output as versionable, deployable artifacts.
Why this matters for CI/CD and programmatic development
The real appeal of the Power BI PBIP format is what it unlocks for teams running continuous integration and continuous deployment (CI/CD) pipelines. Historically, moving a Power BI report through a deployment pipeline was awkward because the .pbix file is a single binary — merge conflicts are painful, and there is no clean way to see what changed between versions.
With a folder-based project format, changes become granular. A developer editing one visual or one measure produces a diff that tools can actually read. That makes automated testing, peer review, and deployment far more practical than trying to diff a compressed binary file.
For organizations that manage multiple Power BI environments — development, test, and production — this granularity is a genuine workflow improvement. It also brings Power BI closer to the practices teams already use for application code.
PBIX is not going away
One thing worth emphasizing: the existing PBIX format is not being replaced. Users can still create and open .pbix files in Power BI Desktop exactly as they always have.
The new formats layer on top of the existing experience rather than forcing a blanket migration. If you are happy working in PBIX and publishing reports the way you do today, nothing about your routine has to change overnight.
What This Means for You
For casual users who build a report now and then, this change is unlikely to alter your day-to-day work. You can keep working in PBIX and publish as before, with no immediate action required.
For teams that treat Power BI as a development project — sharing work across collaborators, running automated pipelines, or deploying reports through multiple environments — the PBIP format addresses a real pain point. If you have ever struggled to track changes in a shared report or merge two people’s edits without stepping on each other, this is the direction Microsoft is heading.
The broader implication is that Power BI is being positioned less as a lone-desktop tool and more as a collaborative, engineering-friendly platform. That matters if your organization values governance, audit trails, and repeatable deployments.
How to Get It
Since Microsoft is rolling out PBIP generally and making PBIR the default, the formats should become available through the standard Power BI updates. Check your Power BI Desktop version for the new save and project options the next time you open or create a report.
If you are setting up CI/CD or version control for Power BI, it is worth exploring the PBIP project format now so you can structure your reports in a way that plays well with Git and your deployment pipelines from the start.
Source: Neowin
Over to you: Are you going to start building your Power BI reports in the new PBIP format for version control, or will you stick with the familiar PBIX file?
