Direct NNTP Usenet Engine
Multi-connection downloading with TLS 1.3 encryption, automatic yEnc decoding, and built-in PAR2 verification and repair.
Download straight from your own NNTP server over TLS 1.3, manage SABnzbd, Radarr and Sonarr, then read EPUB, PDF, CBZ and CBR files in the same app. Credentials stay encrypted on your device.
No account. No sign-up. Bring your own server.com.emeraldnzb.app
Connection active
28.4 MB/s
3.8 GB
1.6 GB
412 MB
Interface preview. Values shown are illustrative.
Each capability is implemented against the protocol or format it depends on, rather than wrapped around a remote service.
Multi-connection downloading with TLS 1.3 encryption, automatic yEnc decoding, and built-in PAR2 verification and repair.
Hardware-accelerated video and audio playback straight from local downloads, no external player handoff.
Read EPUB, PDF, CBZ and CBR files natively with clean page navigation and dark reading modes.
One low-latency search across every indexer you configure, with results merged into a single list.
Monitor download queues and automation libraries from one dashboard, with connection health at a glance.
Server hostnames, ports, API keys and credentials stay encrypted inside Android's local app sandbox.
Requests travel from your phone to servers you choose. There is no middle layer, and no copy of your credentials anywhere else.
Server logins, indexer keys and automation endpoints are written to Android's local app sandbox. No account is created and nothing is uploaded to a developer server.
The app opens its own TLS connections to the NNTP server, Newznab indexers and SABnzbd, Radarr or Sonarr instances that you enter. Hostnames and ports are never shared.
Downloads, e-books and comic archives are stored in local app storage, then opened by the built-in player or reader. Deleting the app removes them.
BYOS Notice
Emerald NZB is strictly a client utility. It does not host, provide, index, or distribute any media files, e-books, comics, Usenet server access, or content feeds. Users must supply their own third-party Usenet servers and their own Newznab API keys.
The developer has no visibility into, and no responsibility for, the servers you connect to or the content you access with the app. Availability, retention and legality of that content rest entirely with you and your providers.
What you bring