What Is Caching? Browser, Server, and CDN Caching Explained

What Caching Actually Solves

Generating a web page from scratch, running database queries, assembling content, applying templates, takes real server time and resources. If every single visitor triggered that full process, a popular page would put far more load on a server than necessary, since the vast majority of requests for the same page produce an identical result. CachingStoring a copy of data or a page so it can be served faster next time instead of being regenerated. stores a ready-made copy of that result so it can be served instantly instead of rebuilt every time.

Browser Caching

When a browser downloads a file, an image, a stylesheet, a script, it can store a local copy according to instructions the server sends along with it. The next time that visitor requests the same file, the browser serves it from its own local cacheA temporary store of already-fetched data, kept so it can be reused quickly instead of fetched again. instead of downloading it again, which is why a second visit to a site usually feels noticeably faster than the first.

Server-Side Caching

On the server, caching stores a ready-made version of a page or a database query result, so the underlying application doesn't need to regenerate it for every single visitor. On WordPress specifically, this is usually handled by a dedicated caching plugin, or increasingly by the web server itself; LiteSpeed's built-in caching is a common example on cPanelA popular web-hosting control panel for managing sites, email, databases, and files through the browser. hosting. See Apache vs. Nginx vs. LiteSpeed for how the web server layer relates to this.

CDN Caching

A CDNA Content Delivery Network — a spread-out set of servers that cache your site closer to visitors for speed. adds another caching layer on top, storing copies of static content across servers in multiple locations, so a visitor is served from whichever copy is physically closest to them. It solves a related but distinct problem: not just avoiding regeneration, but also shortening the physical distance data has to travel. See What Is a CDN? for the fuller comparison between the two.

Why Your Changes Sometimes Don't Show Up Right Away

This is the most common practical frustration caching causes: you publish a change, refresh the page, and see the old version anyway. The cause is almost always a cached copy, at the browser, a caching plugin, or a CDN, still being served because it hasn't expired or been cleared yet. It's rarely a sign the change itself failed to save.

Caching vs. DNS Propagation: Not the Same Thing

These two get confused constantly because both produce the same symptom: "I made a change and it's not showing up everywhere yet." But they're different mechanisms. Caching affects how quickly a published content change appears, at the page or file level. DNS propagationThe delay while an updated DNS record spreads to servers worldwide, so a change isn't visible everywhere at once. affects how quickly a domain-level change, like switching to a new host entirely, is recognized across the internet. Clearing a cache won't fix a DNSThe Domain Name System — the internet's directory that translates domain names into the IP addresses of servers. propagation delay, and waiting out propagation won't fix a stale cached page. See What Is DNS Propagation? for that distinct, domain-level delay.

When and How to Clear a Cache

If a change genuinely isn't showing up, clearing the relevant cache is the right first step: a hard refresh (often Ctrl+Shift+R or Cmd+Shift+R) clears the browser's own cache for that page; a caching plugin typically has its own "clear cache" button; and a CDN dashboard usually offers a "purge cache" option for exactly this situation. Start with whichever layer is most likely involved, a caching plugin if you just edited a page, a CDN if you changed something site-wide, rather than clearing everything by default.