SABnzbd - The automated Usenet download tool http://sabnzbd.org
  • Python 83.4%
  • JavaScript 9.5%
  • CSS 3.7%
  • NSIS 2.8%
  • HTML 0.5%
Find a file
SABnzbd Automation cc61dc974b Update translatable texts
[skip ci]
2026-05-26 14:54:59 +00:00
.github Pin tempora to 5.8.1 2026-05-26 16:45:58 +02:00
.tx
builder Update all dependencies (#3436) 2026-05-26 15:53:21 +02:00
context
email
icons
interfaces Remove disableDelays because config is not defined (#3438) 2026-05-26 06:50:24 +02:00
licenses
linux Add French & Turkish translations to appdata.xml (#3439) 2026-05-26 14:38:21 +02:00
macos
po Update translatable texts 2026-05-26 14:54:59 +00:00
sabnzbd Add logging of unhandled connection exceptions and wait_for result (#3440) 2026-05-26 16:54:19 +02:00
scripts Enable additional Ruff checks and implement fixes 2026-05-13 21:50:32 +02:00
snap Work around pyproject.toml handling in snap build 2026-05-18 09:07:20 +02:00
tests Add logging of unhandled connection exceptions and wait_for result (#3440) 2026-05-26 16:54:19 +02:00
tools Introduce Ruff linter for improved code quality 2026-05-13 14:25:06 +02:00
win
.git-blame-ignore-revs
.gitignore Generalize .gitignore rules for hidden directories 2026-05-13 13:41:56 +02:00
COPYRIGHT.txt
GPL2.txt
GPL3.txt
INSTALL.txt Drop support for Python 3.9 2026-05-26 14:34:19 +02:00
ISSUES.txt
LICENSE.txt
portable.cmd
pyproject.toml Update type hints to use native union syntax and TypeAlias 2026-05-26 16:44:49 +02:00
README.md Drop support for Python 3.9 2026-05-26 14:34:19 +02:00
README.mkd
requirements.txt Pin tempora to 5.8.1 2026-05-26 16:45:58 +02:00
SABnzbd.py Drop support for Python 3.9 2026-05-26 14:34:19 +02:00

SABnzbd - The automated Usenet download tool

License Join our Discord

SABnzbd is an Open Source Binary Newsreader written in Python.

It's totally free, easy to use, and works practically everywhere. SABnzbd makes Usenet as simple and streamlined as possible by automating everything we can. All you have to do is add an .nzb. SABnzbd takes over from there, where it will be automatically downloaded, verified, repaired, extracted and filed away with zero human interaction. SABnzbd offers an easy setup wizard and has self-analysis tools to verify your setup.

If you want to know more you can head over to our website: https://sabnzbd.org.

Resolving Dependencies

SABnzbd has a few dependencies you'll need before you can get running. If you've previously run SABnzbd from one of the various Linux packages, then you likely already have all the needed dependencies. If not, here's what you're looking for:

  • python (Python 3.10 and above, often called python3)
  • Python modules listed in requirements.txt. Install with python3 -m pip install -r requirements.txt -U
  • par2 (Multi-threaded par2 installation guide can be found here)
  • unrar (make sure you get the "official" non-free version of unrar)

Optional:

  • See requirements.txt

Your package manager should supply these. If not, we've got links in our installation guide.

Running SABnzbd from source

Once you've sorted out all the dependencies, simply run:

python3 -OO SABnzbd.py

Or, if you want to run in the background:

python3 -OO SABnzbd.py -d -f /path/to/sabnzbd.ini

If you want multi-language support, run:

python3 tools/make_mo.py

Our many other command line options are explained in depth here.

About Our Repo

The workflow we use, is a simplified form of "GitFlow". Basically:

  • master contains only stable releases (which have been merged to master) and is intended for end-users.
  • develop is the target for integration and is not intended for end-users.
  • 1.1.x is a release and maintenance branch for 1.1.x (1.1.0 -> 1.1.1 -> 1.1.2) and is not intended for end-users.
  • feature/my_feature is a temporary feature branch based on develop.
  • bugfix/my_bugfix is an optional temporary branch for bugfix(es) based on develop.

Conditions:

  • Merging of a stable release into master will be simple: the release branch is always right.
  • master is not merged back to develop.
  • develop is not re-based on master.
  • Release branches branch from develop only.
  • Bugfixes created specifically for a release branch are done there (because they are specific, they're not cherry-picked to develop).
  • Bugfixes done on develop may be cherry-picked to a release branch.
  • We will not release a 1.0.2 if a 1.1.0 has already been released.

Privacy Policy

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.

Code Signing Policy

For our Windows release, free code signing is provided by SignPath.io, certificate by SignPath Foundation.