To improve browsing speed, Google Chrome utilizes a feature known as the “Back/Forward Cache” (bfcache). When you navigate away from a webpage, Chrome takes a complete snapshot of the page’s state (including the JavaScript execution and DOM) and freezes it in your system memory. If you hit the “Back” button, Chrome instantly restores the frozen snapshot instead of downloading the page from the server again.
While this makes navigating history incredibly fast, it can cause severe issues for web developers. If you are actively coding a website and testing changes, hitting the “Back” button might load a stale, cached version of your site instead of the newly compiled code on your local server. To ensure you are always viewing the most current, live version of a webpage, you can disable the Back/Forward Cache.
How to Force Full Page Reloads in Google Chrome
You can disable the freezing engine by modifying Chrome’s hidden developer flags.
- Open the Google Chrome browser.
- Click on the address bar at the top of the window, type
chrome://flags, and press Enter. - In the “Search flags” search box at the top of the screen, type Back-forward cache.
- The main list will filter down to show the specific flag.
- Click the drop-down menu next to the “Back-forward cache” entry (which is usually set to “Default”).
- Select Disabled from the drop-down menu.
- A prompt will appear at the bottom of the screen stating “Your changes will take effect the next time you relaunch Chrome.” Click the blue Relaunch button.
Chrome will restart. From now on, whenever you click the Back or Forward navigation arrows, Chrome will forcibly contact the web server and download a fresh copy of the page, completely bypassing the memory snapshot system and guaranteeing you always see live data.