# Browser extension (/docs/guides/browser-extension)



The browser extension handles one public article at a time. It supports Chrome and Firefox. Safari
is not currently available.

## Install a build [#install-a-build]

During private testing, use the development package supplied with the release. Development builds
connect to `dev.ereaderrelay.com`; production builds connect to the production service. Store
installation instructions will be added when the extension is published.

## Sign in [#sign-in]

1. Open the extension and select **Sign in to eReader Relay**.
2. Sign in in the separate browser window.
3. Select **Allow extension**.
4. After the approval window closes, reopen the extension if your browser also closed its popup.

The extension resumes the pending approval and should show your account name, reading lists, and
devices. It never asks you to paste an account token.

> **Screenshot to add — Signed-out extension:** Show the extension popup and **Sign in to eReader
> Relay** button. Do not include browser profiles or personal bookmarks.

> **Screenshot to add — Approval window:** Show the eReader Relay permission screen with **Allow
> extension**. Use a test account.

## Add the page to a reading list [#add-the-page-to-a-reading-list]

1. Open a readable public article over HTTP or HTTPS.
2. Open the extension.
3. Choose the exact reading list.
4. Select **Add to *list name***.

The success view names the list that received the article and links back to it. The captured article
is included when that reading list next runs.

## Send an EPUB now [#send-an-epub-now]

1. Toggle on every device that should receive the article.
2. Select **Send EPUB**.
3. Wait for the queued confirmation.

eReader Relay builds a one-article EPUB, stores it in the library, and sends it automatically as soon
as it is ready. A direct EPUB contains the article itself, without a numbered edition title or a
visible table of contents.

## Remembered choices [#remembered-choices]

The extension remembers the last reading list and device selection in browser-local extension
storage. On first use, a single available device is selected automatically. If you deliberately turn
every device off, that all-off choice is preserved. Removed or inaccessible destinations are cleared
the next time the extension refreshes them.

## Pages the extension cannot access [#pages-the-extension-cannot-access]

The current tab must be a normal `http://` or `https://` page. Browser settings, extension pages,
new-tab pages, local files, login-only pages, and private content cannot be captured. X has a stricter
policy: only [public X Articles](/docs/supported-content/x-articles) are attempted.

If the account still looks signed out after approval, see [Extension sign-in
troubleshooting](/docs/troubleshooting/sign-in).