cross-seed

cross-seed

Official

Docker app from ambipro's Repository

Overview

Fully-automatic cross-seeding GitHub: https://github.com/cross-seed/cross-seed Documentation/Support: https://cross-seed.org/docs/tutorials/Unraid Official Containers: https://github.com/cross-seed/cross-seed/pkgs/container/cross-seed Official Docker Hub Mirror: https://hub.docker.com/r/crossseed/cross-seed

cross-seed: Fully-automatic cross-seeding

cross-seed is an app designed to help you download torrents that you can cross seed based on your existing torrents. It is designed to match conservatively to minimize manual intervention.

Requirements

  • Node >= 24
  • Any indexers that support Torznab (through Prowlarr or Jackett)
  • At least one torrent client: rTorrent, qBittorrent, Deluge, or Transmission

Tutorial

Head on over to cross-seed.org to get started.

Troubleshooting

Feel free to start a discussion, or reach out on Discord.

Releases and Branches

cross-seed roughly follows semantic versioning. Every release has a corresponding git tag. Git branches do not represent released code.

Versions that look like v0.0.0 are releases and are considered stable. Versions that look like v0.0.0*-0* are prereleases and are not considered stable.

We also publish Docker images at ghcr.io/cross-seed/cross-seed under several tag patterns: :branch, :6, latest.

  • latest - the most recent release.
  • prerelease - the most recent release or prerelease.
  • master - The main development branch. Code that is intended for release, but has not necessarily released yet. This is similar to prerelease but gets new code first so is slightly more bleeding edge.
  • nightly - for open experimental PRs. Not always used and may fall behind master.

Install cross-seed on Unraid in a few clicks.

Find cross-seed in Community Apps on your Unraid server, review the template, and click Install. Unraid handles the Docker app or plugin setup from the published template.

Open the Apps tab on your Unraid server Search Community Apps for cross-seed Review the template variables and paths Click Install

Related apps

Explore more like this

Explore all

Details

Repository
ghcr.io/cross-seed/cross-seed:latest
Last Updated2026-07-17
First Seen2023-11-21

Runtime arguments

Network
bridge
Shell
sh
Privileged
false
Extra Params
--user="99:100"

Template configuration

configDirPathrw

This is your configuration, logging, and torrent_cache appdata directory. A configuration file (config.js) with suggested base defaults will be generated on your first start of the container. If you already have a config.js file, you can find the latest template at the link below. Configure and rename the template to config.js and place in this directory before running. https://github.com/cross-seed/cross-seed/blob/master/src/config.template.cjs

Target
/config
Default
/mnt/user/appdata/cross-seed
Value
/mnt/user/appdata/cross-seed/
portPorttcp

Required when using daemon mode. Make sure your container port matches the port option in the config file.

Target
2468
Default
2468
Value
2468
dataPathrw

This is an optional path for use with linking enabled or as a source for data-based searching. You may need to add more of these mounts if you have multiple drives without using drive pooling. https://cross-seed.org/docs/tutorials/linking

Target
/data
torrentDirPathro

This is unnecessary with useClientTorrents: true. This volume mount should contain all of your torrent clients .torrent files. If you don't know where your torrent client stores its file, this will typically be your somewhere in your torrent client's appdata folder. https://cross-seed.org/docs/basics/options#torrentdir

Target
/torrents
outputDirPathrw

This is unnecessary in most cases, cross-seed will default to /config/cross-seeds. This directory is used as a working directory for cross-seed injections or when using action: save. https://cross-seed.org/docs/basics/options#outputdir

Target
/cross-seeds