Start with the saved file, not the live preview
Download a short recording and play it with headphones. Check that the player is not muted, its volume is up and your computer is sending sound to the headphones you are using. Try a known working audio file too. This separates a playback problem from a recording problem.
Keep the original file while you investigate. If sound is absent from the recorded file, turning up the player cannot recreate it. You may need to record that part again. Do not close the recorder until you have downloaded work you want to keep.
Make a short test with two clear parts: first say a sentence while the shared tab is quiet; then stop speaking and play a sound you have permission to record in that tab. Listen for each part in the downloaded result.
Which part is silent?
- No voice, but tab sound works: check the microphone, its mute switch, device selection and permissions.
- Voice works, but the shared video or app is silent: check the sharing choice and audio option in the browser's screen picker.
- Neither works: check playback first, then test both capture sources separately.
- Sound is doubled or echoes: headphones can stop speaker playback reaching the microphone. Avoid recording the same sound through both a direct source and room speakers.
A moving microphone meter is useful evidence that an input is active, but the saved file is the final check. Likewise, hearing a video through your speakers does not prove the browser recorded it.
1. Restore microphone narration
Check any physical mute switch on your headset or USB microphone. Reconnect a loose cable and choose the intended input in the recorder. A laptop microphone, headset microphone and USB microphone are separate devices; selecting a headset for listening does not necessarily select its microphone for recording.
In Chrome, open Settings, then Privacy and security, Site settings and Microphone. Check that the recorder site is allowed and select the intended default microphone where needed. Google's microphone permission help explains the current route. Labels may differ by version or managed account.
The operating system can also block browser access. On Windows, check microphone privacy settings and whether desktop apps may access it. On a Mac, check Privacy & Security permissions for the browser. Microsoft's recording permission guide covers these layers; it is written for Clipchamp, so its product buttons are not Creator Recorder buttons.
After a permission change, follow any restart prompt, reopen the recorder and select the microphone again. Download existing work before restarting. On a work or school computer, an administrator may control these permissions. Do not bypass that policy; ask for access or use an approved device.
If the microphone also fails in another trusted recording app, investigate the device or operating system before changing more browser settings. Use the microphone setup guide once the input works.
2. Check shared-tab sound separately
Start a new screen selection. If the sound comes from a browser tab, choose that specific tab and enable its audio-sharing option when the browser offers one. Read the actual picker: the option may be called Share tab audio or similar. Make sure the source video is not muted.
A tab capture does not automatically include sound from another application or another tab. Sharing an application window or the whole screen can offer different audio choices. Availability depends on your browser, operating system, version and selected source. Do not assume that a checkbox shown on someone else's computer will exist on yours.
MDN's screen-capture documentation explains that available audio sources differ between browsers. Apple's screen and system audio permission guide describes the Mac permission layer. Permission alone does not guarantee that a browser can capture every application's sound.
If the browser does not offer the required audio source, use a supported capture method or record a separate narration. Do not route speaker sound through the microphone and assume it is equivalent: it can add echo and room noise. Test the exact route you intend to use.
3. Test before recording the full take
- Keep the same browser, microphone and sharing source you will use for the real video.
- Say a normal sentence with the source quiet.
- Stop speaking and play a brief permitted source sound.
- Stop, download and listen with headphones.
- Confirm the voice and source sound independently, then start the real take.
Change one setting at a time and repeat the test. If you switch microphones, Bluetooth devices, tabs or sharing modes later, run another short check. A successful test on one source does not prove a different source is captured.
For a slide video, also check embedded clips using the presentation voiceover guide. For a software walkthrough, use the tutorial recording checklist.
If an important recording is already silent
First confirm the issue in the original downloaded file, not only in a muted editor preview or an uploaded copy. Keep a backup. If the original has sound but an edited export does not, check the editor's mute and audio settings and make a short export test.
If the original contains no required audio, you cannot recover a signal that was never captured. Record a new voiceover in a suitable editing tool or repeat the affected section. Check timing and meaning after the repair; do not pretend the audio came from the original take.
Common questions
Why can I hear the video but my recording cannot?
Listening and capture are different paths. The source can play through your speakers while the browser captures no audio track. Check the selected tab and audio-sharing option, then review a saved test.
Does allowing the microphone record computer sound too?
No. Microphone permission covers microphone input. Captured tab or app audio is a separate source with its own sharing choices and support limits.
Can this fix every silent recording?
No. Device faults, browser support limits, managed permissions and missing original audio need different solutions. The test helps identify which path to investigate rather than promising a universal fix.
Sources and related guides
Official permission and capture references above were checked 11 October 2026. Browser and operating-system interfaces can change. Verify the saved result on your own device.