Mac Dictation Not Working in Firefox? How to Fix It

Short answer: Mac dictation fails in Firefox for one of four reasons: the cursor is not in an editable field, the site's editor is rewriting text as it arrives, Firefox lacks microphone permission for in-page tools, or you are using Google Docs Voice typing, which Firefox does not support. Test in TextEdit first.

You pressed the dictation shortcut, the little microphone appeared (or did not), you spoke a sentence, and nothing landed in the Firefox text box. Meanwhile the same shortcut works fine in TextEdit, or in Chrome, or it worked in Firefox last week. This is one of the more common "dictation is broken" reports we hear from Mac users who prefer Firefox, and the frustrating part is that it almost never has a single cause.

Firefox handles text input a little differently from Safari and Chrome, and it supports a slightly different set of web features. Those two facts explain nearly every case. This guide walks through a sixty-second triage that tells you which category you are in, then the fix for each, and finally the approach that sidesteps the browser question entirely.

First: which "dictation" are you using?

Before you change any settings, be clear about which of two very different things is failing, because they break for different reasons.

System-level dictation. This is macOS Dictation (double-press the Fn or Globe key, or whatever shortcut you set) or a third-party dictation app. It listens through the Mac's microphone and types the result into whatever field has the cursor. Firefox is just another app to it. It works in the address bar, in comment boxes, in web forms, in Gmail, in anything that accepts typed text.

In-page voice typing. This is a feature of a website, not of your Mac. The most common example is Google Docs (Tools → Voice typing), but some note apps, chat tools, and forms have their own microphone buttons too. These run inside the browser and depend on the browser supporting speech recognition and on the site being allowed to use your microphone.

Here is the fact that resolves a large share of Firefox reports: as of this writing, Firefox does not ship the in-browser speech recognition feature that Google Docs Voice typing relies on. If the Voice typing menu item is missing, greyed out, or opens a microphone that never produces text in Firefox, that is not a setting you can flip. It is a browser feature gap. Your options are to use Chrome for that one feature, or to use a system-level dictation tool that types into the Docs page regardless of which browser it is in. More on the second option below.

If you are using system-level dictation and it is failing in Firefox specifically, keep reading. That is fixable.

The sixty-second triage

Do these three tests in order. Each one rules out a whole category.

1. TextEdit test. Open TextEdit, click into a new document, and dictate one sentence. If nothing appears here either, the problem is not Firefox. Jump to the "macOS Dictation itself" section below, or see our guide to Mac dictation turning on but nothing happening.
2. Address bar test. In Firefox, click into the address bar and dictate a few words. The address bar is a plain native text field, so if text appears there, Firefox is receiving dictated text correctly and the problem is specific to a page or a site.
3. Plain field test. Open any site with a simple text box (a search field, a basic comment form) and dictate there. If that works but a particular site's editor does not, you have found your cause: that site's editor is rewriting text as it arrives.

Most people find their answer by step three. If dictation works in the address bar and in a plain form field but not in Google Docs, Notion, WordPress, or a similar rich editor, go straight to Cause 2.

Cause 1: The cursor is not in an editable field

This sounds too obvious to list first, and it is the most common cause. Dictation types where the cursor is. If the cursor is nowhere, the text goes nowhere.

Firefox has a few focus behaviors that catch people out:

• Clicking on the page background (to bring the window forward, say) moves keyboard focus to the page itself, not to the text box you were in a moment ago.
• Pressing Escape in some web editors dismisses the field's focus without any visible change.
• Switching tabs and coming back does not always restore focus to the field you left.
• Styled text areas that only look focused. Many modern sites draw a highlighted border on a box that is not actually the editable element until you click precisely inside it.
• Editors inside iframes. Comment boxes, embedded CMS editors, and support widgets often live in a frame within the page. Focus needs to be inside the frame, in the actual editable element, not on the frame's border.

The fix is a habit: click directly into the field, watch for the blinking caret, type one character to confirm text lands there, delete it, then dictate. If text is going somewhere unexpected instead of nowhere, our guide to dictation text appearing in the wrong place covers that variant.

Cause 2: The site's editor rewrites text as it arrives

This is the Firefox-specific one, and it explains the "works in the address bar but not in the document" pattern.

Google Docs, Notion, the WordPress block editor, Gmail's compose window, Confluence, Jira, and most other rich web editors do not use a plain text box. They build their own text handling on top of the browser's editable-content support, and each one has its own ideas about how incoming text should be processed.

macOS Dictation does not deliver a finished sentence in one go. It streams words in and revises them as you keep speaking, so the editor receives a sequence of "provisional text, then corrected text" updates. Editors that handle those updates well show a clean result. Editors that do not can produce duplicated words, a missing first word, a cursor that jumps to the start of the paragraph, or text that appears and then vanishes. Because Firefox's implementation of the underlying text-input events differs in small ways from Chrome's and Safari's, a site's editor may behave well in one browser and badly in another. That is why "it works in Chrome" is such a common part of this complaint.

