Mac Dictation Not Working in Brave? 9 Fixes That Work

Short answer: If Mac dictation is not working in Brave, enable Brave under System Settings, Privacy & Security, Microphone, then quit Brave fully and relaunch. If in-page voice typing is the problem instead, lower Brave Shields for that site and turn off strict fingerprint protection, because Brave blocks the browser speech service Chrome uses.

Brave is a privacy browser first and a Chromium browser second, and that ordering is exactly why dictation breaks in it more often than in Chrome. Brave ships with protections switched on by default that other browsers leave off, and several of those protections sit directly on top of the plumbing that voice input needs: microphone access, device enumeration, third-party scripts, and the browser speech service.

The good news is that the failures are predictable. There are only a handful of things that can go wrong, and once you know which layer is blocking you, each one takes under a minute to fix. Work through the checks below in order and stop when your voice comes back.

First, work out which kind of dictation is failing

This is the step almost everyone skips, and skipping it is why people spend an hour toggling the wrong settings. Two completely different systems get called "dictation in Brave," they fail for different reasons, and a fix for one does nothing for the other.

System dictation (the Mac's own voice input)

This is macOS dictation, triggered from the keyboard shortcut you set in System Settings, usually a double tap of the Globe or Fn key. It is part of the operating system. It does not care what website you are on. It listens, then types characters into whatever text field currently has focus, exactly as if you were pressing keys. When this is what fails, the cause is almost always a macOS permission or a keyboard focus problem, not a Brave setting.

In-page voice typing (the microphone button on a website)

This is a feature of the web page itself: the mic icon in Google Docs, a voice search button, a dictation control inside a web app. These rely on browser APIs and on scripts the page loads. When this is what fails, the cause is almost always Brave: Shields, site permissions, fingerprint protection, or the missing browser speech service.

The fastest way to tell them apart is a thirty-second test. Open a plain text field, such as the search box on any simple page, and trigger your macOS dictation shortcut. If the microphone indicator appears and words land in the box, system dictation is healthy and your problem is a page-level feature. If nothing happens at all, start at fix 1.

Fix 1: Give Brave the microphone permission in macOS

macOS gates the microphone per application. Brave has to be listed and enabled, and a browser you installed and immediately started using may never have been prompted at a moment when you noticed.

1. Open System Settings.
2. Go to Privacy & Security, then Microphone.
3. Find Brave Browser in the list and switch it on.
4. If Brave is not in the list at all, the prompt was dismissed or never fired. Visit any page with a mic button and click it once to force the request.

The part people miss: toggling this permission does not apply to an already-running browser. Brave has to be restarted for the new grant to take effect, and closing the window is not enough. Use Command-Q, confirm Brave is gone from the Dock, then reopen it.

Fix 2: Confirm dictation is actually enabled in macOS

If system dictation does nothing anywhere, not just in Brave, then the feature itself is off or its shortcut is unset.

1. System Settings, then Keyboard.
2. Scroll to Dictation and make sure the toggle is on.
3. Check the Shortcut dropdown and note what it is set to. If it reads Off, choose a shortcut.
4. Check the Language list includes the language you are speaking. Dictation will silently produce nonsense or nothing at all if you are speaking a language that is not enabled.

Also check the input device. System Settings, Sound, Input shows which microphone macOS is listening to. If a headset is selected but sitting in a drawer, dictation is technically working and hearing nothing. Speak and watch the input level meter move. No movement means you have a hardware or device-selection problem rather than a Brave problem, and our guide to fixing a Mac microphone that dictation cannot hear walks through that in detail.

Fix 3: Allow the microphone for that specific site in Brave

Brave keeps its own permission layer underneath the macOS one. Even with the operating system happy, an individual site can be blocked.

1. Open the site where voice typing fails.
2. Click the lock or tune icon at the left of the address bar.
3. Look for Microphone and set it to Allow.
4. For a global view, open brave://settings/content/microphone and check that the site is not on the "Not allowed" list.

Two Brave-specific traps live here. First, a site denied once in a private window keeps that decision for the session, so a page you blocked in a hurry stays blocked. Second, Brave defaults to asking per site, which means every new web app in your workflow needs its own grant. If the page never shows a permission prompt at all, the request is being blocked upstream, which is the next fix.

Fix 4: Lower Brave Shields for the page

Shields is Brave's signature feature and the single most common reason voice typing fails in Brave but works in Chrome. It blocks trackers, cross-site scripts, and cosmetic elements. Voice input on many web apps is served from a different domain than the page you are on, which makes it look exactly like the third-party script Shields is designed to stop.

1. Click the Brave lion icon in the address bar.
2. Toggle Shields down for that site, or set Trackers & ads blocking to Standard rather than Aggressive.
3. Reload the page and try the mic button again.

If lowering Shields restores voice typing, you have found your culprit. You do not have to leave Shields off everywhere. Brave remembers the setting per site, so the exception applies only to the one web app that needs it. That is a reasonable trade for the tool you dictate into all day, and the rest of your browsing keeps full protection.

Fix 5: Relax fingerprint protection

Brave's fingerprinting defense deliberately lies to websites about your hardware, and one of the things it can obscure is the list of audio input devices. A page that asks "what microphones does this machine have" and receives an empty or randomized answer will show a greyed-out mic button or an empty device picker, with no error message explaining why.

In the Shields panel for the site, find Fingerprint blocking and move it from Strict to Standard. Reload and retry. If a web app's dictation control is visible but permanently disabled, and the site's own microphone test page reports no devices found, this setting is almost always the reason.

Fix 6: Test in a clean profile and without extensions

Brave runs Chrome extensions, and extensions can claim or break microphone access. Meeting recorders, note-taking assistants, transcription add-ons, and privacy extensions are the usual offenders, especially any that hold the mic open in the background.

Open a new private window, which loads without extensions, and try again. If dictation works there, an extension is the cause. Re-enable extensions one at a time from brave://extensions until the failure returns. Also worth checking: Brave profiles keep separate permission sets, so if you have a work profile and a personal profile, a grant in one does nothing in the other.

Fix 7: Clear a Secure Input lock

This one is invisible and maddening. macOS has a mode called Secure Input that stops applications from observing keystrokes, and it is triggered by password fields. When an app enables it and fails to release it, usually because a password prompt was closed oddly or a terminal session was interrupted, system dictation stops inserting text. You get the microphone indicator and no characters.

Three things clear it, in increasing order of disruption: click into a normal text field and press Escape or Tab to move focus off any password field; quit the app that last showed a password prompt, which is often a password manager or a terminal; or log out of your macOS account and back in, which always releases the lock. A full restart is the last resort and is rarely necessary.

If dictation has stopped working in several apps at once rather than only in Brave, Secure Input is the first thing to suspect. Our general Mac dictation troubleshooting guide covers the system-wide version of this problem.

Fix 8: Restart Brave properly, then check for an update

Brave keeps a process alive after the last window closes if background apps are enabled, and that lingering process holds the old permission state. A genuine restart means Command-Q, checking the menu bar and Dock for a leftover Brave icon, and quitting that too.

While you are there, open brave://settings/help and let it update. Chromium's media handling changes often, and permission bugs that affect the microphone get fixed in point releases. If dictation broke the same week you updated macOS, the reverse also applies: a browser built against the previous system can misbehave until it catches up. Our notes on dictation breaking after a macOS update explain why permissions in particular get reset by system upgrades.

Fix 9: Recognise the editors that cannot receive dictated text

Some web apps do not use real text fields. Their editor is drawn on a canvas and keyboard input is intercepted by JavaScript. Because macOS dictation works by inserting characters into the focused field, it has nothing to insert into. The dictation indicator appears, you speak, and nothing lands.

Design tools, diagram apps, spreadsheet grids, and a few document editors behave this way. When you hit one, the reliable workaround is to dictate into a plain field and move the text across, or to use a dictation tool that types at the cursor the way a keyboard does rather than relying on the browser. If that is your daily situation, the section below is the real answer rather than a workaround.

Why Google Docs voice typing fails in Brave specifically

This deserves its own section because it is the most reported Brave dictation complaint and none of the fixes above will solve it.

Chrome's in-page speech recognition is not a local feature. It streams audio to a Google speech service, and access to that service runs through private API keys that Google includes in its own builds of Chrome. Brave, which strips Google service dependencies as a matter of policy, does not ship those keys. The result is that web pages calling the browser speech API in Brave get silence or an immediate error, and Google Docs Voice typing in particular tends to appear greyed out, start and instantly stop, or never produce text.

This is a design decision, not a bug on your machine. You can confirm it in two minutes: open the same document in Chrome or Safari and try Voice typing there. If it works in Chrome and fails in Brave with every permission granted and Shields fully down, you have hit the missing service, and no amount of setting-toggling will change it. Our post on Google Docs voice typing not working covers the other causes worth ruling out first.

Your options are to keep a second browser open for documents you dictate into, or to stop depending on the browser for voice input entirely.

Quick triage table

The approach that sidesteps the browser entirely

Notice what every fix above has in common. You are negotiating with three separate permission layers, and a fourth party, the website, gets a vote as well. That negotiation has to be repeated for every new web app you adopt, and a browser update can reset it. If you dictate occasionally, that is an acceptable annoyance. If dictation is how you write, it is a recurring tax.

Voice Keyboard Pro takes the browser out of the loop. It lives in your Mac's menu bar. You hold your hotkey, speak, release, and the text appears at your cursor in whatever app has focus, including Brave, including a Brave window with Shields at maximum. Because it types at the cursor rather than asking the page for microphone access, Brave's protections are irrelevant to it. There is one permission to grant, once, and it applies everywhere on the machine.

That also fixes the Google Docs problem, because nothing is asked of the browser speech service. And it fixes the privacy discomfort that brought you to Brave in the first place, since you are no longer routing your dictation through whatever a given website chooses to do with it. Our servers store only operational pings. No audio and no transcript content is kept.

A few things that matter once dictation becomes your main input method rather than an occasional trick:

• Smart Vocabulary is a personal dictionary with replacement rules, so the client names, product names, and jargon that browser dictation mangles come out correctly every time.
• Meeting Mode detects who is speaking and drafts notes, which covers the browser-based calls where in-page transcription is exactly the kind of script Shields blocks.
• Calendar meeting detection notices a meeting starting and offers to capture it.
• The iPhone keyboard carries the same thing to your phone, with a built-in mic button that works in any iOS app, plus Voice Edit for fixing a sentence by speaking the change, two-way translation across 24 languages, and swipe typing when speaking is not an option.

On the speed question, the arithmetic has not changed. Comfortable speech runs at 130 to 150 words per minute. The average adult types around 40, and even a genuinely fast typist lands around 80 to 100. The reason people persist through browser permission dialogs is that the payoff is real. It is simply better to collect that payoff without the dialogs.

If you had to grant a permission, lower a shield, and open a second browser to dictate one paragraph, the tool is in the wrong layer of the stack.

Frequently asked questions

Does Brave support voice typing at all?

Brave supports microphone access for websites, so web apps that implement their own recording and transcription work normally once permissions and Shields allow it. What Brave does not support out of the box is the Chromium browser speech API that depends on a Google service, which is the specific thing Google Docs Voice typing uses.

Why does dictation work in Chrome but not Brave on the same Mac?

Three reasons, in order of likelihood. Chrome already holds the macOS microphone permission and Brave may not. Chrome does not run Shields, so it loads scripts Brave blocks. And Chrome ships the speech service keys Brave omits. The first two you can fix; the third you work around.

Is turning Shields off for a site dangerous?

It reduces protection on that one domain only, and Brave still applies its baseline privacy settings. For a web app you have already chosen to trust with your documents and your voice, it is a modest change. Turning Shields off globally is the thing to avoid.

Will a Brave update reset my microphone permissions?

Browser updates usually preserve site permissions, but macOS upgrades can reset the operating-system level grant for applications. If dictation stops working after a system update, recheck Privacy & Security, Microphone before touching anything inside Brave.

What about dictation in Brave on iPhone?

On iOS the picture is different, because dictation comes from the keyboard rather than the browser. Any keyboard with a microphone works in Brave on iPhone the same way it works in Safari, which is why a keyboard-level tool is the more portable answer across both devices.

What to do next

Run the triage table from the top. In most cases the answer is fix 1, a macOS permission Brave never received, followed by a proper quit and relaunch. If the mic button on a page is the problem rather than the shortcut, it is Shields or fingerprint blocking, and both are one click in the lion menu. If it is Google Docs Voice typing, stop troubleshooting, because the service is not there to be fixed.

And if you are here because this is the third browser where dictation has needed babysitting, that is the signal to move voice input down a layer. Voice Keyboard Pro has a free tier on both Mac and iPhone. Install it, grant one permission, and dictate into Brave with Shields exactly where you want them.