01 — Start here
Which audio are you actually after?
Almost every problem people have with this comes from mixing up two jobs that sound identical when you describe them out loud.
Recording your own voice means capturing your microphone through the browser. No extension is needed; the browser has been able to do this natively for years, and any recording site simply asks your permission and writes the file.
Capturing tab audio means recording the sound a page is playing: a video, a stream, a call. Chrome does not expose this to ordinary web pages, so it needs an extension with permission to capture the tab. This is the one people usually cannot find, because they search for a recorder and get microphone tools.
Decide which you need before installing anything. If you want both at once, that is a third case and it is covered further down.
02 — Your own voice
Recording your microphone, no install
Open a browser-based recorder, click record, and allow the microphone when Chrome asks. The permission prompt appears once per site. That is the whole process, and it works the same on Windows, Mac, Linux and ChromeOS.
Choose the input before you start rather than after. If a headset, webcam or interface is connected, Chrome may not pick the one you expect, and there is no way to change your mind once a take is recorded.
This is what Hilite does: recording in the browser with nothing to install, then editing and publishing in the same place. We make it, so weigh that recommendation accordingly, but the underlying browser capability is the same wherever you use it.
One limitation worth planning around: if Chrome is closed, the tab is discarded, or the machine sleeps, an in-progress recording can be lost. For anything long or irreplaceable, use a tool that saves as it goes rather than only at the end.
Record ten seconds and play it back before the real take. Nearly every failed browser recording is the wrong input device selected, and ten seconds catches it.
03 — Sound from a page
Capturing what a tab is playing
This needs an extension. Chrome gives extensions a tab capture permission that ordinary pages do not get, which is why no website can offer this and why the search results for it are full of extensions rather than web apps.
The pattern is the same across all of them: install, open the tab making the sound, click the extension icon, start capture, then save when you are done. Most output MP3 or WAV.
Two things reliably catch people out. Capture usually starts from the moment you click, not from the beginning of whatever is playing, so start the extension first and the media second. And audio often keeps playing through your speakers while being captured, so what you hear is not proof it is being recorded.
Be deliberate about what you install. A tab capture extension can, by design, listen to what your tabs are playing. Prefer one with a large user base and a clear privacy policy, and remove it when the job is done.
04 — Both at once
Your voice over what is playing
Commentary over a clip, or a recorded call with your side included, needs both sources at the same time. Some capture extensions offer a microphone option alongside tab audio; that is the simplest route when it works.
The better approach, if you plan to edit, is to record the two sources separately and combine them afterwards. Mixed-down audio cannot be unmixed, so a single combined file leaves you unable to lower the clip under your voice or cut a section cleanly.
This is the same reasoning behind recording each track separately in a multi-person conversation. Separate tracks cost nothing at record time and save the entire edit.
05 — When nothing records
Microphone permissions, in order
Check the site first. Click the icon at the left of the address bar and look at the microphone setting for that site. If it was blocked once, Chrome remembers and will not ask again, which looks exactly like the recorder being broken.
Then check Chrome. Open Settings, go to Privacy and security, then Site settings, then Microphone. This page lists every site you have allowed or blocked and lets you change any of them, and it also shows which input device Chrome is using.
Then check the operating system. On macOS, Chrome itself needs microphone access under Privacy and Security settings. On Windows, microphone access has both a system-wide switch and a per-app one. If Chrome is blocked at that level, no amount of clicking Allow in the browser will help.
Finally, close anything else holding the microphone. A conferencing app left running in the background is a common cause of a browser recorder that opens fine and captures silence.
06 — Afterwards
Making a browser recording sound good
Browser recording quality is set almost entirely by your microphone and your room, not by the browser. A laptop microphone in a hard-surfaced room sounds like a laptop microphone in a hard-surfaced room whatever software you record with.
Get closer to the microphone than feels natural, put something soft in the room, and turn off any fan you can. Those three things beat any processing you can apply afterwards.
For what remains, an audio enhancer will lift the voice out of the room and even out the level, which is most of the distance between a browser recording and something publishable.
Record your voice in the browser
Nothing to install, and the editing is in the same place.
Record in the browser, nothing to install.
Record, edit and publish with Hilite.