How to confirm it: dictate the same sentence into the Firefox address bar and into the site's editor. Clean in one, garbled in the other means the editor is the problem, not your microphone or your Mac.

Workarounds, from least to most effort:

• Dictate in short bursts. One sentence, pause, let the editor settle, next sentence. Streaming corrections have less to collide with.
• Draft in a plain field, then paste. Dictate into a plain text box (a scratch note, or even the address bar for a short line), copy, paste into the rich editor. Pasting is a single insertion, which every editor handles.
• Use a dictation tool that inserts finished text in one shot. A tool that transcribes after you release the key and then types the completed sentence into the field never sends the editor provisional text, so there is nothing to garble. This is the approach we take with Voice Keyboard Pro, described further down.

The same category of problem shows up in other browsers too. If you also use Chrome, our guide to Mac dictation not working in Chrome covers the Chrome-side variants, and the Safari version is at dictation not working in Safari.

Cause 3: Firefox does not have microphone permission

This one only applies to in-page tools: a meeting site, a browser-based voice recorder, a chat app's microphone button. System-level dictation does not need Firefox to have microphone access, because macOS is doing the listening, not Firefox.

For in-page tools, there are two layers of permission and both must be granted:

1. macOS level. System Settings → Privacy & Security → Microphone. Firefox must appear in the list and be switched on. If Firefox is not in the list at all, it has never asked; visit a site that needs the microphone and click Allow when the macOS prompt appears.
2. Site level. Firefox asks per site. Click the permissions icon at the left of the address bar to see whether the current site is allowed to use the microphone, and to change it. You can review all sites under Firefox Settings → Privacy & Security → Permissions → Microphone → Settings.

Two details that trip people up: private windows do not remember site permissions, so you will be asked every time; and the Firefox permission prompt includes a device dropdown. If you have an external microphone, a USB interface, or Bluetooth headphones connected, make sure the device Firefox picked is the one you are actually speaking into. A site listening to a disconnected interface produces exactly the same silence as a permission problem.

Cause 4: The shortcut is being intercepted

macOS Dictation can be triggered by a double-press of the Fn/Globe key, a double-press of Control, or a custom shortcut. The Fn/Globe double-press is handled by macOS before any app sees it, so a web page cannot steal it. If it does nothing at all, the key may not be assigned to dictation any more; our guide to the Fn key double-press not working covers that setting.

Custom shortcuts are a different story. Web apps like Gmail, Google Docs, Notion, and Linear have their own keyboard shortcut layers, and a shortcut that reaches the page first may be consumed by the page. If you set a custom combination and it works in TextEdit but not in a particular site, that site is claiming the key. Move dictation to a key that no page uses. Third-party dictation tools have the same issue in reverse: pick a hotkey that Firefox and your sites leave alone. F13 through F19 are ideal on keyboards that have them, since almost nothing binds them; a two-modifier combination is the next best choice.

Cause 5: Extensions and hardened privacy settings

Firefox users tend to run more privacy tooling than users of other browsers, and some of it can interfere with in-page voice features. Content blockers, script blockers, and privacy-hardening configurations can prevent a page from reaching the microphone at all, and they do it silently.

The quickest way to find out is Firefox's own Troubleshoot Mode (Help → Troubleshoot Mode), which restarts Firefox with extensions disabled and default settings. If the in-page microphone works there, re-enable your extensions one at a time until it breaks. If you or an administrator have applied a hardened configuration, the setting that disables media capture is the one to look for; you can see whether policies are in effect at about:policies.

Again, this category only affects in-page tools. System-level dictation is unaffected by extensions because the text arrives as if you had typed it.

Cause 6: macOS Dictation itself is the problem

If the TextEdit test failed, Firefox was never the issue. The usual suspects on the macOS side are the wrong input device selected in System Settings → Sound → Input, a dictation language whose model has not finished downloading, a stalled download after a macOS update, or dictation being greyed out under Keyboard settings. Each has its own guide: microphone not working, dictation download stuck, and dictation greyed out. Fix macOS first, then come back to Firefox.

Cause 7: An old or managed Firefox

Less common, but worth thirty seconds: check Firefox → About Firefox for a pending update, since text-input handling does improve between releases. And if this is a work Mac, a managed Firefox may have policies that block microphone permission or specific sites; the about:policies page will show them, and the fix is a conversation with IT rather than a setting.

Firefox, Chrome, and Safari: what actually differs

It helps to have the differences in one place, because "use a different browser" is often the advice people are given and it is only sometimes right.

