Manifest V3 MIT License 100% Client-Side Cross-Device Sync

Never lose a page again.

Auto-archive everything you read to the Wayback Machine — silently, automatically, the moment each page loads.

Download for Chrome / Edge Firefox (coming soon)

Free forever. No account. No server. No tracking.

What ChronoKeep does

▸

Automatic archiving

One second after every page loads, the URL is quietly submitted to web.archive.org/save/. No clicks required.

▸

Cross-device sync

Your ignore list, on/off toggle, and preferences sync across all your signed-in Chrome and Edge instances via chrome.storage.sync — no account we manage, uses the browser's own sync.

▸

Privacy ignore list

Domains and URL patterns you add are never archived. Defaults cover localhost, banking, webmail, PayPal, and more. You stay in full control.

▸

Archive history

The popup shows your last 100 archived pages with direct links back to the Wayback Machine snapshot. One click to verify any snapshot.

▸

Zero backend

All state in chrome.storage. The only outbound requests are to web.archive.org. No server, no database, no analytics, no ads.

▸

One-click pause

Hit the toolbar icon to toggle archiving on or off instantly. Status syncs to all your devices.

How it works

  1. 1
    Install — Download the zip from the latest GitHub release, extract it, open chrome://extensions, enable Developer Mode, and click Load Unpacked. Point it at the extension/ folder.
  2. 2
    Browse normally — ChronoKeep runs invisibly in the background. Every time a page finishes loading, it fires a save request to https://web.archive.org/save/<url>.
  3. 3
    Check snapshots any time — Click the toolbar icon to see the last 100 archived pages. Click any link to open its Wayback Machine snapshot. Open Options to manage your ignore list and preferences — changes sync to all your devices.

Extension UI

ChronoKeep
Auto-archiving enabled
Recent Archives
example.com/articlesaved
news.ycombinator.comsaved
wiki.example.org/pagesaved
Options
Wayback Machine

Popup — toggle + recent archives

Settings sync across your devices
Ignore List
localhost Remove
mail.google.com Remove
paypal.com Remove
mybank.com
Add

Options — cross-device synced ignore list

Install ChronoKeep

Not yet on the Chrome Web Store — load it directly from the GitHub release.

Chrome / Edge (Chromium)
  1. Download chronokeep.zip from the latest release
  2. Extract the zip
  3. Open chrome://extensions
  4. Enable Developer mode
  5. Click Load unpacked → select the extension/ folder
Firefox

Firefox AMO submission coming soon. For now, load as a temporary add-on via about:debugging → Load Temporary Add-on → select extension/manifest.json.

Download chronokeep.zip

FAQ

Does ChronoKeep send my data anywhere?
It sends only the URL of each visited page to web.archive.org. No personal data, no analytics, no server we own. See the privacy policy.
What about private pages — banking, email?
The default ignore list covers localhost, Gmail, Outlook, banking patterns, and PayPal. You can add any domain or URL pattern in Options. Ignored pages are never sent to the Wayback Machine.
Will pages in my ignore list show up in the Wayback Machine?
No. ChronoKeep never fires a save request for ignored URLs. Whether a page was previously archived by others is a separate question.
What is cross-device sync and how does it work?
Your ignore list, on/off state, and archive delay are stored in chrome.storage.sync. Chrome and Edge automatically sync this data across all your signed-in browser instances using your Google or Microsoft account — no account on our end, no backend. History stays local-only because it can be large.
Does the extension work in Firefox?
The extension targets MV3. Firefox supports MV3 from v109. Load it temporarily via about:debugging. AMO submission is planned.
Can I archive pages that are behind a login?
The Wayback Machine save endpoint fetches the page as an anonymous user — it sees the logged-out version. ChronoKeep submits the URL but the snapshot quality depends on how much of the page is public.
Does archiving slow down my browsing?
No. The archive request fires in a background service worker with a configurable delay (default 1 second after page load). It has no impact on page rendering.
Is this open source?
Yes. MIT license. Source on GitHub.