Stream phone, tablet, laptop and USB camera video into a LiveKit room. This open-source project includes a browser publisher, a room viewer and Rust camera libraries. Maintained by Hebbian Robotics for robotics and other shared-video applications. This is an independent project, not an official LiveKit product.
| Task | Start here |
|---|---|
| Publish a browser camera | Browser camera |
| Watch published camera feeds | Room viewer |
| Publish a native USB camera | Native camera publisher |
| Read the latest image | Rust frame API |
| Record timestamped H.264 video | Rust recorder |
| Build browser invite links and QR codes | Rust invite API |
Before connecting, obtain a LiveKit server URL and a room-scoped participant token. See LiveKit's tokens and grants for token creation and permissions.
- Paste the URL and a camera-publishing token, or open an invite link.
- Allow camera access, then select Start streaming.
- Keep the page visible and the device unlocked while streaming.
The publisher sends video only, targeting 720p at 15 fps without simulcast. Orientation, flip, lens and zoom controls change the published image. Device support varies. Camera capture requires a secure origin; see MDN's getUserMedia security requirements.
Install Node.js 24 and pnpm, then run pnpm install --frozen-lockfile.
On a trusted computer or backend, set:
export LIVEKIT_URL='wss://your-project.livekit.cloud'
export LIVEKIT_API_KEY='your-api-key'
export LIVEKIT_API_SECRET='your-api-secret'
export LIVEKIT_ROOM='your-room'
export CAMERA_IDENTITY='phone-table'
pnpm inviteThe example prints a one-hour publishing link and
writes invite.svg. API secrets remain on the issuing computer. Use a unique
participant identity for each camera.
Treat invite links and QR codes as secrets. Anyone holding one can use its room token. Only use a hosted page you trust, or host your own copy. See the browser integration reference for the URL contract, token handling and recording indicator.
Select Room viewer and provide a URL and subscribe-enabled token. It watches existing tracks, including cameras that join later, without opening a camera or playing audio. Switching between Stream and Room viewer keeps an active browser publication running. A publishing invite cannot subscribe to the room.
With the same server credentials and room configured above, run:
pnpm viewer-inviteThis creates a one-hour subscribe-only link. VIEWER_IDENTITY is optional; the
example otherwise generates one. Keep the link private. The viewer is a LiveKit
participant and consumes room resources. See LiveKit's
track subscription documentation
for the underlying model.
The Rust publisher accepts a pre-issued camera-publishing token:
export LIVEKIT_URL='wss://your-project.livekit.cloud'
export LIVEKIT_TOKEN='<camera-publishing-token>'
cargo run --release -p livekit-camera-publisher -- --name front --device /dev/video0
cargo run -p cameras -- listIt publishes the newest frame at up to 15 fps, without simulcast. Persistent device identifiers reconnect; numeric indices stop on failure to avoid selecting a different camera. Capture runs in a subprocess so blocked reads can be stopped. See native publisher integration before embedding it.
For the upstream SDK and examples, see LiveKit's Rust SDK. Build prerequisites and platform checks are in Contributing.
pnpm install --frozen-lockfile
pnpm dev
pnpm buildDeploy dist/ to a static HTTPS host. GitHub Actions validates changes and deploys
main to GitHub Pages; forks must select GitHub Actions as the Pages source.
Deployment needs no LiveKit credentials. For another public URL, update the
canonical and social-preview URLs in index.html. The preview image source is
public/social-preview.svg; its PNG copy is used for sharing.
See Contributing for validation and documentation style.
MCAP Tools writes MCAP recordings and exports camera topics to MP4 from Rust/Python applications.
MIT license. See security reporting and the hosted third-party notices. Native dependencies and system libraries retain their own licenses.