Jitsi server size calculator
Estimate bridge video traffic and recording concurrency. Use the official baseline as a starting point, then load-test your workload before choosing a server.
Official baseline to evaluate
Recording
Modeled video upload + allowance
Modeled video data + allowance
Transcription planning
Planning estimate only. No participant guarantee or cloud bill is calculated. Audio, screen sharing and relay paths are not modeled.
The notes contain only the calculator inputs and estimates. They are generated on your device and are not sent to us.
How the estimate works
Modeled video upload = participants × min(room size minus one, stream limit) × camera share × assumed bitrate. The room size applies to every participant as a simplified scenario; model groups separately when room sizes vary. The selected 20% allowance is adjustable, not measured overhead. Audio, screen sharing and TURN require separate evaluation.
Two-person rooms are modeled through the bridge to budget for fallback. Successful P2P can reduce actual bridge traffic. Monthly video data uses the entered equivalent hours at this load, without a hidden utilization discount.
The Jitsi handbook suggests 8 GB RAM and four dedicated cores for a basic server. This is not a participant guarantee. Use one separate instance per concurrent recording, following Jibri guidance. Vosk memory depends on the model and concurrent work.
Sources checked 2026-10-13. Price compute, storage, data transfer and operating costs separately for your chosen provider.
Details: Jitsi server requirements and self-hosting cost.
Record actual measurements separately with the capacity validation worksheet (.csv). It starts blank: an estimate is not a completed load test.
Frequently asked questions
How accurate is this calculator?
It estimates video traffic from your inputs, with an explicit allowance. It does not predict participant capacity or a cloud bill. Audio, screen sharing and relay traffic need separate evaluation. Measure the actual workload before choosing production capacity.
Why does bandwidth matter more than CPU for Jitsi?
The videobridge forwards video without re-encoding it, so each extra viewer costs network capacity rather than processing. Recording is the exception, because Jibri encodes video on the CPU.
Want this server running today?
Deploy it in one click
A private Jitsi server in your own AWS account with SSL, your domain and optional recording, transcription and JWT. Free 15 minute trial.
Start free trialTalk to a Jitsi engineer
Setup, fixes, branding, recording, scaling. Tell us what is happening and we reply with a plan and a quote.
Get expert help