Flood

Self-hosted torrent management, honestly reviewed. No marketing fluff, just what you get when you run it on your own server.

TL;DR

• What it is: A Node.js + React web interface that sits in front of your existing torrent client (rTorrent, qBittorrent, Transmission, or Deluge) and replaces its default UI with something modern and touch-friendly [1][2].
• Who it’s for: Self-hosters running *arr stacks (Sonarr, Radarr, Lidarr) or seedboxes who want a cleaner dashboard than qBittorrent’s built-in web UI or rTorrent’s aging ruTorrent interface [1].
• Cost savings: Flood is GPL-3.0 and free. Commercial BitTorrent clients with premium features (uTorrent Pro, BitComet Gold) run $15–25/year. The real saving is avoiding seedbox providers’ proprietary control panels or hosted solutions — you run this on a VPS you already own [2].
• Key strength: Multi-client support — one UI for rTorrent, qBittorrent, or Transmission, whichever you run. Clean interface with responsive design, light/dark themes, and 20+ language translations [1][2].
• Key weakness: The last tagged release is 4.7, dated October 2021. That’s nearly five years of silence on versioned releases. The GitHub repository shows ongoing activity, but if you need stable, versioned software with changelogs, this raises questions about long-term maintenance trajectory [1][2].

---

What is Flood

Flood is a monitoring service and web interface for torrent clients. It doesn’t download torrents itself — it connects to rTorrent, qBittorrent (v4.1+), Transmission, or Deluge (v2+, experimental) via their respective APIs and renders a unified, modern web UI on top [1].

The project was originally created as a replacement for ruTorrent, which is rTorrent’s traditional PHP-based web UI. ruTorrent works but it looks and feels like software from 2010. Flood gives rTorrent users a React frontend with smooth interactions and a design that doesn’t require an apology when you share a screen.

The current maintained fork is jesec/flood on GitHub, which took over from the original jfurrow/flood. It’s written in Node.js on the backend and React on the frontend, has a documented REST API, and supports Docker installation as well as npm global install [1]. As of this writing it sits at 2,724 GitHub stars [merged profile].

The project pitch on the website homepage is honest: “A beautiful web UI for various torrent clients.” That’s exactly what it is — no more, no less [2].

---

Why people choose it

The *arr ecosystem (Sonarr, Radarr, Lidarr, Prowlarr) drives most of Flood’s adoption. These automation tools manage your media library, but they still need a torrent client to do the actual downloading. Most self-hosters running this stack use qBittorrent or rTorrent under the hood, and Flood slots in as the human-facing interface when you want to inspect what’s downloading, tweak queue priorities, or manage trackers manually.

The second group is seedbox users. Managed seedbox providers (Ultraseedbox, Seedbox.io, others) often offer Flood as a panel option specifically because it’s cleaner than qBittorrent’s built-in web UI and far more modern than ruTorrent. If you’re renting a seedbox, you may already have Flood without realizing it was a discrete project.

The third case is rTorrent-specific: ruTorrent is the de facto standard rTorrent web UI, but it’s PHP, it’s dated, and the installation is notoriously finicky. Flood’s rTorrent support is its most mature (with dedicated test coverage), and for anyone already invested in the rTorrent ecosystem, it’s the cleanest upgrade path [1].

What Flood doesn’t do: it’s not a torrent indexer, it doesn’t manage your media library, and it doesn’t replace Jackett or Prowlarr. It’s purely the dashboard layer.

---

Features

Based on the GitHub README and website:

Client support:

• rTorrent (rakshasa/rtorrent and jesec/rtorrent variants, both supported with JSON-RPC) [1]
• qBittorrent v4.1+ (fully tested) [1]
• Transmission (fully tested) [1]
• Deluge v2+ (experimental — not covered by integration tests) [1]

Interface:

• Responsive design, collapsible sidebar — works on mobile and tablet [2]
• Light and dark themes, follows system preference by default [2]
• 20+ language translations via Crowdin integration [2]
• Touch screen support explicitly advertised [2]

Integration and API:

• REST API, documented inline in source code and via a community documentation site at flood-api.netlify.app [1]
• Unofficial client API libraries listed in the project wiki [1]
• Unofficial API integrations list maintained separately [1]
• Semantic versioning — the API contract is stable across minor versions [1]

