“In the browser” does not mean “without a host”
The browser replaces the client application, not the host software. Helio runs on the Windows gaming PC, while the web client authenticates, negotiates media and sends controls back.
- Install HelioPair the gaming PC with Lume.
- Open LumeUse a compatible browser on the second device.
- Connect inputPair a controller or use keyboard and mouse where browser support permits.
The useful codec is the one both endpoints can accelerate
Lume can negotiate AV1, HEVC or H.264 depending on the host GPU, OS and browser. AV1 is efficient but hardware support is not universal. H.264 provides a broader fallback. One AMD-to-Chrome test sustained AV1 1440p60 at an 11.31 Mbps median; read the full test conditions.
Desktop Chrome is currently the best-documented web path
Media and input APIs differ across browsers. Keep the browser current, test the controller first and consult the compatibility matrix. Safari PWA coverage is still expanding.
A browser client does not make the stream public
Media travels over encrypted WebRTC transport. Lume seeks a direct route and can use TURN when network conditions require it. See Security and architecture for the data flow.
When a native client is a better fit
Choose native clients when you need deeper system integration or uncommon peripherals. Choose the web path for immediate access. Both remain active Lume workstreams.