← SelfhostSpecs

Jitsi Meet — system requirements

Self-hosted, fully encrypted video conferencing platform, deployable as a multi-container Docker stack. · website · repository

Minimum RAM
2 GB
“for test servers or very small meetings you can try to use 2 GB”
Scope: Jitsi Handbook DevOps guide, Requirements page, test-server/very-small-meeting tier (lowest of the three RAM bands the page gives) · official source · retrieved 2026-09-02
Recommended RAM
8 GB
“it's usually suggested to get 8 GB”
Scope: Jitsi Handbook DevOps guide, Requirements page, general/basic-server suggestion (the page also lists an intermediate "4 GB for small meetings" tier, not captured by this min/rec schema) · official source · retrieved 2026-09-02
Recommended CPU cores
4 cores
“For a basic server, 4 dedicated cores can be enough.”
Scope: Jitsi Handbook DevOps guide, Requirements page, basic-server tier · official source · retrieved 2026-09-02
No official figure published for: minimum CPU cores
Live re-fetch surprise vs. earlier research notes: the current Requirements page states no minimum core count for the test/small-meeting tier. It only says Prosody (one stack component) "can only use ONE (1) core" -- a per-process ceiling, not a stated system minimum -- so filing that as cpu_min_cores would misattribute a different claim (Defect Class #1/#8). Only the basic-server figure ("4 dedicated cores", filed as cpu_rec_cores) is an actual core-count requirement in this source.
We publish nothing we can't source. Evidence of the gap.

External services

Official docker-compose.yml defines web, prosody (bundled internal XMPP server), jicofo, and jvb containers -- no external database service of any kind.

Container

Image: ghcr.io/jitsi/web:stable · compressed size (amd64): 129 MB · architectures: amd64, arm64 · source, retrieved 2026-09-02

Jitsi Meet ships as a 4-container stack (web, prosody, jicofo, jvb) with no single container named "jitsi-meet"; web (the user-facing frontend, and the compose file's first-listed service) is shown here as representative, consistent with the project's core-identity convention for bundled apps (see Mailcow), but this size covers only that one container, not prosody/jicofo/jvb. This image has no :latest tag on the registry -- the officially documented rolling-release tag is :stable (README: "`stable` | Points to the latest stable release"), confirmed live to resolve; ghcr.io/jitsi/web:latest returns 404 (manifest unknown) on live registry lookup. Jibri, the separate optional recording component, ships its own image and its own 8-12GB RAM figure in the Handbook, not reflected in this entry's specs (do not conflate).

Related apps