Each active channel carries its own stream bitrate unless the chosen proxy/downstream behavior reuses a stream. The aggregate network path must sustain the intended tuner count.
Multi-user Live TV households.Hårdvarukrav för Threadfin: RAM, CPU, IPTV-strömmar och nätverk
Lär dig mer om Threadfins krav på CPU, RAM, tuner, IPTV-ström, FFmpeg-buffert och nätverk, och välj sedan lämplig ZimaOS-maskinvara.
Threadfin requirements at a glance
Threadfin does not publish a numerical CPU or RAM minimum. It is an M3U/XMLTV proxy and channel manager for Plex, Emby and Jellyfin, based on xTeVe. Direct stream proxying is lightweight; simultaneous IPTV streams, RAM/FFmpeg/VLC buffering, EPG work and the downstream media server determine the real hardware requirement.
- CPU
- No numerical official minimum. Playlist/EPG management and direct proxying are light; FFmpeg/VLC buffering or remuxing adds CPU work.
- RAM
- No numerical official minimum. Threadfin includes buffering/re-streaming behavior and stream concurrency, so practical memory depends on active streams and chosen buffer path.
- Network
- Bandwidth scales with the number and bitrate of simultaneous upstream/downstream IPTV streams. Network throughput is often more important than application CPU.
- Tuners
- Threadfin lets administrators configure the number of tuners, which effectively defines how many simultaneous channel streams the downstream media server can request.
- Port
- The current official Docker example exposes port 34400.
- Best Zima starting point
- ZimaBoard 2 832 is ample for typical Threadfin proxy/EPG use. ZimaCube tiers make sense when Threadfin shares a larger Plex/Jellyfin storage/transcoding server.
From official requirements to the right setup
Threadfin sizing starts from simultaneous channel streams and whether Threadfin is simply proxying or adding a buffer/remux layer.
-
Official requirements
Count simultaneous tuners/streams and their typical bitrate. IPTV traffic scales with active channels rather than the size of the channel list.
-
Confirm your needs
Choose direct streaming versus an FFmpeg/VLC-assisted buffer path. Direct proxying is much lighter; third-party buffer/remux processes add CPU, memory and temporary I/O.
-
Leave room to grow
Size the downstream Plex/Emby/Jellyfin server separately. If it transcodes Live TV, that CPU/GPU workload belongs to the media server rather than Threadfin.
-
Run it on ZimaOS
Install Threadfin from ZimaOS, test representative channels at the intended tuner count and monitor network throughput, FFmpeg CPU and buffering before increasing hardware.
Check every playback client
- IPTV provider connection/tuner limit
- Concurrent active channels
- Stream bitrate
- Direct versus FFmpeg/VLC buffer mode
- EPG/XMLTV size
- Plex/Emby/Jellyfin Live TV server
- Downstream transcoding
- LAN/WAN throughput
Official minimum requirements
Threadfin's current repository lists compatible Plex/Emby/Jellyfin versions but does not publish host CPU/RAM minimums.
Do not infer a Threadfin hardware minimum from the downstream media server. Threadfin's own control/proxy workload and Plex/Jellyfin transcoding are separate.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | Direct proxying is light; FFmpeg/VLC processing can add CPU demand. |
| RAM | No numerical minimum published | Active streams/buffering determine practical usage. |
| Docker port | 34400 | Current official Compose example. |
| Build requirement | Go 1.18+ | Only relevant when building Threadfin from source. |
| Compatible Live TV servers | Plex / Emby / Jellyfin | Current repository documents minimum compatible server versions. |
| GPU | Not required by Threadfin | Any Live TV transcode GPU requirement belongs to Plex/Emby/Jellyfin. |
When to upgrade your hardware
Upgrade when simultaneous stream traffic or buffer/remux work proves the current host insufficient.
More simultaneous IPTV channels increase network load
FFmpeg or VLC buffering consumes noticeable CPU
Threadfin shares a host with Plex/Jellyfin transcoding
Threadfin's repository notes third-party FFmpeg/VLC as the better buffer solution after removing the older Threadfin buffer option. That extra process can become the compute-heavy layer.
Users stabilizing or remuxing IPTV streams.The media server can consume far more CPU/GPU than Threadfin when clients need Live TV transcoding.
All-in-one IPTV/media servers.Plan hardware growth with confidence
Scale Threadfin by optimizing the stream path before adding arbitrary RAM.
Prefer direct streaming when it works reliably
Community Threadfin/Plex users often troubleshoot by removing FFmpeg/VLC buffering when the upstream stream is already compatible.
This removes a CPU/process layer and can reduce latency.Use FFmpeg/VLC only when compatibility or buffering requires it
Third-party processing can stabilize or reshape streams but adds CPU and I/O overhead.
Benchmark the exact IPTV codec/container rather than assuming a fixed CPU requirement.Keep EPG/config data persistent
Threadfin merges and refreshes M3U/XMLTV data; persistent config is small but essential for channel maps and schedules.
Local appdata storage is sufficient for normal deployments.Size the media server separately for transcoding
Plex, Emby or Jellyfin may transcode Live TV after Threadfin hands off the stream.
Use the appropriate media-server hardware guide for CPU/iGPU/GPU sizing.Can it run on ZimaOS?
Threadfin is currently available in the ZimaOS App Store under Media.
Install Threadfin from ZimaOS
Use the packaged M3U proxy and Live TV tuner bridge for Plex, Emby or Jellyfin.
Open Threadfin in the ZimaOS App StoreUse the current upstream Docker layout
Threadfin's current repository documents port 34400 and persistent conf/temp paths in its Compose example.
Read Threadfin Docker setupTreat downstream transcoding as a separate workload
Threadfin manages/proxies IPTV while Plex, Emby or Jellyfin may perform client-specific decoding/transcoding.
Read Threadfin compatibility requirementsChoose Zima hardware for Threadfin
Threadfin's core proxy workload is modest. Choose larger Zima hardware for simultaneous IPTV processing and the media server around it.
Is Threadfin a lightweight IPTV proxy or part of a full media/transcoding server?
Direct IPTV proxy/EPG for a few household streams
ZimaBoard 2 832 provides ample compute and dual 2.5GbE.
- Normal Threadfin hostZimaBoard 2 832
- More network/media servicesZimaBoard 2 1664
All-in-one Live TV/media-storage server
Use ZimaCube when Plex/Jellyfin storage and transcoding—not Threadfin alone—drive the requirement.
- Integrated Live TV/media serverZimaCube 2 Standard
- Larger media/10GbE platformZimaCube 2 Pro
No fixed stream-count or bitrate guarantee is implied. IPTV provider limits, codec/container, FFmpeg options, tuner count, media-server behavior and network quality all matter.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A normal Threadfin IPTV proxy and EPG server. | M3U/XMLTV management and several direct household streams. |
|
Heavy FFmpeg processing or downstream transcoding must be sized separately. | Get Now |
| ZimaBoard 2 1664 | Threadfin plus more networking/media containers. | More simultaneous services and buffer/remux headroom. |
|
Provider connection limits and stream quality are not solved by more RAM. | Get Now |
| ZimaCube 2 Standard | An all-in-one Threadfin plus Plex/Jellyfin media server. | Live TV proxying, media storage and wider home-media services. |
|
Choose it for media/storage integration rather than Threadfin compute. | Get Now |
| ZimaCube 2 Pro | A larger Live TV/media-storage platform. | More media services, stronger CPU and 10GbE-capable storage/network workflows. |
|
IPTV source quality/provider limits can remain the bottleneck. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
FAQ topics follow query fan-out around RAM, tuner count, direct streaming, FFmpeg buffering, Plex/Jellyfin transcoding and network bandwidth.
How much RAM does Threadfin need?
Threadfin does not publish a host RAM minimum. Direct M3U/EPG proxying is lightweight; active buffering and the wider media stack determine practical memory use.
Does Threadfin transcode IPTV streams?
Threadfin is primarily a proxy/channel manager. FFmpeg or VLC can be used as external buffer/remux tools, while Plex/Emby/Jellyfin may perform downstream client transcoding.
How many streams can Threadfin handle?
There is no official fixed number. Threadfin exposes an adjustable tuner count, while provider connection limits, stream bitrate, network capacity and buffer mode determine the practical ceiling.
Why does IPTV work better when I disable the Threadfin/FFmpeg buffer?
Some community users find compatible MPEG-TS/HLS streams work more reliably when sent directly to Plex/Emby/Jellyfin, avoiding an extra FFmpeg/VLC processing layer.
Does Threadfin need a GPU?
No. Any GPU requirement usually belongs to the downstream Plex/Jellyfin/Emby server if it transcodes Live TV.
Can ZimaBoard 2 832 run Threadfin?
Yes. Its N150, 8 GB RAM and dual 2.5GbE provide substantial headroom for typical Threadfin proxy/EPG workloads.
What determines Threadfin network requirements?
The aggregate bitrate of active IPTV streams, how they are proxied/restreamed and the downstream clients/media server.
When is ZimaCube 2 useful for Threadfin?
When Threadfin is part of an all-in-one Plex/Jellyfin media server requiring multi-drive storage, more media processing or a larger network platform.
What sources and further reading informed this Threadfin hardware guide?
The current Threadfin repository defines its proxy role, adjustable tuners, buffer/restream behavior, Docker port and compatible media servers. ZimaOS confirms the Media app, while Plex/Emby community discussions were used for real buffer/direct-stream query fan-out.
