Listenarr

Listenarr is a cross-platform, self-hosted audiobook management server that automates searching, downloading, metadata enrichment, and serving audiobook…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Listenarr is a cross-platform, self-hosted audiobook management server that automates searching, downloading, metadata enrichment, and serving audiobook collections from torrent and newsgroup (NZB) indexers.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

81/100 Excellent

Maintained
100last commit 7 days ago
Popular
59938 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
No data
Security check
94no serious findings, 1 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 21 days ago

GitHub stars
938
Open issues
300
Last commit
2026-11-14
Activity
rising

Checked 7 days ago - source: GitHub (Listenarrs/Listenarr)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Manual setup needs .NET 10 and Node 24 If you are doing the manual setup, install the .NET 10.0 SDK (tools needed for the backend) and Node.js 24.x (a JavaScript runtime), then run npm run install:all in the project folder. Without them, the frontend dependencies won't install and the setup will fail. source
  • Optional: keep Discord helper working If you use the optional Discord bot helper, run npm install fetch-cookie tough-cookie in the project folder. That helps prevent occasional CSRF (a web-safety check that blocks unwanted requests) errors when the helper talks to Listenarr. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why can a manual Listenarr setup fail during frontend installation?

Manual setup needs the .NET 10.0 SDK and Node.js 24.x, and you must run npm run install:all in the project folder. Without those, the frontend dependencies will not install and the setup will fail.

How can I prevent occasional CSRF errors in the optional Discord bot helper?

Run npm install fetch-cookie tough-cookie in the project folder. This helps prevent occasional CSRF errors when the helper talks to Listenarr.

What download-related problem area is documented in the common issues guide?

The guide covers download client connectivity, along with Discord bot failures, database errors, search problems, and deployment issues.

Does Listenarr use Audible metadata when managing the library?

The project page says it can search, download, and organize your library automatically using metadata from Audible.

Answers sourced from deepwiki.com, github.com, github.com

Community

Collected 49 days ago - public community threads