Unpackerr

Unpackerr is a daemon that automatically extracts RAR archives from completed downloads so media managers like Sonarr, Radarr, Lidarr, and Readarr can import…

  • Automation
  • Media Applications
  • Media Servers
  • Tools & Utilities
Unpackerr is a daemon that automatically extracts RAR archives from completed downloads so media managers like Sonarr, Radarr, Lidarr, and Readarr can import them without manual intervention. It also supports standalone extraction from a watch folder for users who don't rely on the *arr suite.

Platform availability

Available on 5 of 10 platforms

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.

78/100 Good

Maintained
95last commit 22 days ago
Popular
641,517 GitHub stars
Easy to install
755 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
Security check
78no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 6.4/10

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

GitHub stars
1,517
Open issues
5
Last commit
2026-10-30
Latest release
v1.0.1
License
MIT
Activity
declining

Checked 21 days ago - source: GitHub (davidnewhall/unpackerr)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 1 GB disk. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Keep your settings file and prefix safe Save your unpackerr.conf settings file (a simple TOML text file) somewhere safe and point Unpackerr to it with --config; also choose a --prefix, which is short text added to output folders. If you lose or break that file, Unpackerr can stop working because it no longer knows where your downloads and output folders live. source
  • Allow port 5656 for the web dashboard Unpackerr’s dashboard and API usually answer on port 5656, so open that port on your firewall if you need to reach it from other devices. If it is blocked, the app may be running but you still won’t be able to open it in a browser or send API calls. source
  • Test your webhook before real files run Run the example command unpackerr -w 4 to send a sample “extracted” webhook (a small HTTP notification) to your receiver. If that test fails, real notifications to your apps may not arrive when files are done. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

In Docker, why do Starr apps fail to import files extracted by Unpackerr?

This often happens when Unpackerr runs as a different user than the Starr apps. Start the container with the proper uid and gid so it writes files that the other containers can read.

What port do I need open for the Unpackerr web dashboard?

Open port 5656 for the dashboard and API. If the firewall blocks it, Unpackerr may be running but you cannot open it in a browser or send API calls.

What configuration file should I back up for Unpackerr?

Save the unpackerr.conf TOML file and point Unpackerr to it with --config. Also choose a --prefix that is added to output folders, because losing the config can make it forget your download and output locations.

How do I check that my notification receiver works before extracting real files?

Run unpackerr -w 4 to send a sample extracted webhook to your receiver. If that test fails, real notifications to your apps may not arrive when extraction finishes.

Answers sourced from github.com, github.com, unpackerr.zip

Community

Collected 53 days ago - public community threads