Jackett vs Prowlarr

Editor take

Choose Jackett for one feed URL across every tracker you add and for TorrentPotato clients. Choose Prowlarr for indexer sync into the Arr apps and for Usenet indexers beside torrents.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

Jackett

Where Jackett is stronger

  • One feed for every trackerJackett's "all" indexer returns one combined feed for every tracker you added, though its README suggests separate feeds where a client takes several; Prowlarr lists each indexer on its own address.1
  • TorrentPotato clients work tooJackett answers the TorrentPotato API as well as Torznab, so CouchPotato can use it; Prowlarr serves Newznab and Torznab addresses only.2

Prowlarr

Where Prowlarr is stronger

  • Indexers sync to the Arr appsSonarr, Radarr, Lidarr, Readarr, Mylar3, Whisparr and LazyLibrarian take their indexers from Prowlarr and stay in step; with Jackett each app holds its own copy.3
  • Torrent and Usenet togetherOne indexer list covers torrent trackers and Usenet indexers; Jackett proxies torrent trackers only.4

Jackett vs Prowlarr: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceGPL-2.0GPL-3.0
Web UIYesYes
DockerYesYes
Linux packageYesYes
WindowsYesYes
macOSYesYes
Tech stack.NET.NET
Docker Containers1 (app only)1 (app only)
Databasefile onlySQLite
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Jackett docs and Prowlarr docs.

Updated