👋 Welcome to the Link Help Center
Find the answers you need—fast and easy
Server Configuration Recommendations
1. Estimation Assumptions
The following recommendations are estimated under these conditions:
• LiveKit runs on a single server in pure SFU forwarding mode.
• One concurrent 1:1 call means two users online in the same room.
• Egress recording, transcoding, compositing, and live streaming are disabled.
• Approximately 40% production headroom is reserved for CPU and memory.
• Approximately 30%-50% headroom is reserved for network bandwidth.
• Bandwidth values in the tables are sustained available throughput, not an instantaneous peak advertised by a cloud provider or the theoretical line rate of a NIC.
2. Video Call Sizing Recommendations
| Concurrent 1:1 calls | Concurrent users | Recommended CPU | Recommended memory | Recommended inbound bandwidth | Recommended outbound bandwidth | Recommended NIC |
|---|---|---|---|---|---|---|
| 1 call | 2 users | 2 cores | 4 GB | 10 Mbps | 5 Mbps | 1 Gbps |
| 10 calls | 20 users | 4 cores | 8 GB | 75 Mbps | 30 Mbps | 1 Gbps |
| 50 calls | 100 users | 8 cores | 16 GB | 370 Mbps | 130 Mbps | Dedicated 1 Gbps |
| 100 calls (estimated) | 200 users | 16 cores | 32 GB | 750 Mbps | 260 Mbps | 2.5 Gbps |
The original estimate for 50 concurrent video calls is inbound 246 Mbps and outbound 85 Mbps. The table rounds these values with close to 50% headroom. The 100-call figures are linear estimates based on the same model and are intended only for capacity planning; they do not replace load testing.
3. Audio Call Sizing Recommendations
| Concurrent 1:1 calls | Concurrent users | Recommended CPU | Recommended memory | Recommended inbound bandwidth | Recommended outbound bandwidth | Recommended NIC |
|---|---|---|---|---|---|---|
| 1 call | 2 users | 2 cores | 4 GB | 1 Mbps | 1 Mbps | 1 Gbps |
| 100 calls | 200 users | 4 cores | 8 GB | 10 Mbps | 10 Mbps | 1 Gbps |
| 500 calls (estimated) | 1,000 users | 8 cores | 16 GB | 40 Mbps | 40 Mbps | 1 Gbps |
| 1,000 calls | 2,000 users | 16 cores | 32 GB | 80 Mbps | 80 Mbps | Dedicated 1 Gbps |
Audio uses relatively little bandwidth, but at high concurrency the number of WebRTC connections, UDP packet-processing rate, file descriptors, and operating-system network buffers become the main bottlenecks. Therefore, do not size a low-spec server for 1,000 concurrent audio calls based on bandwidth alone.
4. Recommended Production Specification
For a workload that must support either 50 concurrent video calls or 1,000 concurrent audio-only calls, start with the following specification:
| Resource | Recommended specification |
|---|---|
| CPU | 16 cores, at least 3.0 GHz, with high-clock physical cores preferred |
| Memory | 32 GB |
| System disk | 100 GB or larger SSD |
| Network interface | Dedicated 1 Gbps full-duplex NIC |
| Public video bandwidth | At least 370 Mbps inbound and 130 Mbps outbound |
| Public audio-only bandwidth | At least 80 Mbps in each direction |
| Public address | Static public IP address with UDP support |
During production operation, keep sustained CPU usage below 60% and memory usage below 70%. Scale up or move to a multi-node deployment when CPU, packet loss, RTT, or outbound bandwidth remains close to its threshold.
If LiveKit Egress is used on the same server for recording, transcoding, or compositing, the specification above no longer applies. Egress is compute-intensive and should preferably be deployed separately, with CPU, GPU, memory, disk, and outbound bandwidth reassessed.