Avera
Browser connector

Browser connector

Save references and PDFs from Chrome into Avera.

The Avera Connector is a Chrome extension that detects scholarly references on the web and sends them to your desktop library.

Requirements

  • Google Chrome (extension is Chrome-focused today)
  • Avera desktop app running for imports (except when testing error states)
  • Native messaging registered between Chrome and Avera (automatic in production installs)

Install (production)

  1. Install Avera Connector from the Chrome Web Store when available.
  2. Install and launch Avera.
  3. Visit a publisher or database page — a floating Add to Avera banner may appear when references are detected.

Production builds connect through native messaging — no manual port or token.

Install (development / unpacked)

  1. Chrome → Extensions → enable Developer mode.
  2. Load unpacked and select the connector extension folder from your Avera install or source tree.
  3. Copy the 32-character extension ID from chrome://extensions.
  4. Register the native host (from the app install or dev environment), then reload the extension and launch Avera.

See your install docs for the exact register:native-host command if you build from source.

Using the connector

  1. Open a page with a DOI or article metadata (PubMed, publisher sites, Google Scholar, and many others).
  2. Use the floating banner to save, or open the toolbar popup.
  3. When multiple references exist on one page, pick from the list before importing.
  4. The toolbar badge shows how many references were detected.

PDF import

The connector can attach PDFs using your browser session — including institutional logins when the PDF is reachable. If PDF capture fails, Avera still imports metadata only.

Batch import

Select multiple DOIs or references in the popup for batch import.

MessageMeaning
Connected to Avera.Ready to import
Is Avera running?Launch the desktop app
Connector disabledEnable the connector in Settings

Settings in Avera

Open Settings → Browser connector to:

  • View native messaging status
  • Register native host when needed
  • Enable HTTP connector (dev) with port and bearer token for development fallback

After import

The library usually refreshes automatically and may show a toast. See Sync.

Troubleshooting

Connection errors, wrong extension ID, and institutional PDF edge cases: Connector troubleshooting.

On this page