How to Clear Cache in Power BI

Nothing is more frustrating than making a change in your data and not seeing it reflected in your Power BI report. Sometimes, despite hitting the refresh button, you're stuck looking at old information. This problem is often caused by caching, and this article will show you exactly how to clear it in both Power BI Desktop and Power BI Service to get your reports displaying fresh, accurate data.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What is Caching in Power BI and Why Clear It?

In simple terms, a cache is a temporary storage space that an application uses to hold frequently accessed data. Power BI uses several caches to speed things up. Instead of having to reload every single piece of data and redraw every visual from scratch each time you open a report, it retrieves much of this information from its cache. This makes reports load faster and feel more responsive.

While this is great for performance, it can occasionally cause problems. You might need to clear the cache if:

• You've updated your underlying data source, but the changes aren't appearing in your visuals.
• A report is behaving strangely, throwing unexpected errors, or visuals aren't rendering correctly.
• Power BI Desktop is running slow or consuming a large amount of your computer's resources.
• You want to test your report's true performance without the speed benefit of cached queries.

The process for clearing the cache is different depending on whether you're working locally in Power BI Desktop or a published report in Power BI Service. Let's walk through the methods for both.

How to Clear Cache in Power BI Desktop

Power BI Desktop doesn't have a single "Clear All Caches" button. Instead, there are a few different types of caches stored in different locations, and you can clear them using several methods.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 1: Clearing the Data Load Cache (Official Method)

This is the most direct method and is built right into the Power BI options. This cache specifically stores data that Power BI has downloaded from your data sources. Clearing it forces Power BI to re-download the data on the next refresh.

When to use this: Use this method when you suspect Power BI is holding onto old source data and not fetching the latest version, even after a refresh.

1. Open Power BI Desktop.
2. Go to File in the top-left corner.
3. Click on Options and settings, then select Options.
4. A new window will open. On the left-hand menu, under the Global section, click on Data Load.
5. Look for the Data Cache Management Options section. You'll see a button labeled Clear Cache.
6. Click the Clear Cache button. A confirmation pop-up will appear, asking if you're sure you want to delete the files from your cache. Click OK.

In this same dialog, you can also manage the maximum size of your data cache. If you work with very large datasets or find Power BI is consuming too much disk space, you might consider changing this limit.

Method 2: Troubleshooting with Power Query Cache Settings

Sometimes, the issue isn't a deep-seated cache but an in-progress background data preview causing problems in the Power Query Editor. While not a "clear cache" function, disabling the background preview can resolve odd behavior when you are actively transforming data.

When to use this: Use this when you're experiencing slowness or errors specifically within the Power Query Editor window.

1. With your report open, go to File > Options and settings > Options.
2. Under the Current File section, select Data Load.
3. Look for the setting called Allow data preview to download in the background.
4. Uncheck this box and click OK.

This prevents Power Query from continuously trying to cache data previews as you make changes, which can solve certain stubborn transformation issues.

Method 3: Manually Deleting the Visuals Cache (The Under-the-Hood Way)

Power BI Desktop uses a built-in browser engine (called Chromium Embedded Framework or CEF) to render many of its visuals. Just like a web browser, this engine has its own cache that can sometimes become corrupted, leading to broken visuals, login pop-ups that won't go away, or other strange display issues.

When to use this: Use this method as a powerful troubleshooting step when visuals are not loading, are showing old formatting, or you have persistent sign-in issues within Power BI Desktop itself.

1. Most importantly: close down Power BI Desktop completely. Make sure the process is not running in the Task Manager.
2. Open File Explorer in Windows.
3. In the address bar, paste the following path and press Enter: %localappdata%\Microsoft\Power BI Desktop\CEF
4. This will take you to your personal Power BI Desktop folder. Inside the "CEF" folder, you might see a "cache" folder or other folders like "blob_storage" and "IndexedDB."
5. Select all the files and folders inside the "CEF" folder and delete them.

