Media transport adapters connect WebRTC tracks to services that exchange media over another transport. The WebSocket adapter supports audio ingest, audio egress, and video egress as JPEG frames.
An external service can process or generate audio without implementing a WebRTC peer. Your backend creates the adapter and manages its lifetime.
The WebSocket adapter is in beta. Choose the path your external service needs; each adapter handles one direction:
| Your service | Direction | Media |
|---|---|---|
| Generates audio | WebSocket → SFU → WebRTC | PCM audio published as a WebRTC audio track |
| Transcribes or processes audio | WebRTC → SFU → WebSocket | Audio delivered as PCM |
| Inspects frames or generates previews | WebRTC → SFU → WebSocket | Video delivered as JPEG frames |
Use separate adapter instances for bidirectional audio. Video ingest over the WebSocket adapter is not supported.
Use the WebSocket adapter
The AI audio guide shows speech generation and transcription through separate adapter paths. For video, the WebRTC-to-JPEG example ↗︎ receives frames in a Durable Object and distributes them to viewers.
Both examples are experimental and require application authentication and authorization before public use. Their repository guides describe setup and integration limitations.