Cleanuparr

Cleanuparr, formerly Cleanuperr, is an automation tool that keeps download queues clean across Sonarr, Radarr, Lidarr, qBittorrent, Deluge, and Transmission.

  • Automation
  • Downloaders
  • Media Applications
  • Media Servers
  • Tools & Utilities
Cleanuparr, formerly Cleanuperr, is an automation tool that keeps download queues clean across Sonarr, Radarr, Lidarr, qBittorrent, Deluge, and Transmission. It removes failed, stalled, slow, or orphaned downloads, manages seeding, applies blocklists, and provides a web interface for monitoring and configuration. It is aimed at self-hosted media users who want less manual cleanup of problematic or abandoned downloads.

Platform availability

Available on 6 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.

76/100 Good

Maintained
100last commit 23 days ago
Popular
692,690 GitHub stars
Easy to install
856 install platforms, install notes, Docker image
Light to run
85512 MB minimum RAM
Security check
201 serious finding, 8 minor, CI, tests

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

GitHub stars
2,690
Open issues
46
Last commit
2026-10-28
Latest release
v2.10.12
License
GPL-3.0
Activity
declining

Checked 22 days ago - source: GitHub (Cleanuparr/Cleanuparr)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 1 CPU core(s), 2 GB disk.

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

First-install notes

  • Start with Docker and set these values Map a real folder to /config, keep port 11011 mapped, and set PUID/PGID (the user/group IDs the container runs as) to your host user/group, often 1000. The config folder stores settings, the port opens the web page, and wrong IDs can create files you can't delete. source
  • Arch/Manjaro quick install with AUR If you're on Arch or Manjaro, run yay -Sy cleanuparr to install the package. It gives you a ready-to-run version, so you can start Cleanuparr without manually putting it together. source
  • Tell it which categories and folders to scan For each download client, enter its category (such as tv-sonarr or radarr) and the exact full folder paths starting with / that Cleanuparr should scan. If these are wrong, it may miss leftover download files or point at folders it should not clean. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker values should I use for a basic Cleanuparr deployment?

Map a real folder to /config, keep port 11011 mapped, and set PUID/PGID to your host user and group, often 1000. Wrong IDs can create files you cannot delete.

How can I install Cleanuparr on Arch or Manjaro?

Run yay -Sy cleanuparr to install the AUR package. It provides a ready-to-run version, so you can start Cleanuparr without manually putting it together.

What category and folder values should I configure for the download cleaner?

Enter the client category, such as tv-sonarr or radarr, and the exact full folder paths that start with /. If these are wrong, it may miss leftover files or point at folders it should not clean.

How does Cleanuparr handle stalled, slow, or failed-import downloads?

It strikes those downloads, removes them, and re-searches.

Answers sourced from bytesized-hosting.com, github.com, github.com

Community

Collected 48 days ago - public community threads