WebRTC enables real-time communication in browsers — including the audio capture that powers StreamTranslate's live captioning. Here's what it is and how it fits into the modern streaming stack.
Try StreamTranslate FreeWebRTC (Web Real-Time Communication) is an open standard developed by Google and the W3C that enables real-time audio, video, and data communication directly in web browsers and native applications without the need for plugins or third-party software. WebRTC powers video calls in Google Meet, Discord, Zoom (web client), and countless other real-time communication tools.
From a technical perspective, WebRTC handles peer-to-peer connection establishment (ICE/STUN/TURN), audio/video encoding and decoding (Opus, VP8/VP9, H.264), network adaptive bitrate, and packet loss concealment. The combination of these capabilities allows WebRTC sessions to maintain quality even on imperfect network connections.
WebRTC supports real-time communication, while HLS typically distributes segmented video. Actual latency depends on the implementation, buffering, and network; neither technology establishes a universal end-to-end delay for captions. WHIP provides a standardized way to ingest media using WebRTC.
StreamTranslate requires a configured audio input and an active caption session. Browser microphone capture uses permissions in Control, which must remain open. The OBS Browser Source displays caption output; loading it alone does not start audio capture.
Browser audio APIs can provide microphone input when permission is granted. Captured audio, recognition, translation, network travel, and output settings all contribute to caption delay. StreamTranslate does not guarantee a fixed transmission or caption latency.
The browser source approach also means StreamTranslate is completely agnostic to your streaming platform and RTMP configuration. Whether you stream to Twitch, YouTube, Kick, or all three simultaneously via multistreaming, the caption system works identically because it captures audio at the source rather than from the stream output.
Configure an audio capture method and start a caption session in Control. The OBS Browser Source displays the resulting caption text.
Configured audio is processed for recognition, and caption text is sent to the output. Connection quality and processing contribute variable delay.
Because audio is captured at the browser level rather than from RTMP output, StreamTranslate works identically regardless of where you stream to.
WebRTC is an open standard enabling real-time audio, video, and data communication in browsers without plugins. It powers video calls, live streaming, and real-time audio capture.
StreamTranslate uses configured audio capture and an active caption session. The OBS Browser Source displays caption output; it does not start microphone capture just by being loaded.
WebRTC achieves caption timing that varies with audio, language, and connection vs 10-30 seconds for standard HLS, making it ideal for interactive real-time streaming scenarios.
Twitch primarily uses HLS for standard streams. WebRTC is used by platforms like Discord and Zoom for ultra-low-latency interactive features.
Web Audio APIs and RTMP serve different roles. StreamTranslate needs a configured capture route and an active caption session; the OBS Browser Source displays the caption output. Choose and test the audio route that fits your setup.