If Command-R appears to do nothing, first confirm Safari is responding and the correct tab is active. Then try View > Reload Page. If the page still shows stale or incomplete content, test it in a private window before removing stored website data. Use Safari’s developer cache controls only if ordinary reloads and the site-specific check do not help.

1. Use Safari’s menu to reload the active page

Click the tab that needs refreshing, then choose View > Reload Page from the macOS menu bar. Apple documents this menu command and Command-R as two ways to reload a page. If the menu command works but the shortcut does not, the page itself may not be the issue: check that Safari has focus and that the intended tab is selected. (Apple Support: If Safari doesn’t work as expected on Mac)

A reload asks Safari to load the page again; it cannot fix every reason a site may be blank, slow, or partly missing. If Safari itself is unresponsive, Apple’s next step is to close Safari and try again. If it will not quit, use Option-Command-Esc, select Safari, and choose Force Quit. Unsaved work in open web apps may be lost, so use this only when Safari has stopped responding. (Apple Support)

2. Check whether the problem is saved site data

If Safari reloads but one site still displays old content or behaves incorrectly, open a New Private Window with Shift-Command-N and visit the same address. Apple recommends this as a way to check whether cookies, caches, or other website data are involved. If the page works in the private window, that points toward stored site data or a setting affecting the regular window; it does not by itself identify which one. (Apple Support)

To remove data for that site, go to Safari > Settings > Privacy > Manage Website Data, select the affected website, click Remove, then Done. Reopen the site in a regular window. This removes that website’s stored data, including cookies and caches; if you use an account there, make sure you know your sign-in details first. Removing site data can sign you out or reset site preferences. (Apple Support)

3. Use Empty Caches only when a normal refresh is not enough

Safari’s Develop > Empty Caches command is a broader option. Apple describes it as deleting all caches stored by the browser and says it is useful when cached content prevents a developer from seeing changes. That makes it relevant when you specifically suspect stale cached files, but it affects browser caches broadly rather than just one site. Try the site-specific removal step first when only one website is affected. (Apple Developer: Develop menu)

The Develop menu may be hidden. To enable it, choose Safari > Settings, open Advanced, and turn on Show features for web developers. Apple notes that developer tools are off by default. Once enabled, return to the menu bar and choose Develop > Empty Caches, then reload the page with View > Reload Page. (Apple Developer: Enabling features for web developers)

Do not assume a shortcut from another browser will force Safari to bypass its cache: Apple’s current support instructions identify Command-R as Reload Page, while its developer documentation identifies Empty Caches as a separate Develop-menu command. If you do not see a clearly labeled reload-from-origin option in your Safari version, use the documented menu commands instead of guessing at a key combination.

4. If the page still will not load

Try another website in Safari. If other sites work, check whether the problem is limited to one site: test a private window, remove that site’s data if appropriate, and check for a site-specific Safari setting such as a content blocker. Apple also recommends testing the page in another browser or on another device on the same network. If the problem appears across browsers and devices, the website or network may be responsible; if it persists only in Safari, check extensions and Safari or macOS updates. (Apple Support)

A useful order is: View > Reload Page, restart Safari if it is stuck, test the site in a private window, remove only that site’s data if the test points to stored data, and use Develop > Empty Caches only when a broader cache clear is warranted. This keeps the troubleshooting tied to what the evidence shows and makes it easier to tell whether the reload shortcut, stored site data, Safari, or the site itself is the likely source of the problem.

Sources