# Questions about screen sharing on the network

**URL:** <https://community.livekit.io/t/questions-about-screen-sharing-on-the-network/986>\
**Category:** Self Hosting\
**Created:** [April 29, 2026, 1:39pm UTC](https://community.livekit.io/t/questions-about-screen-sharing-on-the-network/986 "2026-04-29T13:39:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![getdd6](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@getdd6](https://community.livekit.io/u/getdd6)\
**Post date:** [April 29, 2026, 1:39pm UTC](https://community.livekit.io/t/questions-about-screen-sharing-on-the-network/986/1 "2026-04-29T13:39:09Z")

</div>

Regarding the issue of screen sharing self-hosting, my current room has 130 people and the bandwidth is too high (around 400Mbps). Using the official service causes lag and stuttering in China. Are there any solutions? How should I choose a server?

---

<div class="post-metadata">

**Author:** ![Raghu\_Udiyar](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/raghu_udiyar/32/334_2.png) [@Raghu\_Udiyar](https://community.livekit.io/u/Raghu_Udiyar)\
**Post date:** [May 11, 2026, 8:54am UTC](https://community.livekit.io/t/questions-about-screen-sharing-on-the-network/986/2 "2026-05-11T08:54:36Z")

</div>

When self-hosting single room scalability is limited to a single server, because livekit OSS doesn’t support multi-homed rooms. Is there a reason for all participants to actively participate in the room? Or are there passive observers as well? If yes, webrtc might not be needed for all of them.

---

<div class="post-metadata">

**Author:** ![Muhammad\_Usman\_Bashir](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/muhammad_usman_bashir/32/1149_2.png) [@Muhammad\_Usman\_Bashir](https://community.livekit.io/u/Muhammad_Usman_Bashir)\
**Post date:** [May 11, 2026, 9:45pm UTC](https://community.livekit.io/t/questions-about-screen-sharing-on-the-network/986/3 "2026-05-11T21:45:08Z")

</div>

@Raghu_Udiyar’s framing is right. `1-to-130` broadcast over raw WebRTC is wasteful regardless of server. Math: `130 × ~3 Mbps screen share = ~400 Mbps`, the SFU fanning out one track `130 times`.

Two paths:

- Mostly passive viewers. Egress with `segment_outputs` to `HLS`, stored on `S3` or `aliOSS` (Alibaba OSS is a built-in egress destination), served via a Chinese CDN. SFU bandwidth drops to the presenter’s single track plus the egress transcoder. Latency `~5` to `10s`; fine for passive viewing.
- Everyone active. A self-hosted OSS room is bound to one node. Redis-distributed mode spreads rooms across nodes, not one room. That’s Cloud Scale-tier or commercial-mesh territory. Also trim publisher resolution and fps; simulcast on screen share is typically single-layer.

China side: host the SFU on Alibaba or Tencent cloud near your users. Global Cloud edges fight the Great Firewall on cross-border WebRTC.

> **[Output & streaming options | LiveKit Documentation](https://docs.livekit.io/transport/media/ingress-egress/egress/outputs/)**
>
> Export content anywhere, in any format.

---

<div class="post-metadata">

**Author:** ![getdd6](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@getdd6](https://community.livekit.io/u/getdd6)\
**Post date:** [May 12, 2026, 9:25am UTC](https://community.livekit.io/t/questions-about-screen-sharing-on-the-network/986/4 "2026-05-12T09:25:38Z")

</div>

However, LiveKit does not support SFU and can only use their cloud service.