# What is eReader Relay? (/docs/what-is-ereader-relay)



eReader Relay turns writing from the web into EPUB books that are easier to read away from a noisy
browser. It can handle a single page on demand or assemble new feed and newsletter entries into a
scheduled edition.

## The four parts [#the-four-parts]

1. **Inputs** provide the writing: browser captures, public RSS or Atom feeds, and newsletters sent
   to a private subscription inbox.
2. **Reading lists** group one or more feed or newsletter inputs and define a daily, weekly,
   fortnightly, or monthly schedule.
3. **The EPUB library** keeps every generated book so you can read it in the web reader, download
   it, archive it, or send it again.
4. **Devices** are optional delivery addresses supplied by Kindle, Kobo, or another eReader
   workflow that accepts personal documents by email.

## One-off pages and scheduled editions [#one-off-pages-and-scheduled-editions]

The browser extension offers two actions:

* **Add to a reading list** saves the page to the exact list you select. It becomes an input for a
  future edition.
* **Send EPUB** builds a one-article EPUB and sends it to the devices you select as soon as the book
  is ready.

Scheduled reading lists work differently. At the chosen local time, eReader Relay looks for new
entries from every selected feed and newsletter, packages readable entries as chapters, stores the
book in your library, and delivers it to the selected devices.

## What eReader Relay removes [#what-ereader-relay-removes]

Article extraction keeps meaningful headings, text, links, and supported images on a best-effort
basis. Navigation, trackers, advertisements, scripts, forms, and unrelated page chrome are removed.
Interactive page behavior does not run inside an EPUB.

## What it does not do [#what-it-does-not-do]

* It does not monitor every page you visit.
* It does not bypass logins, paywalls, or private content.
* It does not turn X posts, long posts, or threads into books; only public X Articles are attempted.
* It does not guarantee that every JavaScript-rendered site can be read from its initial HTML.
* It does not require AI for its core ingestion or EPUB-generation workflow.

Next, [compare the available workflows](/docs/feature-comparison) or follow the
[quick start](/docs/quick-start).