Don't worry, this is perfectly safe. The next time you launch Power BI Desktop, it will automatically recreate these folders with a fresh, clean cache. This step alone solves a surprising number of unexplainable display bugs.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 4: Clearing the Query Cache with DAX Studio

For more advanced users and report developers, an external tool called DAX Studio provides the most precise way to clear the cache for performance testing.

When to use this: Use this when you are writing complex DAX queries and need to accurately measure their performance without cached results skewing your test times.

1. Download and install DAX Studio (it's free).
2. Open your Power BI Desktop file (PBIX).
3. Launch DAX Studio. It should automatically detect and offer to connect to your open PBIX file. Select it and click Connect.
4. In a new query window in DAX Studio, navigate to the Traces tab and select Enable All Details.
5. Go to the Functions section, and perform a search and replace using the button entitled Replace/Prefix.... Then run your chosen query.

This is an advanced technical function. DAX Studio has the capability of doing cache clearing or disabling them through "DirectQuery." Again, this is for more advanced users familiar with what those terms mean in reference to their specific Power BI workspace configuration choices.

Clearing "Cache" in Power BI Service

When you publish a report to Power BI Service (app.powerbi.com), "caching" becomes a different beast. You no longer have local files to delete. Instead, you're dealing with caches happening on Microsoft's servers and within your own web browser.

Method 1: Performing a Dataset Refresh

This is the most common way to get fresh data into your cloud reports. When you publish a PBIX file, you're publishing two main things: the report visuals and the dataset. A "dataset refresh" tells Power BI Service to go out to your original data sources (e.g., your SQL database, SharePoint file, or CRM) and pull in the latest information.

When to use this: Always use this when your underlying data has changed and you need the report's numbers and information to be updated.

1. Log in to app.powerbi.com.
2. Navigate to the appropriate Workspace that contains your report's dataset.
3. Find your dataset in the list (it will likely have the same name as your report and have the type "Dataset").
4. Hover over the dataset and click the Refresh now icon (a circular arrow).

You can also set up a scheduled refresh to have this happen automatically on a daily or hourly basis, keeping your reports consistently up-to-date without manual intervention.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 2: Clearing Your Browser Cache

Often, the problem isn't with Power BI Service at all, but with your own web browser. Browsers like Chrome, Edge, and Firefox cache web page elements, including parts of your Power BI report, to make them load faster next time. This can cause you to see a "stale" version of a report even after the dataset has been refreshed.

When to use this: If you're confident the dataset has been refreshed but you're still not seeing changes, or a report visual looks broken or won't load in your browser.

• The Quick Fix (Hard Refresh): In your browser with the report open, press Ctrl + F5 (or Ctrl + Shift + R on most browsers). This tells the browser to ignore its local cache specifically for this page and download a completely fresh copy. This one simple step solves the majority of display issues in Power BI Service.
• The Full Fix (Clear Browser Data): If a hard refresh doesn't work, you can clear your browser's entire cache. The location varies slightly by browser, but it's typically under Settings > Privacy and security > Clear browsing data. Make sure you select to clear "Cached images and files."

A great way to test if the issue is your browser cache is to open the report in a private or Incognito window. Since these windows don't use your regular cache, if the report looks correct there, you know your main browser cache is the problem.

Final Thoughts

Power BI uses caching to provide a smooth, fast user experience, but it can sometimes get in the way of seeing fresh data or cause rendering glitches. Knowing how to clear these caches — whether it's through the Data Load settings in Desktop, deleting the CEF folder for visual bugs, or forcing a dataset and browser refresh for the Service — gives you the power to resolve these issues and trust the information in your reports.

Manually refreshing datasets and tinkering with local cache settings is often part of the friction that comes with traditional BI software. We built Graphed because getting insights from your data shouldn't be so hands-on. By connecting your SaaS tools directly, we automate the entire reporting process so your dashboards are always live and up-to-date, without ever needing to worry about a manual refresh or a stale cache again.