Page Archives

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:

  • track down a bug you can't replicate when loading the live site
  • check when a bug was introduced
  • compare how your app used to work, vs. how it works now

How to load page archives

  1. Install the Chrome extension
  2. Open a monitored page on the DebugBear website
  3. Go to the "Overview" tab and scroll to the bottom of the page
  4. 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. (Get in touch 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.
DebugBear is a website monitoring tool built for front-end teams. Track performance metrics and Lighthouse scores in CI and production. Learn more.
© 2021 DebugBear Ltd