How to record a Chrome tab with audio in 2026 (the right way)

The most common complaint about Chrome screen recorders isn't "the picture is bad" — it's "there's no audio". You hit Record, do the thing, hit Stop, watch the MP4 back in QuickTime, and it's a silent film. This is almost never a bug in the extension. It's almost always one specific Chrome behavior that the extension didn't surface clearly enough in the UI. This post walks through what's actually happening, the three different audio sources Chrome can capture, and the exact workflow we use in ClearRec to make sure the right audio lands in the file every time.

The three different audio sources, and why they matter

Before anything else: Chrome can capture audio from three completely different places, and the right answer depends on which one you mean.

1. Tab audio — the sound coming out of the specific Chrome tab you're recording. The YouTube video, the Google Meet call, the embedded audio player, the website's UI sounds.
2. System audio — the sound coming out of every application on the machine, mixed together. Useful when the audio is in a desktop app, not a tab.
3. Microphone audio — your voice, narrating over the recording. Useful for walk-throughs, lecture-style demos, "let me show you how I'd debug this" videos.

Most failed recordings are people who meant Tab Audio and accidentally captured Microphone (or vice versa). Chrome's UI surfaces this with a checkbox so small it's missable, and most "free screen recorder" extensions inherit the same UI. The fix is to know what you're choosing before you click Start.

