# Supported content (/docs/supported-content)



eReader Relay accepts several kinds of writing, but each uses a different ingestion path.

| Input                          | Supported | Important limitation                              |
| ------------------------------ | --------- | ------------------------------------------------- |
| Public web article             | Yes       | Must expose a meaningful article in public HTML   |
| Public RSS or Atom feed        | Yes       | Must be a valid, publicly reachable feed          |
| Email newsletter               | Yes       | Must arrive through a private subscription inbox  |
| Public X Article               | Yes       | Posts, long posts, and threads are excluded       |
| Login-only or paywalled page   | No        | eReader Relay does not reuse your browser session |
| Private or local-network URL   | No        | Network-safety checks block private destinations  |
| Browser settings or local file | No        | The extension can submit normal HTTP(S) tabs only |

<Cards>
  <Card title="Web articles" href="/docs/supported-content/web-articles" />

  <Card title="RSS and Atom feeds" href="/docs/supported-content/feeds" />

  <Card title="Newsletters" href="/docs/supported-content/newsletters" />

  <Card title="X Articles" href="/docs/supported-content/x-articles" />

  <Card title="Devices and delivery" href="/docs/supported-content/devices-and-delivery" />
</Cards>

When a submission cannot be processed, eReader Relay records a stable outcome and reason code. See
[Article capture troubleshooting](/docs/troubleshooting/article-capture) for how to interpret it.