If you have ever made a change to your Power Pages site and wondered why it did not show up right away, you have already met caching. Caching is one of those behind-the-scenes things most people never think about until it confuses them. It is also a big reason your site loads fast. In this article I will explain what caching is in Power Pages, how it works, and how to handle it without causing yourself trouble. I will keep things plain so it makes sense even if this is new to you.
What Caching Actually Is
Caching is simple at heart. Instead of fetching the same information over and over, the system keeps a copy close by and reuses it. Think of it like keeping a snack in your desk drawer instead of walking to the store every time you are hungry. The drawer is faster. Caching does the same thing for your website. It holds onto data it already grabbed, so it does not have to go fetch it again for the next visitor.
This matters because your Power Pages site stores its real data in Microsoft Dataverse. Reaching into Dataverse for every single request would be slow, especially when many people visit at once. Caching lets the site answer most requests from a fast local copy, which keeps pages snappy and your visitors happy.
Server-Side Caching: The Main Event
The most important kind of caching in Power Pages is server-side caching. This sits between the web server and Dataverse. When the web server needs some data, it asks Dataverse once, gets the answer, and keeps that answer in memory. The next time the same data is needed, the server hands back the saved copy instead of bothering Dataverse again.
This server-side cache usually refreshes about every 15 minutes. So even if nothing else happens, the cached data does not sit there forever. After roughly 15 minutes, the system goes back to Dataverse to get a fresh copy. This 15 minute window is worth remembering, because it explains a lot of the behavior you will see on your site.
The Two Kinds of Cached Data
Power Pages caches two main types of data, and they behave a little differently.
The first type is configuration and metadata. This is the stuff that makes up your site itself: web pages, web templates, content snippets, and similar settings. This data is the same for everyone who visits, so the system caches it for all users at once. Whenever you change one of these configuration records, the cache for it updates automatically, within that same 15 minute window.
The second type is business data. This is the actual content from your Dataverse tables that shows up on the site, like a list of products or a customer’s records. This data is usually cached per user, because different people are allowed to see different things. The system only caches the data each user actually looks at. There are some exceptions, such as anonymous visitors or tables set to global permission, where the data may be shared more broadly.
Knowing this split helps you understand why some changes seem to appear instantly while others take a few minutes.
How the Cache Refreshes
Here is the part that trips people up. When does the cache update?
The good news is that the cache is smarter than a plain timer. If any record in a table is created, updated, or deleted through the website by any user, the cache for that specific table clears right away for everyone. So actions that happen on the site keep things fresh on their own. A new record posted through a form will show up without a long wait.
On top of that, the cache clears automatically within about 15 minutes even when nothing changes. So at worst, you wait a quarter of an hour and the latest data appears. This is why a change you made directly in Dataverse, outside the website, might not show up at once. The site is still serving its cached copy until the next refresh.
CDN Caching Is a Separate Thing
There is another layer worth knowing about, and it is easy to mix up with server-side caching. A content delivery network, or CDN, caches static resources like images, style files, and scripts. These are the unchanging pieces that make your site look the way it does. The CDN keeps copies of them close to your visitors around the world so they load quickly.
This is different from the server-side cache, which deals with your data. If you ever update an image or a script and the old one keeps showing, the CDN is the likely culprit, not the data cache. You can clear the CDN cache using the Purge Cache option in the Power Platform Admin Center when you really need to.
Clearing the Cache, and Why to Be Careful
Sometimes you want to force a refresh instead of waiting. There are a few ways to do this. Clicking the Preview button in the Power Pages design studio refreshes things as you work. There are also clear cache buttons available at your site address followed by /_services/about, which you can reach when you are signed in as an administrator.
Here is the important warning. Do not lean on the clear cache button as a habit. When you clear the cache, you clear it for all data tables and all configuration tables at once. That means the site has to rebuild everything from Dataverse, which can cause temporary slowness. On a busy live site, hitting clear cache during peak hours can make real visitors feel the lag. Use it rarely, and ideally during quiet times, not as your go-to fix.
A Few Practical Tips
Plan around the 15 minute window. If you make a change and it does not appear at once, give it a little time before you reach for the clear cache button. Most of the time, the site catches up on its own.
When you change data directly in Dataverse rather than through the site, expect a short delay before it shows. If you need it live immediately and it is safe to do so, you can refresh, but remember the cost on a busy site.
And keep the two cache types straight. If data is stale, think server-side cache. If images or styles are stale, think CDN. Knowing which one you face saves a lot of guessing.
Wrapping Up
Caching is what makes a Power Pages site fast, but it can feel mysterious until you know the rules. The server-side cache stores your Dataverse data and refreshes about every 15 minutes, or instantly when records change on the site. Configuration data is shared for everyone, while business data is usually cached per user. A separate CDN handles static files like images and scripts. Clearing the cache by hand works but should be a last resort, because it slows the whole site while it rebuilds. Understand these layers, give the system a little time, and caching goes from a source of confusion to a quiet helper that keeps your site quick.