When F5 isn't enough.
Your browser saved an old copy of this page to load it faster next time. Sometimes it holds on too long and you keep seeing yesterday's version. Here's how to make it let go.
Try this first — hold it down
Reloads the page and ignores the saved copy.
On a phone, there's no shortcut
Mobile browsers have no hard-refresh gesture — pulling down to refresh reuses the cache. Pick your browser below for the real steps.
On your computer
Desktop browsers
7 guides
Google Chrome
Windows · macOS · Linux · ChromeOS
Mozilla Firefox
Windows · macOS · Linux
Safari
macOS
Microsoft Edge
Windows · macOS · Linux
Opera
Windows · macOS · Linux
Brave
Windows · macOS · Linux
Vivaldi
Windows · macOS · Linux
On your phone or tablet
Mobile browsers
8 guides
Google Chrome
Android · iOS
Mozilla Firefox
Android · iOS
Safari
iOS
Microsoft Edge
Android · iOS
Opera
Android
Brave
Android · iOS
Vivaldi
Android
Samsung Internet
Android
On iPhone and iPad, Apple requires every browser to use its WebKit engine. Chrome, Firefox, Edge and Brave each keep their own separate cache, so clearing one does not clear the others.
Why this happens
A cache is a shortcut your browser takes
To make pages load faster, your browser saves copies of the things a site sends it — images, stylesheets, scripts, whole pages. The next time you visit, it checks whether it already has those files and reuses them instead of downloading them again. Most of the time this is exactly what you want.
The problem comes when a site changes but your browser doesn’t notice. It keeps serving you the copy it saved, so you see an old layout, a stale price, or a bug that the site owner already fixed. Pressing the normal refresh button often isn’t enough, because a normal refresh is still allowed to reuse cached files.
A hard refresh tells your browser to ignore what it saved and fetch everything again. If that doesn’t do it, you can clear the cache entirely, which throws away the saved copies for every site. Both are covered below, for every browser.