Installation:

• npm global install (npm install --global flood) [1]
• npx without installation (npx flood) [1]
• Docker [merged profile]
• Single-executable builds available in GitHub Releases for Linux, macOS, Windows — bundles Node.js [1]
• Installable as a system service via wiki instructions [1]

Configuration:

• CLI-based configuration (flood --help) [1]
• Full schema in shared/schema/Config.ts [1]

Release 4.7 changelog highlights: size by tag or tracker, performance improvements, bug fixes (October 2021) [2].

What’s notably absent from the feature list: no built-in torrent search, no indexer integration, no media library management, no mobile app. It is a UI layer, full stop.

---

Pricing: SaaS vs self-hosted math

There is no SaaS version of Flood. This is a purely self-hosted open-source project with no cloud tier, no freemium, and no vendor behind it selling support contracts [1][2].

Flood self-hosted:

• Software license: $0 (GPL-3.0) [merged profile]
• VPS to run it on: $5–15/month depending on provider and your torrent client’s resource requirements
• Time to set up: 30–60 minutes for someone comfortable with Docker

What you’re replacing:

If you’re on a managed seedbox, the seedbox itself might cost $8–25/month depending on the provider and storage tier. Flood is typically included as a free panel option — you’re not saving money there; you’re just getting a better interface than the default.

If you’re self-hosting your torrent setup already, Flood costs nothing beyond the VPS you’re already paying for.

If you were paying for something like BitTorrent Web (the proprietary BitTorrent Inc. product) or using uTorrent Pro ($19.95/year) just for a web interface, switching to a self-hosted qBittorrent + Flood stack eliminates that line item.

The honest financial framing: Flood’s value isn’t primarily cost savings. Most people who need it are already self-hosting. The value is getting a significantly better interface over the built-in web UIs of free clients, without paying anything extra.

---

Deployment reality check

Flood installs via npm or Docker. The single-executable releases are a thoughtful addition for users who don’t want to manage Node.js installations separately [1].

What you actually need before installing Flood:

• A running torrent client: rTorrent, qBittorrent, Transmission, or Deluge — Flood connects to these, it doesn’t replace them
• Node.js (Current or Active LTS) if not using the bundled executable [1]
• A reverse proxy (nginx, Caddy) if you want HTTPS — not bundled
• For rTorrent specifically: if you’re on rakshasa/rtorrent >0.15.1 with JSON-RPC, two additional config lines are required in your rtorrent config [1]

What can go sideways:

• Deluge support is explicitly experimental. If Deluge is your client, test before committing [1].
• The rTorrent setup notes are easy to miss — if you skip the config lines for JSON-RPC-enabled rTorrent, the connection will fail silently.
• Configuration is CLI-only. There’s no web-based settings panel. This is fine for most setups but means any config changes require a service restart.
• The last versioned release is October 2021. The master branch has activity, but if you’re tracking the npm package, verify what version you’re actually getting and check the rolling builds from GitHub Actions [1].

What the setup experience is like in practice:

If you already have Docker and a torrent client running: 20–30 minutes to a working Flood instance, including reverse proxy setup. If you’re starting from scratch (VPS, torrent client, Flood): 2–4 hours. The Flood-specific piece is simple — the larger time investment is configuring the underlying client and reverse proxy, which you’d need regardless of UI.

The Discord server (link in the README) is the primary support channel [1]. For specific issues, GitHub Issues is the recommended path [1].

---

Pros and cons

Pros

• Multi-client support. One UI for rTorrent, qBittorrent, Transmission — useful if you switch clients or manage multiple servers with different clients [1].
• Modern, responsive design. Touch-ready, collapsible sidebar, works on mobile — this is a meaningful upgrade over qBittorrent’s built-in web UI and a large upgrade over ruTorrent’s dated interface [2].
• Light/dark theme. Follows system preference, switchable manually. Small thing, but ruTorrent doesn’t do this [2].
• REST API. Documented and with community client libraries. You can script against Flood or integrate it with other tools in your homelab stack [1].
• Zero cost. GPL-3.0, no commercial tier, no feature gating [merged profile].
• 20+ language support. Crowdin integration means translations are community-maintained and relatively current [1][2].
• Single-executable builds. No Node.js installation required — download, run, done [1].
• Active Discord. For a community project of this size (2,724 stars), having a real-time support channel matters [1].

