one click saves the page you're looking at to wayback, archive.today, and a local html file.
link rot. i'll send someone an article i read last month and it's a 404. blog got taken down, tweet got deleted, docs page moved, site went behind a paywall. the wayback machine and archive.today both solve this but actually using them is four clicks, a captcha, and a 30-second wait.
this is one click from the toolbar.
the local html copy is the safety net. if both public archives go down in 10 years (entirely possible), you still have the file.
git clone https://github.com/wanderer-npm/archive-quick
cd archive-quick
npm install
npm run build
then in chrome: chrome://extensions → toggle developer mode → load
unpacked → pick dist/.
pin the icon, optionally bind Ctrl+Shift+A.
open the popup. four buttons:
- archive.org, goes to wayback
- archive.today, goes to archive.ph
- save local, dumps the page html to
Downloads/archive-quick/ - archive everywhere, fires all three
the popup also shows every past archive of the current url with clickable links.
wayback's submit endpoint can take 30 to 60 seconds for a page it's never seen before. that's on their side, nothing to do about it.
nothing leaves your machine except the actual submissions to the two
archive services, which is what you asked for by clicking the button.
history is chrome.storage.local. no analytics, no pings.
activeTab and scripting to read the page html for the local save.
downloads to write the file. storage for the history list. host
permissions for web.archive.org, archive.today, archive.ph.
mit.