ArchiveBox
An open-source extension that sends your pages to your own ArchiveBox server to keep.
Before you install: This extension needs your own ArchiveBox server. It is a client for that server, not a stand-alone bookmark manager. The README setup steps use an ArchiveBox 0.9.0 API key.
Why it's a strong pick
ArchiveBox is for keeping pages that might disappear. You choose the server that stores them. It is open source under the MIT license, and its code is public on GitHub. It uses Manifest V3, Chrome's current extension format. The README says v3.2.0 (May 2026) moved it to Manifest V3. The latest repo commit we found, on 23 September 2026, bumped it to 3.3.3.
What it does
The README says it lets you send individual browser tabs, or all URLs matching patterns you set, to your ArchiveBox instance for offline preservation. You can save the current page by button, by shortcut (Ctrl+Shift+X) or from the right-click menu.
Key features
- Save in several ways. Button, shortcut or right-click.
- Auto-archive. Match URL patterns, with allow and deny lists.
- Bulk import. Bring in URLs from your history or bookmarks.
- Organise. Search, sort and tag saved URLs.
- Local copies. Screenshots, MHTML copies on Chrome and Edge, and optional SingleFile HTML copies.
- Export. CSV, JSON, PNG, HTML, MHTML or ZIP.
- Cookie sync. Send chosen login cookies to an ArchiveBox auth profile.
Who it's for
ArchiveBox is for people who run their own ArchiveBox server and want to preserve pages against link rot. If you only want a simple list of links, look at the other bookmark managers below.
What permissions does ArchiveBox ask for?
The build config asks for storage, alarms, activeTab, contextMenus and unlimitedStorage. It lists history, bookmarks, cookies, tabs, scripting and pageCapture as optional, plus optional access to all sites. We read the build config, not the built manifest. Read the install prompt before you add it.
Do I need my own ArchiveBox server?
Yes. The extension sends pages to an ArchiveBox instance you run. Without one, it has nowhere to save your pages. Set up the server and an API key first, following the README steps, then connect the extension to your server's address.
Is the cookie sync safe to turn on?
Only for a server you trust. The README lists cookie sync, which sends login cookies you choose to an ArchiveBox auth profile on your server. Anyone with access to that server could see them. This advice is ours: leave the feature off unless you need it.
Can I trust its privacy?
We could not read the developer's privacy policy when we checked; read it before installing. The README says imported Safari files are parsed locally and that passwords and payment cards are ignored. It sends saved URLs to the server you set up.
FAQ
Is it a bookmark manager on its own? No. It needs your ArchiveBox server.
Which formats can I export? CSV, JSON, PNG, HTML, MHTML or ZIP, per the README.
Is it open source? Yes, under the MIT license.
Good to know
Start with the manual save button on a few pages before you turn on auto-archive. Auto-archive sends every URL that matches your patterns to your server, so use the deny list to keep private pages out.
Other bookmark managers to compare
ArchiveBox is one of 6 picks in our bookmark managers guide:
- Floccus: sync browser bookmarks through storage you choose.
- Linkwarden: save links to your Linkwarden collections.
- Karakeep: save links to your Karakeep app.
- linkding Extension: save links to your linkding server.
- Wallabagger: save pages to your wallabag server.
This is a third-party extension, not built or maintained by Xplorekit. We link to the official Chrome Web Store listing — install and permissions are entirely between you and the extension's own publisher.