• System-level dictation works in all three browsers, in any editable field. Rich editors can misbehave in any of them, and which editors misbehave in which browser changes over time.
• Google Docs Voice typing is a Chrome feature first. It is not available in Firefox. If you need that specific menu item, you need a different browser; if you need to dictate into Docs, you do not.
• Per-site microphone permission exists in all three, but Firefox's per-site prompt with a device picker is a place where the wrong microphone gets selected without anyone noticing.
• Extensions are most likely to interfere in Firefox, simply because privacy extensions are most common there.

If dictation is failing in Firefox and every other browser too, look at the third-party app angle rather than the browser angle. Our guide to voice to text not working in third-party apps on Mac covers the app-permission side.

The fix that works on every site: dictate at the system level

Every cause above except the first is a consequence of doing dictation inside the browser: browser feature support, per-site permission, extensions, and how a particular editor handles a stream of provisional text. The way to make all of that irrelevant is to dictate at the system level with a tool that types finished text where your cursor is.

That is what Voice Keyboard Pro does. It is a small Mac menu bar app. You hold a hotkey, speak, and release; the transcribed sentence is typed at your cursor, in whatever app and whatever field is active. Firefox is not special-cased. Google Docs in Firefox, a WordPress editor in Firefox, a Jira comment in Firefox, a search box in Firefox: all of them are just "the field with the cursor."

Why this sidesteps the Firefox problems specifically:

• No browser speech feature required. Google Docs Voice typing not existing in Firefox does not matter, because nothing in the page is being asked to recognize speech.
• No per-site permission. The microphone permission is granted once, to the app, in macOS. Firefox never needs it, and no extension can block it.
• Finished text, one insertion. Because transcription happens after you release the key, the editor receives the completed sentence in a single insertion, the same way a paste does. There is no stream of provisional words for a rich editor to mangle. This is the difference that fixes the "works in the address bar, garbled in the document" case.
• A hotkey pages cannot steal. You choose the key. Set it to something no site uses (F13 to F19 if you have them) and the shortcut interception problem goes away.

Two more things that matter once the basic problem is solved. Smart Vocabulary lets you keep a personal dictionary with replacement rules, so the names of your projects, tools, and colleagues come out spelled the way you spell them, which is not something a browser-based tool can learn about you. And on privacy: our servers store only operational pings, not audio and not transcript content, so what you dictate into a Firefox tab stays between you and that tab.

Honest limits: it still needs an editable field with a cursor in it (Cause 1 is Cause 1 for everyone), and it needs an internet connection to transcribe. Voice Keyboard Pro has a free tier with daily limits, and Pro is $4.99 per month or $34.99 per year. If you want the fuller picture of how the system-level approach compares to the browser-based one, this guide to dictation that types where your cursor is, in any app goes deeper.

Frequently asked questions

Does Apple Dictation work in Firefox at all?

Yes. macOS Dictation is system-level and types into any editable field, including Firefox's address bar, form fields, and web editors. When it fails in Firefox, the cause is almost always focus, a specific site's editor, or the shortcut, not Firefox itself.

Why is Voice typing missing or greyed out in Google Docs on Firefox?

Because Firefox does not support the in-browser speech recognition feature that Google Docs Voice typing depends on. It is a browser feature gap, not a setting. Use Chrome for that menu item, or use a system-level dictation tool that types into the Docs page in Firefox.

Does Firefox need microphone permission for Mac dictation to work?

Not for macOS Dictation or other system-level tools; macOS does the listening. Firefox needs microphone permission (at both the macOS level and the per-site level) only for in-page tools like meeting sites and browser-based recorders.

Dictation works in Chrome but not Firefox. Why?

Usually one of two things: you are using an in-page feature that Chrome supports and Firefox does not, or a particular site's rich editor handles streamed dictation text well in Chrome and badly in Firefox. The address-bar test tells you which. If text lands cleanly in the Firefox address bar, it is the editor.

Why do dictated words duplicate or disappear in Notion or WordPress on Firefox?

Those editors are receiving provisional text that gets revised as you speak, and not every editor handles that well in every browser. Dictate in short bursts, draft in a plain field and paste, or use a tool that inserts finished text in one insertion.

Does a Firefox private window change anything?

For system-level dictation, no. For in-page tools, private windows do not remember site permissions, so you will be prompted for microphone access every time, and any permission you granted in a normal window does not carry over.

The short version

Run the three tests: TextEdit, the Firefox address bar, a plain form field. Where dictation stops working tells you the cause. If it stops at TextEdit, fix macOS. If it stops at a specific site, that site's editor is the problem, and dictating short bursts or pasting finished text will get you through. If the feature you want is Google Docs Voice typing, Firefox does not have it, and no setting will add it.

Or skip the browser question entirely. A system-level tool that types finished text at your cursor works the same in Firefox as it does everywhere else, which is the whole point. Voice Keyboard Pro is free to try; open the Firefox tab that has been refusing to cooperate, click into the field, hold the hotkey, and say the sentence.