The browser extension captures pages as you visit them. Browser imports read URLs from existing history or saved bookmarks and fetch their current contents. You can use imports to bring in existing content and the extension to capture future visits.
Choose the Right Method
| Goal | Use | Why |
|---|---|---|
| Index pages from now on | Browser extension | It captures rendered page content automatically while you browse |
| Capture pages behind a login | Browser extension | It sees the page already rendered in your signed in browser tab |
| Bring in existing browser history | hister import browser | It reads qualifying URLs from the browser history database |
| Bring in saved browser bookmarks | hister import browser bookmarks | It reads saved URLs, including bookmarks you have never visited |
| Index an entire public site | Website crawler | It follows permitted links instead of relying on your visit history |
| Keep browser data continuously synchronized | No direct option | History and bookmark imports run explicitly and do not continuously sync |
Browser Extension Capture
The extension reads the current tab after the page loads. It submits the URL, title, extracted text, rendered HTML, and favicon to your configured Hister server. It also watches for content changes made by applications that update a page without a full navigation.
This means the extension can index content that a normal crawler cannot see, including pages rendered with JavaScript and pages available through your signed in browser session. It also means private account pages can be submitted. Configure skip rules for sites or paths that should never be stored, and review the sensitive content patterns.
The extension only handles pages visited after it is installed and enabled. It does not scan old browser history, bookmarks, downloads, cookies, or browser caches. It does capture the rendered page, which can contain private or sensitive information. Browser internal pages such as about: and chrome: pages cannot be captured.
For installation, authentication, controls, and shortcuts, see Browser Extension.
Browser History Import
Browser history databases contain URLs, titles, visit counts, and timestamps. They normally do not contain complete historical page contents. When you run:
hister import browserHister detects a supported browser database, reads qualifying URLs, and asks its crawler to fetch the pages that exist now. The resulting indexed content can differ from what you originally saw. A page may have changed, disappeared, moved, or started requiring authentication.
The --min-visit option can use the browser’s visit count to choose URLs. The --start-date option selects URLs whose most recent recorded browser visit is
on or after the given date. These filters do not recreate the browser’s
original visit timeline or preserve every historical visit as a Hister record.
The indexed document timestamps describe the imported page fetch.
The import does not inherit the browser session. Sites that need login cookies may return a login page or reject the request. You can select a browser based crawler backend and provide cookies explicitly when appropriate. Treat exported cookies as secrets.
Browser imports use persistent crawl jobs so an interrupted import can resume. The job records remain in the Hister database until you remove the job with hister crawl delete JOB_ID.
See Importing Browser History for supported browsers, filtering, backends, cookies, and resume commands.
Browser Bookmark Import
Import saved bookmarks from Firefox based browsers, Chromium based browsers, or Ladybird:
hister import browser bookmarks
hister import browser bookmarks --browser firefoxHister reads saved URLs, including bookmarks you have never visited, then fetches and indexes the current pages. Use --browser to select a browser or --db to select a bookmark store. Documents receive the bookmarks label by default; --label LABEL overrides it.
Like history imports, bookmark imports use persistent crawl jobs and do not inherit your signed in browser session. They apply allow and skip rules and support the same crawler backends and request options. The history filters --min-visit and --start-date do not apply to bookmarks.
See Importing Browser Bookmarks for supported stores, examples, and resume commands.
How Repeated Visits Behave
Hister stores one current document for each normalized URL and owner. If the extension submits that URL again, the current document is updated and its Hister submission count increases. Hister does not keep a complete snapshot for every visit.
If the URL matches a versioning rule and its content changes, Hister stores a difference record that can reconstruct earlier content. Version tracking is optional and has no automatic expiry. See Data Storage and Lifecycle.
What Deleting at the Source Does
Browser ingestion is not bidirectional sync.
- Clearing browser history does not delete Hister documents.
- Removing a bookmark does not delete an imported Hister document.
- Disabling or uninstalling the extension stops future capture but does not delete data already on the server.
- Deleting a Hister document does not change browser history, bookmarks, or source websites.
Use Hister deletion controls separately. See Deleting Documents.