Requirements

Torsher runs as one Linux container, so any computer with Docker can run it: Linux, or Windows and macOS through Docker Desktop. The operating system decides what else works, such as GPU transcoding. This page tells you how well your setup will do.

What you'll learn

Whether your hardware is supported, how much disk you need, and which TVs and browsers work.

Support levels

Level	What it means	Platforms
Main target	Checked on reference hardware, fixed first	x86-64 Linux, including NAS on x86 (Unraid, TrueNAS SCALE, Synology and QNAP with Intel CPUs)
Best effort	Built and accepted in bug reports, without guarantees	arm64 Linux (Raspberry Pi 5, RK3588 boards), Docker Desktop on Windows and macOS: no GPU transcoding, hard links and the database on shared folders not checked yet
Not supported	No image	32-bit ARM, Synology models with Realtek ARM CPUs

The reference machines are an Intel N150 mini PC and a desktop with an NVIDIA RTX 3080. NAS systems are checked together with testers.

Server

• CPU: x86-64 or arm64. An Intel N100 or N150 mini PC is a good fit: it streams and serves files easily and has a GPU for transcoding.
• Memory: 4 GB or more.
• GPU (optional): Intel or AMD graphics through VAAPI, or an NVIDIA card through NVENC. Without one, the CPU transcodes and scales large video down. See Hardware transcoding.
• Docker: Docker Engine with the Compose plugin on Linux, or Docker Desktop on Windows and macOS. See Docker Compose.

On a Raspberry Pi 4 and similar boards, the CPU is too slow to transcode: files the TV plays directly work, the rest may not.

Disks

• The data volume holds the database, the watch cache and the library. Plan for the cache (it cleans itself up when it reaches the limit) plus everything you keep.
• Downloads and the library on one volume. Kept files are hard-linked from downloads into the library and take no extra space. On different volumes they are copied. See Docker Compose.
• Your existing media can stay where it is: Torsher reads those folders and never writes there.

Network

• One port for the web interface and the API, 8080 by default.
• The server needs internet access to TMDB, your indexers and torrent peers. If your provider spoofs DNS or blocks hosts, Torsher can use DNS over HTTPS and your own proxy. See Network.
• Opening a port for incoming peer connections is optional and improves download speed.

TVs and browsers

Client	Status
LG webOS app	Tested on LG C4 (2024). TVs from 2020 (webOS 5) and later are targeted, but not tested yet
Browser on a computer	Developed and checked in Chrome; other current browsers are expected to work. The server converts what a browser can't play
Browser on a TV	Works if the TV browser is recent enough
Android TV, Apple TV, phones	Planned. See Other devices