Page Archives

Page archives allow you to load a page as it was when the archive was captured. Instead of making requests to the monitored site, resource response (HTML, JavaScript, images, ...) are replayed from the archive.

The page remains interactive and JavaScript functionality works as normal. For example, you can use page archvies to check when a bug was introduced.

This video shows an example of how to select and load an archive:

How to load page archives

  1. Install the Chrome extension
  2. Open a monitored page on the DebugBear website
  3. Click the "Load archived page" button

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.

Can I load page archives in browsers other than Chrome

Not right now, please email if you're interested in this.

Page archives and login state

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 and then load an 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:

  • When the page makes a request no matching request is found in the archive. This may be the case when the page generates unique URLs.
  • A request may not have been made when capturing an archive, e.g. a request to save data. (Contact us if you're interested in running more complex page interactions when capturing the archive.)
  • The current time and date are not simulated. This might cause problems if, for example, the front-end JS checks if the login is expired.

Still need help? Contact for support.
© 2019 DebugBear Ltd