Mount Usenet NZB content as a network drive and stream media without waiting for downloads
Replace SABnzbd as the download target for Sonarr or Radarr via the compatible HTTP API
Run a watchdog that verifies and re-fetches broken Usenet posts automatically
Configure multiple Usenet providers with failover and per-provider usage tracking
No published Docker image, so you must git clone then docker build before running, and configure Usenet provider credentials and indexers.
NzbDavEx is a self-hosted server that presents NZB files as if they were folders and files on a normal disk. An NZB is a small index file used by Usenet clients that points at posts on Usenet servers, the way a torrent file points at peers. Normally a downloader has to pull every part down to local storage before you can read anything. NzbDavEx skips that step: it exposes the content over WebDAV, the same protocol macOS Finder and many file managers can mount as a network drive, and only fetches the bytes you actually read. The server supports random-access reads, including seeking inside RAR and 7z archives, and inside password-protected archives. That means a media player or another program can open a file directly from the mount and jump to any point without waiting for a full download. The project also ships an HTTP API that is compatible with SABnzbd, a popular Usenet downloader, so any automation tool that already speaks SABnzbd can use NzbDavEx as a drop-in target. NzbDavEx is an extended fork of an earlier project called nzbdav. The added features include a Watchdog module that runs unattended verification and re-fetch jobs based on user rules, support for several Usenet providers with failover and per-provider usage tracking, an indexer manager configurable from the UI, a profile system for per-profile quality and handling policies, and an updated settings interface. There are also health checks that detect when content has gone missing upstream and trigger replacements. There is no published Docker image. Installation is a git clone, then docker build, then docker run, exposing port 3000. To keep settings between runs you mount a host folder at /config, and there are PUID and PGID environment variables for file ownership. A more detailed setup guide covers Docker Compose, mounting through Rclone, and tuning. The README ends with a disclaimer that the software hosts no content itself and that the user is responsible for following the law and provider terms of service.
Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.