FFmpeg video transcoding is CPU-intensive and can dominate the host.
Instances accepting many uploads or many output resolutions.PeerTube 하드웨어 요구 사항: RAM, CPU, 트랜스코딩 및 스토리지
RAM, CPU, 동영상 트랜스코딩, PostgreSQL, Redis, 스토리지 및 대역폭을 고려한 PeerTube 하드웨어 계획과 실용적인 ZimaOS 사양 가이드.
PeerTube requirements at a glance
PeerTube itself is not very CPU-heavy outside transcoding; video encoding, storage and network delivery are the real sizing variables.
- Large-instance reference
- Official recommendation for about 1,000 concurrent viewers: 4 vCores, 4 GB RAM and 1 Gbit/s upload, plus sufficient video storage and bandwidth.
- Same-host transcoding
- Official guidance: 8 vCores and 8 GB RAM when transcoding runs on the same machine.
- Dependencies
- Current supported dependencies include PostgreSQL 14+, Redis 6.2+, Node LTS 22.12–<25 and FFmpeg 4.3+.
- Storage
- No fixed disk minimum; original videos, transcoded renditions, thumbnails and backups determine capacity.
- Network
- PeerTube warns against production hosting behind low-bandwidth links; upload capacity and transfer bandwidth are fundamental.
- Best Zima starting point
- ZimaCube 2 Pro is the better all-in-one choice when local transcoding is required; ZimaBoard 2 can suit smaller/light instances with limited transcoding.
From official requirements to the right setup
Size PeerTube around video delivery and transcoding rather than the web application alone.
-
Official requirements
Estimate concurrent viewers, video bitrate and upload bandwidth. A large-instance official reference uses 4 vCores, 4 GB RAM and 1 Gbit/s upload for about 1,000 viewers.
-
Confirm your needs
Decide where transcoding happens. If the same machine performs transcoding, PeerTube recommends 8 vCores and 8 GB RAM.
-
Leave room to grow
Plan storage for source videos plus every generated rendition, thumbnails and backups; media capacity normally dominates disk use.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with PeerTube's official production Compose files, persist PostgreSQL/Redis/video data, and map web/TLS ports carefully.
Check every playback client
- Concurrent viewers
- Upload bandwidth
- Video bitrate
- Transcoding on host
- PostgreSQL 14+
- Redis 6.2+
- Video library size
- Backup retention
Official minimum requirements
PeerTube publishes workload-based hardware references rather than one universal minimum.
The 4-vCore/4-GB/1-Gbit profile is a large-instance reference for about 1,000 viewers; the 8-vCore/8-GB figure specifically applies when transcoding runs on the same machine.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Large-instance CPU | 4 vCores | Reference for about 1,000 concurrent viewers. |
| Large-instance RAM | 4 GB | Reference for about 1,000 concurrent viewers. |
| Large-instance upload | 1 Gbit/s | Reference for about 1,000 concurrent viewers. |
| Same-host transcoding CPU | 8 vCores | Official recommendation. |
| Same-host transcoding RAM | 8 GB | Official recommendation. |
| Database/cache | PostgreSQL 14+ and Redis 6.2+ | Current dependency guidance. |
| Disk | Enough storage for videos | No universal numerical disk minimum. |
When to upgrade your hardware
PeerTube should scale when transcoding, bandwidth or video storage becomes the bottleneck.
Transcoding queues build up
Concurrent viewers approach network limits
Video renditions fill storage
Outbound bandwidth can become the primary constraint even when CPU is idle.
Public video communities.Source media plus multiple transcoded versions can consume storage rapidly.
Large or high-bitrate libraries.Plan hardware growth with confidence
Scale PeerTube around transcoding CPU, outbound bandwidth and multi-drive video storage.
Use ZimaBoard only for smaller/light instances
The N150 can run PeerTube services but is not a good match for heavy same-host transcoding.
ZimaBoard 2 1664 for smaller deployments with limited transcoding.Use stronger CPU for local transcoding
PeerTube's same-host guidance calls for 8 vCores and 8 GB RAM.
ZimaCube 2 Pro's 10-core/12-thread CPU aligns much better with that profile.Use multi-drive storage for video libraries
Originals and multiple renditions dominate disk capacity.
ZimaCube 2 Standard or Pro.Plan networking before adding compute
Public PeerTube delivery may become bandwidth-bound before CPU-bound.
ZimaCube 2 Pro adds 10GbE for fast local storage/network paths, though internet upload remains the external limit.Can it run on ZimaOS?
No public official ZimaOS one-click PeerTube App Store page was verified for this guide. PeerTube can be deployed through Install Custom App using its official production Docker Compose files.
Custom install PeerTube in ZimaOS
Use Install Custom App with PeerTube's official production Compose files, persist PostgreSQL, Redis and video data, and configure a permanent domain plus TLS.
Custom install PeerTube in the ZimaOS app ↗Use PeerTube's official production Compose
The current Docker guide requires Docker Compose v2 and provides production Compose and environment files.
Review PeerTube Docker installation ↗Match current PeerTube dependencies
Current dependency guidance lists PostgreSQL 14+, Redis 6.2+ and FFmpeg 4.3+ among the core requirements.
Review PeerTube dependencies ↗Choose Zima hardware for PeerTube
PeerTube is a media-delivery workload; CPU for transcoding and storage/network capacity matter more than baseline web-app memory.
Is this a small instance with light transcoding or an all-in-one transcoding/video server?
Small/light instance
Use ZimaBoard 2 with enough external video storage; keep transcoding limited.
- Compact choiceZimaBoard 2 1664
Same-host transcoding and larger library
Use stronger CPU, more storage and faster network interfaces.
- Best all-in-one choiceZimaCube 2 Pro
- Storage-first optionZimaCube 2 Standard
These are practical mappings to published workload references, not guaranteed viewer or transcoding throughput.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Small PeerTube instances with limited transcoding. | PeerTube, PostgreSQL, Redis and modest media delivery. |
|
The 4-core N150 does not match PeerTube's 8-vCore same-host transcoding recommendation. | Get Now |
| ZimaCube 2 Pro | PeerTube with same-host transcoding. | 10-core/12-thread CPU, 16 GB RAM, multi-drive video storage and faster networking. |
|
Internet upload and FFmpeg workload still determine real viewer/transcoding capacity. | Get Now |
| ZimaCube 2 Standard | Large video storage with lighter transcoding. | Multi-drive video retention and backups. |
|
8 GB RAM meets the same-host memory reference, but CPU is less suitable than Pro for heavy transcoding. | 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
These answers cover PeerTube RAM, CPU, transcoding, storage, bandwidth and ZimaOS deployment.
How much RAM does PeerTube need?
PeerTube gives workload-based references: 4 GB RAM for a large roughly 1,000-viewer instance, and 8 GB when transcoding on the same machine.
How many CPU cores does PeerTube need?
The large-instance reference uses 4 vCores, while same-host transcoding is recommended with 8 vCores.
How much bandwidth does PeerTube need?
A large-instance reference uses 1 Gbit/s upload for about 1,000 concurrent viewers, and PeerTube warns against low-bandwidth production links.
Which database does PeerTube use?
Current dependency guidance requires PostgreSQL 14 or newer and Redis 6.2 or newer.
How much storage does PeerTube need?
There is no universal disk minimum; source videos, transcoded renditions, thumbnails and backups determine capacity.
Does PeerTube need a GPU?
A dedicated GPU is not part of the published baseline; the official guidance centers on CPU-based transcoding capacity.
Can ZimaBoard 2 run PeerTube?
Yes for a smaller instance, but heavy same-host transcoding can overwhelm the 4-core N150.
When should I choose ZimaCube 2 Pro?
When PeerTube performs local transcoding, stores a larger library or needs stronger CPU and network headroom.
What sources informed this PeerTube hardware guide?
Current PeerTube hardware, Docker and dependency documentation plus current Zima product pages.
