Repository navigation
Download Clients and Sources
ROMarr needs two things to download a game: a search source that lists releases, and a download client that fetches them.
Settings → Download Clients. Supported:
- Torrent: qBittorrent, Transmission, Deluge, rTorrent, Synology Download Station, Vuze, BiglyBT, uTorrent, aria2, Flood, Freebox, Hadouken, Porla, and Mister Download Manager (built-in BitTorrent).
- Usenet: SABnzbd, NZBGet, NZBVortex, and built-in Usenet (NNTP).
- Debrid and cloud: Real-Debrid, AllDebrid, Premiumize, TorBox, Debrid-Link, Offcloud, put.io, LinkSnappy.
- Other: torrent and Usenet blackhole folders, direct HTTP, browser downloads, and the ROM Hub client for plugins.
Always use Test before saving.
qBittorrent:
- Each grab gets a unique ROMarr tag, which is how Queue matches progress and imports, even when the torrent is renamed.
- If qBittorrent already has the exact same magnet and no ROMarr request owns it, ROMarr attaches to that torrent instead of failing.
- Progress, speed and ETA appear in Queue.
Settings → Indexers. Prowlarr, Torznab/Newznab indexers, and torrent RSS feeds. ROMarr respects indexer rate limits and lets you set timeouts.
If Prowlarr manages your indexers, connect Prowlarr. An empty Prowlarr has nothing to search, so check each indexer's Test and game categories there.
A Usenet setup has three parts: a provider (NNTP login), a Newznab indexer (search), and a client (built-in Usenet, SABnzbd or NZBGet). A provider account alone returns no search results. See USENET.md.
The client's completed download path must be readable by ROMarr at the same path, or mapped under Settings → Media Management → Remote path mappings.
More: FEATURES.md, INDEXER-RESILIENCE.md.
ROMarr is MIT licensed · Report a problem · Detailed, release-tracked docs live in the repository's docs folder.