## TL;DR
Never say "clear your cache" without the exact clicks, because to a non-technical user those words mean nothing. Give them the 4-click path for their browser, tell them what they will see, and warn them they will get logged out. The logout warning is the part everyone forgets, and it is the part that gets you the angry reply.

## The query

```text
browser cache clear instructions for non-technical users
```

## Use this when

- A page looks broken right after a release
- The user sees old data you know was fixed
- Buttons do nothing and the console-free user cannot debug
- You need a clean retest before escalating
- You are writing the help article your macros link to

## Not for

- The site being fully down for everyone
- Wrong-password or account-locked logins
- Bugs that reproduce in a fresh incognito window
- Mobile app issues, which have no browser cache

## Steps

### 1. Find out which browser they use

Ask them what they open the internet with. If they say "Google" they mean Chrome. If they say "the blue E" they mean Edge. Do not make them figure this out alone.

Expected output: you know the browser and can give the right clicks.

### 2. Offer the shortcut first, with a fallback

The quick way on Windows is holding Ctrl and pressing F5 for a hard refresh. Say it like a recipe: "hold down the Ctrl key, keep holding it, and tap F5." If that fails, move to the full clear below.

Expected output: a fixed page, or a user ready for the longer path.

### 3. Give the exact menu path for their browser

Chrome: three dots top right, Settings, Privacy and security, Delete browsing data, pick "All time", check only "Cached images and files", Delete data. Safari: Safari menu, Settings, Privacy, Manage Website Data, Remove All. Edge: three dots, Settings, Privacy, search and services, Choose what to clear. Firefox: three lines, Settings, Privacy and Security, Clear Data.

Expected output: the cache is cleared with no wrong turns.

### 4. Warn about the logout before it happens

Say this before they click: "this will log you out of websites, so have your password handy." Then tell them to close the browser fully and reopen it before testing again.

Expected output: a prepared user, not a surprised and locked-out one.

## Ready-to-use message

```text
Let's clear the saved files your browser keeps from our site.
In Chrome:

1. Click the three dots in the top right
2. Settings, then Privacy and security
3. Delete browsing data
4. Change the time range to All time
5. Check only "Cached images and files" and hit Delete data

Heads up: this signs you out of websites, so keep your password
handy. Then close Chrome completely, reopen it, and try again.
```

## Variant phrasings

### how to hard refresh a page for a customer

Step 2 on its own. Ctrl plus F5 on Windows, Cmd plus Shift plus R on Mac. One line, done.

### clear cookies and cache simple instructions

Same as step 3, but check both boxes and explain cookies mean saved logins. Only do this when the bug smells like a bad session.

### cache clear instructions for elderly users

Step 3 with screenshots and numbered arrows. Describe icons by appearance ("the three dots in the top right corner") never by name alone.

## Why it happens

Browsers save copies of site files to load faster, and after an update the saved copy and the live site stop matching. The page then behaves in ways that look like a real bug but are really just the browser reading yesterday's files. Clearing the cache forces a fresh download, which is why it fixes a surprising number of "it just broke" tickets.

## Edge cases

- User refuses because they fear losing something: reassure them that clearing cached images and files does not delete bookmarks, saved passwords in the password manager, or downloads.
- Bug persists after clearing: that is useful data. It means the problem is real, not stale files. Escalate with "cache cleared, still reproduces" in the notes.
- They use a managed work laptop: IT policy may block the settings page. Ask them to try incognito mode instead, which skips the cache without changing settings.
- Safari on iPhone: the path is Settings app, Safari, Clear History and Website Data. Warn them this clears history on all synced devices too.
- The user cleared everything including saved passwords and is now locked out of everything: own it, help them reset, and next time lead with the logout warning twice.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__1-JX-hE8hjjoOKzpxb5_w