English (United States)
English (United States) Bengali (Bangladesh) Actions
Video imports
Enable video import using youtube-dl (Youtube, Dailymotion...)
Enable video import using webtorrent (torrent file or magnet URI)
Enable signup and set a max users and upload limits
Assign <a target="_blank" rel="noopener noreferrer" href="">moderator/admin</a> roles
Manage abuse reports on videos, accounts or comments using a dedicated dashboard
Automatically block videos from untrusted users awaiting a review by moderators
Block specific videos and specify a reason
Ban local users, mute accounts or instances
Highly configurable
Easily set instance metadata: name, description, main categories...
Create your own homepage using markdown or HTML
Search and install PeerTube <a target="_blank" rel="noopener noreferrer" href="">plugins or themes</a>
Use external auth (LDAP, OpenID Connect...) using auth plugins
Choose default user settings (NSFW policy, comments/download/P2P enabled, etc)
Store videos in the server filesystem of in object storage
Broadcast a message to users using a banner
The <a target="_blank" rel="noopener noreferrer" href="">installation guide is here</a> (only in English).
If you need help, check the <a target="_blank" rel="noopener noreferrer" href="">help page</a>.
PeerTube should run happily on a virtual machine with 2 threads/vCPUs, at least 1 Gb of RAM and enough storage for videos. In terms of bandwidth, a lot will depend on which PeerTube instances you federate with and what your relation with them is (more about that below).
As a real life example, the PeerTube demonstration server runs on 2 vCores and 2GB of RAM. Average consumption is:
CPU: nginx ~ 2%, peertube ~ 10%, postgres ~ 1%, redis ~ 1%
RAM: nginx ~ 1MB, peertube ~ 150MB, postgres ~ 30MB, redis ~ 20MB
Network: ~200GB sent per month ( ~1.5TB sent per month)
Except for video transcoding, a PeerTube instance is not CPU bound. Neither Nginx, PeerTube itself, PostgreSQL nor Redis require a lot of computing power. If it were only for those, one could easily get by with just one thread/vCPU.
You will hugely benefit from at least a second thread though, because of transcoding. Transcoding is very cpu intensive. It serves two purposes on a PeerTube instance: it ensures all videos can be played optimally in the web interface, and it generates different resolutions for the same video. PeerTube support for offloading transcoding to other machines is <a target="_blank" rel="noopener noreferrer" href="">being discussed</a>, but not yet implemented.
1/2 GB of RAM should be plenty for a basic PeerTube instance, which usually takes at most 150 MB in RAM. The only reason you might want more would be if you colocate your Redis or PostgreSQL services on a non-SSD system.
There are two important angles to storage: disk space usage and sustained read speed. To make a rough estimate of your disk space usage requirements, you want to know the answer to three questions:


No matching activity found.
Browse all component changes


English (United States) Bengali (Bangladesh)
No related strings found in the glossary.

String information

Source string location
String age
2 months ago
Source string age
2 months ago
Translation file
src/locale/bn_BD/LC_MESSAGES/app.po, string 352