This is known as "URL Rewriting" and it's traditionally done in one of three ways:

• at archive time before saving to disk (not ideal, but easy, see wget and SiteSucker)
• at replay time on the server/proxy before it gets served to a client (difficult but doable, see pywb)
• at replay time in the browser of the client viewing the archive (see wayback-everywhere and wombat.js, easiest and lightest weight option)

There are no plans to add any of these to ArchiveBox at the moment, but if someone wants to build a Chrome Extension to do client-side rewriting at replay time, I'd be down to add a link to our README/add it to our Github org and help maintain it.

Check out these alternative solutions for now:

• pywb (python app that does proxy-replay / server-side rewriting, or client-side rewriting with JS)
  • https://github.com/ikreymer/pywb-proxy-demo
  • https://pywb.readthedocs.io/en/latest/manual/configuring.html#proxy-mode-rewriting ⭐️
  • https://pywb.readthedocs.io/en/latest/manual/rewriter.html#rewriter
  • https://pywb.readthedocs.io/en/latest/manual/configuring.html#wombat
• wayback-everywhere (extension that does client-side rewriting)
  • https://chromewebstore.google.com/detail/wayback-everywhere/heienainncnjjejmamdkmbbfmblpffjj
    Someone should fork this extension to develop an equivalent for ArchiveBox!
• SiteSucker (macOS app that does archive-time rewriting before saving html to disk)
  • https://ricks-apps.com/osx/sitesucker/index.html
  • https://ricks-apps.com/osx/sitesucker/archive/2.x/2.9.x/2.9/manuals/en/pgs/FAQ.html#:~:text=Modification%20option%20to-,Localize,-.%20With%20this%20setting