ClearRec exposes all of these in the popup before you click Start. The default for Screen capture mode is microphone off (because most screen recordings are silent UI demos); the default for Tab capture mode is microphone off + tab audio on (because if you're capturing a tab, the audio is usually the point).

Why your last recording was silent

Three causes, in order of frequency:

1. You hit "Screen" or "Window" instead of "Chrome Tab"

This is by far the most common cause. The Chrome screen-capture APIs treat "share this tab" and "share this screen" as two genuinely different operations, and tab audio capture only works in the Tab path. If you pick Screen or Window, Chrome will gladly record the video but it will refuse to attach the tab's audio — even if the audio was playing audibly throughout the recording.

The fix: when you launch the recorder, pick Chrome Tab as the capture target if you want the tab's audio. The Tab picker will then show a "Share tab audio" checkbox; make sure it's ticked. (ClearRec ticks it by default.) The recorded MP4 will contain the tab's audio mixed into the file.

2. "Share tab audio" was unticked

Even on the Tab picker, the checkbox is opt-in. Chrome's UI defaults it to ticked in some versions and unticked in others; on macOS the toggle is in a different place than on Windows. If the recording is silent and you definitely picked the Tab option, this is the next thing to check.

ClearRec defaults to ticked because the absence of audio is almost never what you want when recording a tab. (If you genuinely want a silent capture of a tab, you can untick it, but the default is the friendly choice.)

3. The microphone was muted or set to the wrong device

If you wanted narration and got silence, the microphone is the suspect. Open the OS sound settings, confirm the microphone you expect is selected, confirm it's not muted, and confirm Chrome has permission to use it (chrome://settings/content/microphone). A common gotcha: Bluetooth headsets sometimes switch the active mic to the built-in laptop mic when their battery is low, with no notification.

The exact workflow for "record a tab with its audio"

The path that works every time, broken down by what you click:

Step 1 — Open the recorder on the tab you want to capture

Install ClearRec from the Chrome Web Store if you haven't. Open the tab whose audio you want to record — the YouTube video, the Meet call, the web app. Click the ClearRec icon in your toolbar.

Step 2 — Pick "Chrome Tab" as the capture mode

In the launcher popup, choose Chrome Tab (not Screen, not Window, not Webcam). This is the step that determines whether tab audio is even possible. If you skip this and pick Screen, the rest of the workflow is irrelevant — the audio won't be in the file.

Step 3 — Confirm "Share tab audio" is on

Chrome will pop a tab picker. The checkbox labeled "Share tab audio" or "Also share audio" needs to be ticked. ClearRec ticks it by default. If you've previously unticked it, Chrome remembers that choice across sessions, so this is worth verifying.

Step 4 — Decide on the microphone

The ClearRec popup has a microphone toggle. The decision rule:

• Off if you don't want to narrate (you'll only get the tab's audio).
• On if you want to mix your voice on top of the tab's audio (the walk-through style).

If both are on, the resulting file has a single audio track with both sources mixed together. There's no separate "tab" and "mic" track in the export — that's a constraint of the WebM/MP4 container ClearRec writes, and matches what every other Chrome recorder does.

Step 5 — Hit Start, do the thing, hit Stop

Standard recording flow. The recording overlay shows a level meter for the audio source — if the meter is flatlining when you expect sound, that's the moment to stop and check the source selection rather than after the fact.

Step 6 — Confirm the audio is in the export

In the trim editor, the timeline shows the audio waveform underneath the video preview. If the waveform is flat, the audio didn't make it in. (This is almost always a Step 2 issue — pick Chrome Tab and re-record.) If the waveform looks right, hit Export MP4 and you're done.

Recording a specific use case: YouTube with sound

YouTube is the canonical "record a tab with audio" use case. The full workflow:

1. Open the YouTube video. Hit pause if you want to compose your start, or just let it play.
2. Open ClearRec → Chrome Tab → tick Share tab audio → mic off → Start Recording.
3. Hit play on the YouTube tab. Let it play for as long as you need.
4. Hit Stop. The MP4 in your Downloads folder has the video and the audio.

Two caveats worth knowing:

• Copyright. Recording a YouTube video for fair use purposes — research notes, criticism, education — is generally fine in most jurisdictions. Re-uploading the recorded clip to another platform is a different matter, and not something this post is going to advise on. If you're recording for personal reference (the "let me save this for later" use case), you're in the clear. If you're recording to re-publish, talk to a lawyer.
• Frame rate. YouTube videos at 60 fps look fine recorded at 30 fps — the perceptual difference is small for talking-head content. Use ClearRec's Medium tier (1080p / 30 fps) and the file will be ~1 MB per minute of recording.

Recording a Google Meet call (with consent)

A common ask. The mechanics are identical to YouTube — Chrome Tab capture with "Share tab audio" on. The only thing to add is consent: in most jurisdictions, recording a video call requires the consent of the other participants. Google Meet itself shows a "this meeting is being recorded" banner when the built-in recording feature is used; if you're using an external recorder, the legal requirement to notify is on you, not the tool.

The pragmatic workflow:

1. At the start of the call, tell participants you're recording.
2. Hit ClearRec → Chrome Tab → the Meet tab → tick Share tab audio → Start.
3. Run the call as normal.
4. Stop when the call ends. The full meeting — video grid, screen-share, audio — is in the MP4.

This is genuinely useful for: async stakeholder updates, post-meeting transcription, archived design reviews. It is genuinely not the right tool for: secretly recording a customer call. Get consent.

Recording a web app with both UI sounds and your narration

Demo videos for a web app are the classic "tab audio + microphone" case. The web app makes a ding when a notification arrives; you want to narrate "watch — this is the notification when a new message comes in". Both need to be in the file.

Workflow:

1. ClearRec → Chrome Tab → pick the app's tab → tick Share tab audio → mic on.
2. Verify the mic level meter in the popup responds when you speak.
3. Start. Narrate over the app. The recording will contain both sources mixed.
4. Export MP4.

If the result has your voice but not the app's sounds, you accidentally picked Screen, not Chrome Tab. If it has the app's sounds but not your voice, the mic was off or assigned to the wrong device.

What about system audio (everything on your desktop)?

Tab audio covers ~80% of cases. System audio — capturing the entire desktop's mixed audio — covers the other 20% and is significantly more complex than tab audio for one reason: the operating system doesn't expose it through a clean API.

On the three platforms:

• macOS: Chrome can capture system audio when you pick the Screen capture mode and the OS-level "Share system audio" permission is granted. On recent macOS versions (14+), the permission is part of the screen-recording permission grant. If you don't see a system-audio option, check System Settings → Privacy & Security → Screen & System Audio Recording and re-grant Chrome's permission.
• Windows: Chrome's Screen capture mode supports system audio out of the box on Windows 10/11. Tick "Share system audio" in the picker.
• Linux: System audio capture in Chrome on Linux is patchy. PulseAudio works through pavucontrol; PipeWire works in most distributions in 2026 but the experience is less polished. If you're on Linux and the system-audio toggle isn't there, you'll need a desktop recorder rather than a Chrome extension.

ClearRec exposes the system-audio checkbox automatically when the OS supports it. If you don't see the option, the cause is one of the three OS-specific issues above.

Diagnostics: a checklist when audio still doesn't record

Run this list in order. The first match is almost always the cause.

1. Did you pick Chrome Tab? Screen and Window can't capture tab audio, only system audio (and only on platforms where the OS allows it).
2. Is "Share tab audio" ticked in the Chrome picker? It's a separate checkbox from "Share this tab".
3. Is the source actually emitting audio? Play the tab outside the recording, with the volume up, and confirm you can hear it through your normal output device.
4. Is your output device not Bluetooth? Some Bluetooth headsets cause Chrome to fall back to a different audio routing path; the recording can still work but the diagnostic is harder.
5. Is the microphone permission granted? chrome://settings/content/microphone.
6. Is the microphone device correct? OS sound settings → confirm the right mic is selected.
7. Is the mic muted at the OS level? Some laptops have a hardware mute key.
8. Is the mic muted in the meeting / app? Meet, Zoom, and Teams all have their own mute states.
9. Is the export actually silent or is the player muted? Sounds dumb, but: open the MP4 in a different player to rule out a player-side mute.

If you walk that list and the answer is "all of those are correct", you've found a genuine bug. We treat audio bugs as P1s — file an issue with a recording of the issue and we'll dig in.

File size: what audio adds

A common follow-up: does recording audio make the file much bigger? Short answer: no.

For a 60-second screen recording at 1080p / 30 fps / 5 Mbps:

• Video-only MP4: ~38 MB
• Video + AAC 128 kbps audio: ~39 MB

Audio adds roughly 16 KB per second at the default AAC bitrate. Over a 30-minute recording that's still under 30 MB of audio overhead. It's never the reason a recording is too large; the video bitrate is.

What ClearRec does differently

Most screen recorder extensions surface a single "Microphone" toggle and hope the user understands the difference between mic, tab audio, and system audio. ClearRec separates them in the popup with distinct controls, defaults Tab Audio to on when Tab capture is selected (because if you're recording a tab, the audio is usually why), and shows a live level meter for the active audio source so a silent meter is visible before you waste a recording.

The other thing worth naming: every recording happens locally. There's no server in the audio path. Whatever your mic captures, whatever the tab emits, is encoded by Chrome's MediaRecorder API and written straight to your Downloads folder. No upload step, no third-party transcription service, no "we keep a copy on our servers for diagnostics". The audio in your recording is between you and your laptop, full stop. (Privacy policy has the full data-flow breakdown.)

Frequently asked questions

Q: Can I record only the audio, no video? Not from a Chrome screen recorder — Chrome's getDisplayMedia() API requires a video source. For audio-only capture, use Chrome's voice recorder PWA or a desktop tool like Audacity. ClearRec is a screen recorder; if your use case is audio-only, it's the wrong tool.

Q: Can I record tab audio without recording video? No, for the same reason — the API is bundled. The workaround is to record video + tab audio, then strip the video in a downstream tool. ffmpeg can do this in one command: ffmpeg -i input.mp4 -vn -c:a copy audio.m4a.

Q: Why does my recording have my voice but the YouTube audio is muted? You almost certainly picked Screen instead of Chrome Tab. The Screen capture mode doesn't capture tab audio (it captures system audio if the OS allows). Re-record with Chrome Tab selected.

Q: My recording is in stereo but my mic is mono. What happened? Chrome's MediaRecorder mixes mono mic into a stereo track automatically. The "second channel" is a duplicate; the file is still functionally mono.

Q: Can I record two tabs' audio at the same time? Yes, but indirectly. Pick Screen capture mode and tick Share system audio; whatever's playing in any tab will be in the mixed system audio. There's no built-in "record tab A's audio + tab B's audio separately" mode in Chrome — that would require capturing two streams from getDisplayMedia(), which the API doesn't support.

Q: Can I record audio from a tab in the background? Yes. Once recording starts, you can switch tabs and the original recording continues. The audio keeps flowing. This is genuinely useful for "I want to record a YouTube video while I work on something else in another tab".

Q: Does ClearRec capture system notification sounds? Only in Screen + system-audio mode (where the OS supports it). In Chrome Tab mode, the recording captures only the selected tab; system notification sounds aren't mixed in.

Q: Why does my exported audio sound robotic / pitch-shifted? Almost always an output sample-rate mismatch in a downstream tool. The MP4 contains 48 kHz AAC; if you played it back in a player that's set to 44.1 kHz, the pitch shifts. Open the file in a different player — VLC, MPV — to rule that out before assuming the recording is broken.

The summary

The pattern that works:

1. Chrome Tab capture mode (not Screen, not Window) if you want tab audio.
2. Share tab audio ticked in Chrome's picker.
3. Microphone on if you want narration, off if you don't.
4. Verify the audio waveform in the trim editor before exporting.

That's the entire flow. The reason this post exists is that the first three steps are spread across three different UI surfaces in stock Chrome and it's easy to miss one. ClearRec's launcher consolidates them into a single popup with sensible defaults; if you want the simplest path to a tab recording with audio, install ClearRec from the Chrome Web Store and pick Chrome Tab. The first recording will have audio.

See also

• Screen recording for bug reports: a developer's complete guide — when silence is the right answer.
• MP4 vs WebM vs GIF: which screen recording format should you use? — what to export the audio-bearing recording as.
• The 6 best free Chrome screen recorder extensions (2026 review) — how the six tools handle audio differently.
• The best free Loom alternative for Chrome (2026) — when local audio beats cloud audio.
• Privacy policy — what happens to the audio bits after capture.