Archives allow you to load a page the way it worked when the page was tested. Instead of making requests to a real server, responses are replayed from the archive data.
Loading page archives requires a Chrome extension, this video shows how to do it:
Note: the Load Archive button is now at the bottom of the Overview tab.
Here are some of the things you can do with page archives:
This will open a new tab which makes no network requests and instead uses archived responses instead.
The archive loader extension uses the Chrome Debugger Protocol, so you'll see a "DebugBear Archive Loader is debugging this browser" message.
Not right now, please email firstname.lastname@example.org if you're interested in this.
Since the loaded page may depend on a certain set of login data, cookies are set to what they were when the archive was captured. They are reset to the normal state when you finish using the archive.
This means that if you're logged into example.com and then load an example.com archive you will be temporarily logged out of your normal account.
You could avoid this problem by creating a separate Chrome Profile to load the archive in.
Some reasons why loading an archived page may not work correctly: