Viewing Camera Streams with a WebRTC Camera Card

The Short Answer

A WebRTC camera card is a dashboard element that plays a live camera feed in a web browser using WebRTC, the browser's built-in technology for real-time audio and video. The phrase most commonly refers to a community-made custom card for Home Assistant dashboards. That card uses a separate streaming service to convert the camera's own stream, often RTSP from an IP camera, into a format the browser can play with little delay. Whether you can hear speech, or talk back through the camera, depends on three conditions: the audio format the camera sends, whether the streaming service can convert that audio for the browser, and whether the camera supports two-way audio. The card displays what it receives. It does not improve the microphone on the camera.

What the Card Does

Most IP cameras publish their video as an RTSP stream. RTSP is a network streaming protocol that web browsers cannot play directly. A WebRTC camera card relies on an intermediary service that pulls the RTSP stream, repackages it, and delivers it to the browser over WebRTC. In the Home Assistant setup, that intermediary is typically go2rtc, an open-source streaming server. The card is the visible player on your dashboard, and the server does the routing and conversion behind it.

How It Differs from a Standard Camera View

Standard dashboard camera views often use periodic snapshots, MJPEG, or HLS. HLS delivers video in short downloaded segments, which by design adds delay. WebRTC was built for live conversation, so it generally plays with noticeably lower latency. Lower latency matters for speech. If you want to hear someone at a door and answer them, a delay of several seconds makes the exchange awkward. WebRTC is designed to keep that delay short, but the actual delay depends on your network, the camera, and any conversion being done. No measured figures were available for this guide.

What This Means for Hearing and Capturing Speech

• Audio codec compatibility: Browsers playing WebRTC commonly support the Opus and G.711 (PCMA/PCMU) audio codecs. A codec is the method used to compress the audio. Many cameras send AAC audio instead, which WebRTC in browsers does not play. If your camera uses AAC, the streaming server must transcode it, meaning convert it to a supported codec, often with FFmpeg. Without that step, you may get video with no sound.
• Autoplay muting: Browsers usually block audio from playing automatically until you interact with the page. A silent stream on first load does not necessarily mean the audio path is broken. Try unmuting or clicking on the player first.
• Talking back through the camera: Two-way audio works only if the camera has a speaker and exposes a supported backchannel, and if the streaming server supports that camera model. Some card configurations add a microphone option for this. Check the current documentation for your camera and card version, because support varies.
• Microphone permission: Browsers allow microphone access only on secure (HTTPS) pages or on localhost. If you open your dashboard over plain HTTP, the browser will refuse the talk-back microphone.
• Voice quality: The clarity of speech you hear is limited by the camera's built-in microphone, its placement, and the codec in use. G.711 is a narrowband telephone-grade codec, so speech will sound more like a phone call than a recording. The card cannot add detail that the source did not capture.

Routing a Webcam as a Camera Source

If your goal is to turn a USB webcam into a network camera you can view this way, the streaming server can capture a local video device and its microphone, typically through FFmpeg, and publish them as a stream for the card. Doing this well for speech takes a few checks. Confirm that the correct audio input is selected on the host computer, since webcams often appear as a separate microphone device alongside others. Confirm that the audio is encoded in a codec the browser can play. Test with someone speaking at a normal distance from the camera. The exact setup options depend on the server version and operating system, and no verified configuration details were available for this guide.

Evidence Gaps

No confirmed specifications, latency measurements, compatibility lists, or test results were available for any particular WebRTC camera card, streaming server version, or camera model. Everything above comes from documented general behavior of WebRTC, browsers, and common camera protocols. Whether a specific camera's audio or two-way talk will work should be checked against its manufacturer documentation and the current documentation for the card and streaming server.