Migrate an application off the retired Mux Real-Time Video (Spaces) product to LiveKit
domain: docs.mux.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your integration is on the now-shut-down Mux Real-Time Video / Spaces / Studio / Web Broadcast SDK product line per Mux's changelog shutdown notice
Review Mux's "Migrate to LiveKit Web SDK" guide for the mapping between Spaces concepts (spaces, participants) and LiveKit equivalents (rooms, participants)
Provision a LiveKit Cloud or self-hosted deployment and generate LiveKit access tokens to replace Mux Spaces session tokens
Swap the client SDK from Mux's Web Broadcast SDK to the LiveKit client SDK, updating join/publish calls to LiveKit's API surface
If Mux offered a temporary compatibility adapter during your migration window, treat it as a stopgap only — plan to finish moving fully onto LiveKit's native SDK
Known gotchas
Mux's regular Live Streaming/On-Demand product (RTMP/HLS ingest, Mux Data, simulcast targets) is unaffected by this shutdown — don't confuse it with the retired real-time/WebRTC product
There is no way to keep using Mux Real-Time Video going forward; it's a hard retirement, not a deprecation with a long tail
Confirm the exact shutdown/cutoff date against Mux's current changelog before planning a timeline, since secondary sources vary
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?