Done configuring clients? Continue to the next step in the Setup Guide.

Download Clients

A download client handles NZB downloads for Huntarr. Only usenet clients are currently supported — torrent support is coming soon.

Recommended
NZB Hunt Built-in
Zero configuration required. Built directly into Huntarr — no external software, no remote path mappings, just works.
SABnzbd / NZBGet
External clients. Requires host, port, and API key configuration. If running in Docker, you'll likely need Remote Path Mappings below.
Add Client

Remote Path Mappings

Not needed with NZB Hunt. Since NZB Hunt runs inside Huntarr, it uses the same paths — no remote path mappings required.
You're using an external download client. If Huntarr and your client run in different Docker containers (or different machines), they likely see different paths. You'll need to map the client's download path to Huntarr's path.

When your download client and Huntarr don't see the same folder paths, you need a mapping: tell Huntarr which local path on your system corresponds to the remote path the client uses. If running in Docker, paths inside the container are usually different from the host, so remote path mappings are typically required for external clients. If both run on the same machine with the same paths, you can leave this empty. For more detail see the wiki.

Host Local Path Remote Path

Edit Remote Path Mapping

The same host you specified for the remote Download Client

Path that Huntarr should use to access the remote path locally

Root path to the directory that the Download Client accesses

Add Download Client

Only usenet clients are supported. Torrent support is coming soon.

NZB Hunt Built-in
Zero config. No external software or remote path mappings needed.
Recommended
SABnzbd Beta
External usenet client. Requires host, port, and API key. Support is under development and may not be fully stable.
NZBGet Beta
External usenet client. Requires host, port, and password. Support is under development and may not be fully stable.