Browser caching explained: why customers still see your old website

Caching is your browser being loyal to the last version it saw; the fix is not to fight the loyalty but to prove what actually shipped.

The message arrives in a tone somewhere between confusion and accusation: the redesign shipped, the invoice was paid, and a customer writes to say the website still looks exactly like the old one. Nothing is broken here. The most common cause of this particular pain is browser caching, and it is the rare support issue whose root cause is the system working correctly.

A browser keeps copies of the files a site is built from, so that your second visit is faster than your first: why download again what has not changed? That is caching, and it is doing its job. The pain lives in the gap between what actually shipped and what a returning visitor's browser is still politely holding on to.

The failure versions follow from that gap. An owner pays for changes the customers cannot see and concludes the developer did nothing. A team rolls back a deploy in a panic, convinced it failed, when in fact it succeeded and the only witness of the old version was one returning visitor. And someone ends up making the hard-refresh phone call, walking a client through clearing a cache after hours.

The practice starts on the builder's side: before declaring a fix shipped, verify the live site through a cache-bypassing view, a private window or a fresh profile, and check the page the way a first-time visitor would meet it. A change proven only in the developer's own warm browser has not been proven at all.

Then tell clients the one-week rule about their own browsers: a returning browser can serve yesterday for days, so if a page you know has changed still looks old, force one refresh before reporting it. And on the server side, let the machine send honest freshness signals, so caches expire on a schedule the site chose rather than whenever the browser happens to guess.

We verify every launch and every fix through a clean view before we call it done, and we would rather send the awkward note explaining the refresh rule than take the panicked rollback call a week later. This stays an owner-level subject: the details underneath belong to whoever runs your hosting. Guidance, not guarantees: caching behavior varies by browser and by network, and what stays constant is the discipline of proving what shipped.