Do unused columns slow Power BI down?

Cleaning up columns nobody uses is one of the most common Power BI chores. It shrinks the model. Whether it makes anything faster is a different question, and the honest answer is "often not much".

Published Updated 2 minute read

Ask on any Power BI forum how to speed up a slow report and someone will suggest removing unused columns. Microsoft's own guidance lists removing unnecessary columns as the first data reduction technique for Import models.1 The idea is sound. The expected payoff is often overstated.

What removing columns does

An Import model stores each column compressed, on its own. Removing a column you don't need:

  • makes the model smaller in memory and on disk;
  • can shorten refresh, if that column was expensive to load or calculate;
  • removes something people have to scroll past and wonder about.

What it usually doesn't do is make a visual faster. A query reads only the columns it asks for, so a column no visual uses was never on the query's path to begin with.

What practitioners found

In one r/MicrosoftFabric thread, a team cut a 5 GB semantic model by 85% and reported no change in refresh time or capacity units consumed.2 In another, asked to put a financial figure on deleting unused columns, a Tabular Editor employee asked for evidence that they hurt performance at all, pointing out that the engine is column-compressed. The reply that won the thread reframed the value: the real cost of unused columns is the work, knowledge and confidence it takes users to find the data they need.3

The exceptions are real, though. A wide, high-cardinality column that nobody uses still costs memory and refresh time, and a model close to its size limit gains a lot from losing it. Thousands of measures nobody uses can make Power BI Desktop itself sluggish.

Better reasons to clean up

  • Clarity. A model with half its fields unused is harder to understand, document and hand over.
  • Safety. Fewer fields means fewer things a rename or a schema change can break.
  • Size. Smaller models refresh and deploy more easily, and stay further from capacity limits.
  • Copilot. A model with fewer, clearer fields gives Copilot less to get confused by.

How to find them across every report

The hard part isn't deleting columns. It is knowing which ones no report on a shared model uses, which Power BI can't tell you on its own; Microsoft's idea asking for it had 211 votes in November 2026.4 TrailsBI reads the model and every report you give it and lists the columns, measures and tables nothing depends on: see finding columns and measures no report uses.

Sources

  1. Microsoft Learn: Data reduction techniques for Import modeling
  2. r/MicrosoftFabric: Semantic model size cut 85%, no change in refresh
  3. r/MicrosoftFabric: Translating the financial impact of deleting unused columns
  4. Fabric Ideas: Identify unused tables/columns