Need to put a remote guest, browser-based production tool, or another permitted browser source on air? In some desktop browsers, you can share a tab’s audio directly with compatible broadcast software—without installing a virtual audio cable.
This guide covers when browser capture is a good fit, how to get started, what to expect on different systems, and how to solve common problems.
When to use browser audio capture
Browser capture is useful when the audio source is playing in a browser tab—for example, a conferencing guest or a browser-based production tool—and you want to bring that sound into your station mix. It can be a convenient option on a studio machine where you cannot install drivers or where you want to avoid setting up virtual devices.
It does not capture every app on every computer. If your source is a desktop media player, DAW, or another native application, use an operating-system audio route or a suitable audio interface instead.
Before you start
- Use the current desktop version of Chrome or Edge for the most consistent browser-capture experience in brūhi Cloud Studio.
- Start the source and check that it is playing audio in the tab you intend to share.
- Use headphones if you are monitoring the source locally.
- Make sure the source is one you are permitted to broadcast. Capturing audio does not grant rebroadcast rights.
Browser and operating-system support varies. The browser may offer tab audio, system audio, both, or neither, depending on the selected source and platform. The share dialog is the final check: if it does not offer an audio option, the browser cannot provide audio for that selection. MDN’s getDisplayMedia() guide explains that audio is optional and availability depends on the browser and selected display surface.
Start sharing browser audio
- Check that your broadcast software supports browser-tab or system-audio capture. The exact controls differ by product.
- Open the browser tab that is playing your source.
- In your broadcast software, choose its browser-audio or screen-audio input and start sharing.
- Select the source tab in the browser’s share dialog and enable audio sharing if offered. Share the whole screen only when you specifically need system audio and are comfortable sending all audio from that output to air.
- Confirm that the input meter responds, then bring the source into the mix at a safe level.
- When finished, stop sharing from the browser’s sharing controls or disconnect the input in your broadcast software.
The browser asks you to choose what to share each time. A request to share audio does not guarantee that an audio track will be available; if you do not see meter activity, check your selection and the audio checkbox first.
Browser and operating-system limits
| Source or setup | What to expect |
|---|---|
| Chrome or Edge on desktop, sharing a browser tab | Often the simplest choice for tab audio, when your broadcast software supports browser capture. The share dialog must offer and enable audio. |
| Sharing an entire screen | May offer system audio on some browser and operating-system combinations. It can include sounds from other apps and notifications, so use it only when needed. |
| Firefox or Safari | Audio capture options differ from Chrome and Edge and may not be available for your chosen source. If the share dialog does not offer audio, use another supported browser or an OS-level audio route. |
| Mobile browser | Do not rely on this workflow for a live studio input. Use a supported desktop setup. |
| Native app such as a DAW or media player | Use OS routing or an audio interface; browser-tab sharing will not capture an unrelated app. |
A virtual audio cable creates a software audio device that applications can route sound through. Depending on the tool and operating system, setting one up may require driver installation, permissions, and matching audio settings. There are also built-in OS options: Windows supports loopback capture of an output device, and macOS provides Core Audio taps for capturing process audio in supported applications. Linux systems using PipeWire or PulseAudio can route audio through virtual sinks. These options can be better when you need to capture a native app or route several sources separately. Microsoft’s WASAPI loopback documentation and Apple’s Core Audio taps guide describe their respective approaches.
Avoid echo and feedback
A loop occurs when the audio you are capturing includes the station’s own return. That can send the programme back into the mix and create echo or feedback.
- Share the specific source tab when possible, rather than the entire screen.
- Do not share a tab that is playing the station’s live return or your broadcast software’s control page.
- Use headphones to keep the captured audio out of the room and away from an open microphone.
- If you need to capture system audio, silence notifications and close unrelated audio sources first.
- If a remote guest needs to hear the programme, provide a mix-minus feed that excludes that guest’s own voice.
Some browsers can suppress local playback of captured audio. The setting and behavior vary, so check your browser and monitor with headphones rather than relying on suppression alone.
Levels and sound quality
Start with the source level low, then raise it while watching the input meters. Leave headroom so a loud browser player does not overload the mix. Use the input’s gain and mute controls to manage the captured source independently from the microphone input.
Browser audio is not always delivered at the format your station uses. Check the source level and sound on your on-air monitors before taking it live. Voice-call processing can change music or other programme audio; if the source sounds gated, thin, or uneven, check whether the browser or source application is applying speech-oriented processing.
Troubleshooting
The input meter does not move. Confirm the source is playing, share the correct tab, and enable the audio option in the browser dialog. If the dialog offered no audio option, try Chrome or Edge on desktop or use OS-level routing. Check that your broadcast software supports this kind of capture.
There is echo or doubled audio. Stop sharing the station return or your broadcast software’s control tab. Share only the source tab, use headphones, and check whether the source is also playing through another route into the mix.
Notifications or other apps are audible. You are likely capturing system audio. Stop sharing and select the specific source tab, or silence other apps before sharing the screen again.
The sound is too loud, thin, or uneven. Lower the input gain and check the source application’s output level. If voice processing is enabled in the source app or browser, turn it off when appropriate for the material.
The audio stops unexpectedly. The shared tab may have been closed, navigated away, or stopped from the browser’s sharing controls. Start sharing again and confirm that the meters respond.
A native app is silent. Browser sharing captures the selected browser source, not an unrelated desktop application. Use OS-level routing or an audio interface for native apps.
Broadcast rights
Only capture sources you have the right to broadcast. Access to a streaming service or web player does not by itself permit rebroadcasting. Music and other content may require licences in your territory; check the terms for your source and the requirements that apply to your station.