← Directory

Tdarr Node

Tdarr Node is a distributed transcoding worker that processes media files to meet your defined codec, stream, and container requirements as part of the Tdarr…

  • Media Applications
  • Media Servers
  • Productivity
  • Tools & Utilities
Tdarr Node is a distributed transcoding worker that processes media files to meet your defined codec, stream, and container requirements as part of the Tdarr V2 system. It supports Windows, Linux (including ARM), and macOS, and is designed to work alongside applications like Sonarr and Radarr for automated transcode and remux management. Each library has its own transcode settings, filters, and schedule, with workers split into four types (Transcode CPU/GPU and Health Check CPU/GPU) managed by the scheduler or manually. A separate Tdarr server instance is required to configure and manage the nodes. For a desktop application with similar functionality, see HBBatchBeast.

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

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

No GitHub repository data collected yet.

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Point the node to your Tdarr server Set serverIP, serverPort, and nodeName to match the Tdarr server you want to join, and add apiKey if the server requires one. Without them, the node starts but has nowhere to report jobs, so your media won't be processed. source
  • Map media, cache, and user IDs Mount your movie folder to /media and a cache folder to /temp, and set PUID/PGID (the user and group IDs the container runs as) to match the files' owner. If the paths or IDs don't match, Tdarr may not find your videos or may fail to write processed files. source
  • If you host the server, open 8265 and 8266 If you are also running the Tdarr server container, publish 8265 for the web dashboard and 8266 for node connections. If those ports are blocked, you can't open the dashboard and remote nodes can't talk to the server. source

Fetched 16 days ago - each note links to its source

Alternatives (2)

  • FileFlows - FileFlows is a self-hosted media file processing tool that automates video and file workflows through a flexible, rule-based flow system.
  • Tdarr - Tdarr V2 is a distributed, self-hosted transcoding and remuxing system that automates media library management by enforcing your required c…

Checked 3 days ago - source: AlternativeTo

Common questions

How do I configure a Tdarr node container to connect to my Tdarr server?

Set serverIP, serverPort, and nodeName to match the Tdarr server you want to join, and add apiKey if the server requires one. Without these values, the node starts but has nowhere to report jobs.

What volumes and user IDs should I set for a Tdarr node container?

Mount your media folder to /media and a cache folder to /temp. Set PUID and PGID to match the owner of the files so Tdarr can find videos and write processed files.

Which ports do I need to expose if I run the Tdarr server in Docker?

Publish 8265 for the web dashboard and 8266 for node connections. If those ports are blocked, the dashboard is unreachable and remote nodes cannot talk to the server.

Can multiple Tdarr nodes cause the server to become overloaded?

A user reports that four nodes and shared Docker storage caused heavy host I/O, and pausing the nodes dropped activity to idle.

Answers sourced from docs.tdarr.io, www.redditmedia.com

Community

Collected 11 days ago - public community threads