v1.13.0: Downloads in Jellydash 🎉

Jellydash now has an optional Downloads page for SABnzbd, qBittorrent, Transmission, Deluge and NZBGet. Follow your downloads alongside playback activity, without opening each downloader to check its progress.

Downloads

• See current download speed, progress, remaining time, processing jobs and the waiting queue. A compact indicator on Now Playing links to the full page.
• Add up to ten named clients from Settings. Monitor everything or select categories, tags or labels, depending on the client. The main speed follows those filters; when a Usenet client cannot provide a reliable split, its total is shown separately.
• Recent activity shows up to 20 matching results, including completed downloads, failed Usenet jobs and NZBGet postprocessing warnings. Seeding torrents do not count as active downloads, and completed does not mean imported into Jellyfin.
• Turn Downloads off in Settings to hide it and stop collection while keeping saved clients and recorded history. With no clients configured, Downloads stays out of the sidebar and Now Playing.

This first version is monitoring only. Pausing, resuming, retrying and other queue changes still happen in the downloader. The Docker app runs the collector automatically; no extra service is needed. Client management follows normal Settings permissions: owner/admin access with Jellydash login enabled, or access through your existing protection when login is disabled.

Connection interruptions keep the last known activity visible and clear live speed and remaining-time readings. Recent-history failures keep saved results without stopping live queue updates. History is bounded rather than loaded as a complete archive; see the Downloads guide for provider limits and filtering details.

The README now includes Downloads setup and a screenshot with sample activity. This release also includes clearer labels and helper text across the dashboard.

Updating

Saved clients and credentials use your existing Jellydash database. Downloads needs no separate encryption key, additional volume mapping or required environment variables. Credentials are stored unencrypted in the database and stay server-side. Keep database backups private.

No manual database import is needed. Update Compose installations as usual:

docker compose pull && docker compose up -d

For a pinned image, use ghcr.io/themartz90/jellydash:1.13.0.

On Unraid, use the normal container update. The existing appdata mapping is enough.

The initial v1.13.0 image was withdrawn and replaced before the release announcement to remove a separate credential-key requirement. If you tried that image and its key was lost when replacing the container, reenter the affected client's credential once. The corrected build stores new credentials directly in the database.

Further testing on different downloader versions and setups is welcome. If you report a problem, include the client version, expected behavior and what Jellydash showed. Leave credentials and private download details out of reports.