Cons

• Last release: October 2021. Version 4.7 is nearly five years old. The master branch shows commits, but versioned releases have stopped. For production use, you’re either tracking rolling builds or running old software [1][2].
• Deluge support is experimental. If you’re on Deluge, Flood isn’t your safest bet — and the project’s own README flags this with an alembic emoji rather than a checkmark [1].
• No built-in torrent client. You must have rTorrent, qBittorrent, or Transmission already running and correctly configured. Flood adds zero downloading capability on its own.
• CLI-only configuration. No web-based settings panel. Config changes require editing config files and restarting the service. Reasonable for a homelab, inconvenient for less technical users.
• GPL-3.0 license. More restrictive than MIT. If you’re building a product on top of Flood, you need to understand the copyleft implications.
• No indexer integration. Flood doesn’t search for torrents — it only manages what you’ve already added. You’ll need a separate solution for finding content.
• Third-party review coverage is thin. No substantial independent reviews exist in mainstream tech publications, which makes it harder to validate real-world stability claims beyond GitHub issues and Discord anecdotes.

---

Who should use this / who shouldn’t

Use Flood if:

• You’re running rTorrent and want a modern UI that isn’t ruTorrent.
• You manage multiple servers with different torrent clients and want a consistent interface across them.
• You’re in the *arr ecosystem and want a cleaner manual dashboard for your torrent client.
• You’re on a seedbox where Flood is already offered as a panel option — use it, it’s better than the alternatives.
• You’re comfortable maintaining software that may not have tagged releases for extended periods.

Skip it (use qBittorrent’s built-in web UI instead) if:

• You’re a casual self-hoster with a single qBittorrent instance and the built-in web UI is good enough. The built-in UI improved significantly in recent qBittorrent versions.
• You want software with active, versioned releases and a predictable update schedule.
• You’re not already comfortable with Node.js or Docker.

Skip it (use Deluge’s built-in web UI) if:

• Deluge is your client. Flood’s Deluge support is experimental, and Deluge’s own web UI is stable.

Skip it entirely if:

• You want an all-in-one solution. Flood is a UI layer only — you still need to manage indexers, automation (Sonarr/Radarr), and storage separately.

---

Alternatives worth considering

• ruTorrent — the traditional rTorrent web UI. PHP-based, older design, but extremely feature-complete and battle-tested. If you need plugin compatibility (Autodl-irssi, etc.), ruTorrent is likely the better choice.
• qBittorrent’s built-in web UI — has improved significantly. If qBittorrent is your client, test the built-in UI before deciding you need Flood. It covers most use cases without the added dependency.
• Transmission’s built-in web UI — minimal but functional. For simple use cases, adding Flood just adds complexity.
• Deluge’s web UI — for Deluge users, use this instead of Flood’s experimental support.
• Sonarr/Radarr native client views — if you’re running *arr software, you can manage queue and history through those interfaces directly, reducing the need for a separate torrent UI.

For most self-hosters, the realistic question is: Flood vs. the built-in web UI of your chosen client. Flood wins on design and multi-client flexibility. The built-in UIs win on stability and fewer moving parts.

---

Bottom line

Flood is the right tool for a specific situation: you’re already invested in a torrent client with a weak or dated web UI (typically rTorrent), you want something that looks and works like a modern web application, and you’re comfortable maintaining community-supported software between versioned releases. For rTorrent specifically, it’s the best self-hosted web UI available. For qBittorrent and Transmission, it’s a meaningful UI upgrade, but the calculus depends on how much you care about design versus simplicity. The main risk is the release cadence — four-plus years without a tagged version is a yellow flag for anything running in production. Check the master branch health on GitHub before committing.

---

Sources

Primary sources:

1. GitHub repository — jesec/flood — README, supported clients, installation instructions, API documentation, configuration. https://github.com/jesec/flood (2,724 stars, GPL-3.0 license)
2. Official website — flood.js.org — Feature descriptions, release notes, homepage copy. https://flood.js.org

Note: The third-party review sources provided for this article [articles 1–5] were about natural flood events (WHO health topics, European Commission flood policy) and contained no information about the Flood torrent UI software. No relevant independent reviews were available in the source data. This article is based on primary sources only.