Website Showing an Old Page? Try a Hard Reload in Chrome

A website has changed, but your browser still shows the old design—or a page loads without its usual styling. A cached file is one possible cause. In desktop Chrome, try a hard reload before deleting browsing data. It asks Chrome to fetch the page again without relying on its normal browser cache. Save any unfinished form first; reloading can discard what you have typed.

This guide uses Chrome on Windows, Linux and macOS. It follows Google's documented tools rather than a hands-on test of your particular website. A hard reload is a diagnostic step, not proof that the browser cache caused the problem.

Why a page can look out of date

Browsers can keep copies of responses such as images, stylesheets and scripts so they do not need to retrieve everything on every visit. An HTTP cache can reuse a stored response while it is fresh, or check with a server whether a stored copy is still valid. The HTTP caching standard describes both browser caches and shared caches between a browser and the origin server.

Suppose a site's page has been updated, but a stylesheet controlling its layout is still being served from an older copy. The page might appear incomplete or oddly formatted. That is an illustrative example, not a diagnosis: the site could also have a deployment error, an extension could interfere, or the server could be delivering an old response.

Try a hard reload in Chrome

1. Save or copy any unsent work on the page.
2. Click the page, then press Ctrl + Shift + R on Windows or Linux, or Command + Shift + R on a Mac. Chrome's keyboard shortcut reference also lists Ctrl + F5 on Windows and Linux.
3. Check the specific thing that looked wrong: for example, whether the new logo appears or the layout returns. Then navigate away and back or reload normally to see whether the result persists.

If the page improves after the hard reload, a cached resource is a useful lead. If it immediately breaks again, note which action brings the problem back. A single successful reload does not identify which resource was responsible, and it does not guarantee the website will remain fixed.

A hard reload does not sign you out by deliberately clearing your cookies or erase the site's stored data. It also does not necessarily bypass every layer involved in a website: a service worker or a shared cache can be relevant. Google distinguishes the browser cache from service-worker caches in its DevTools caching overview.

Compare before clearing data

Try the same address in another browser or on another device, ideally with the same account and network where practical. If the problem appears only in one browser, local browser state or an extension becomes a more useful place to investigate. If it appears elsewhere too, a site or network issue is plausible. Neither result proves the cause: browsers, accounts and network routes can differ.

You can also compare a private window, but treat it as a comparison with a different browser session, not a clean scientific test. You may be signed out, and site behaviour can change with account state or extensions. Record the address, time and visible symptom before changing multiple things at once.

When site data is the next suspect

A broken sign-in loop or a preference that will not stick can involve site data rather than an old image or stylesheet. Cookies are used for session management and preferences, among other purposes, as Google's cookie documentation explains. Removing them can sign you out; removing other local storage can discard offline or locally saved work. Make sure you can sign back in and have saved anything important first.

For a more targeted investigation, Chrome DevTools has an Application panel for site storage. Google's Chrome 75 DevTools notes describe clearing selected types of site data there as well as a command that clears all data for the page. Read the available selections carefully: clearing all site data is broader than a hard reload. Avoid deleting individual cookies at random if you do not know what they do.

If a site is used for work or stores unsynchronised drafts, ask its support team which data can safely be removed. A reload cannot recover information already deleted from local storage.

If the problem remains

Check whether the same page fails with extensions temporarily disabled, then restore them one at a time if that changes the result. Do this only if you can safely change the browser's extensions; a managed work browser may have restrictions. If the symptom persists across browsers or devices, report the exact URL, time, browser and version, and what you observed to the site's support team. Avoid sending passwords, session cookies or private screenshots.

For a site you maintain, Chrome's Network panel can help inspect requests, while its Application panel can help investigate service-worker storage. A shared cache or the origin server may still need attention; clearing a visitor's browser is not a substitute for fixing the response being served. Start with the smallest reversible check, record the result, and widen the investigation only when the evidence points there.