Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Sc
Self-host Screego
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A screen-sharing server built for showing code and terminals with low latency and high resolution. Someone creates a room, shares the link, and everyone in it can share their screen with the others over WebRTC. It has no chat, calling or recording, and it ships its own STUN and TURN server, so the same container handles connection setup and relaying. It is an addition to a call tool rather than a replacement for one.
Pick Screego when the only thing you need is to show your screen to other people at readable quality and low latency, for example code or a terminal during a review. Someone opens a room, shares its link and everyone in the room can share a screen with the others over WebRTC. It does one job: the README says it only helps to share your screen, so there is no chat, calling or recording. It is GPL-3.0 licensed and ships its own STUN and TURN server. Our snippet runs the `screego/server` image pinned to 1.12.6 (released 2026-09-27) with host networking, as the project's installation page recommends, and a relay port range of 50000 to 50200. We did not find an upstream RAM minimum, so our 128 MB floor is an estimate. In the catalog, Jitsi Meet, MiroTalk P2P and OpenMeetings are full meeting servers with audio, video and chat, and Nextcloud Talk lives inside Nextcloud; Screego is the small add-on you run next to a call tool when its screen sharing is too slow or too blurry.
What you need
Any VPS with at least 128 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Screego's installation, configuration and NAT traversal documentation flag these before you rely on it:
non-negotiableTLS is required. The docs say Screego will not work without it, either through SCREEGO_SERVER_TLS with a certificate and key or through a reverse proxy, and browsers only allow screen capture on HTTPS or localhost. Our snippet serves plain HTTP on port 5050, so the page opens at the server's address but sharing needs TLS in front.
non-negotiableSCREEGO_EXTERNAL_IP must be the server's public address, because Screego advertises it to peers. Our snippet reads it from api.ipify.org when you run it; if the address changes, use the dns: form that the example configuration describes.
non-negotiableOpen 5050 for the web interface, 3478 on TCP and UDP for STUN and TURN, and the relay range on UDP (50000 to 50200 in our snippet, set through SCREEGO_TURN_PORT_RANGE). The docs warn that running without network_mode: host may not work correctly (issue 226) and give a port-mapping alternative.
non-negotiableThe default SCREEGO_AUTH_MODE=turn requires a login to create a room that uses the TURN relay (people joining need none), and logins come from a users file of bcrypt hashes made with screego hash. Without a users file, rooms can only use direct or STUN connections, so peers behind strict firewalls will fail. Set SCREEGO_USERS_FILE before relying on it from behind strict firewalls.
non-negotiableThe TURN server relays video through your server for those users, so bandwidth and traffic costs land on your host. By default it denies peers on local addresses through SCREEGO_TURN_DENY_PEERS; leave that on if the server sits inside a private network.