Short answer: Apple Dictation often fails in Google Docs on Chrome because the Docs editor is not a standard macOS text field, so dictated text has nowhere reliable to insert. Use Google Docs' own Voice typing (Tools menu, Chrome only), grant Chrome microphone access, or use a tool that types at the cursor in any app.
You can dictate happily into Notes, Mail, and Safari, but the moment you open a document in Google Docs inside Chrome, Apple Dictation goes quiet. The microphone indicator might appear, your words might land in the wrong spot, or nothing happens at all. It is one of the most frustrating dictation failures on a Mac because everything else works fine.
The good news: this is a known, explainable problem, not a broken Mac. Below is exactly why macOS Dictation struggles inside Google Docs on Chrome, an eight-step fix checklist, and the most reliable long-term workaround.
Why Apple Dictation breaks specifically in Google Docs
To understand the fix, you need to understand what Google Docs actually is. Unlike Notes or a standard web form, the Google Docs editor is not a normal text box. It is a custom-built editing surface that renders text and the cursor itself, intercepting keystrokes and managing the document in its own way rather than using the browser's standard text input.
Apple Dictation was designed to insert text into standard system text fields. When it finishes recognizing your speech, it hands the resulting text to whatever field has focus. In most apps that works perfectly. But Google Docs does not present a standard field for Dictation to write into, so the handoff has nowhere clean to land. The result is the classic symptom set: text that never appears, text that appears in the wrong place, or dictation that starts and immediately stops.
This is the same underlying reason Apple Dictation is unreliable in many browser-based apps, which we cover in voice to text not working in third-party apps on Mac. Google Docs is just the most common place people hit it.
If dictation works everywhere except Google Docs, the problem is almost never your microphone. It is the gap between how macOS inserts text and how the Docs editor accepts it.
Two different "dictation" features get confused here
Part of the frustration is that there are two separate voice features in play, and people mix them up:
- Apple Dictation is the system-wide macOS feature you trigger with a keyboard shortcut. It is supposed to work in any text field, anywhere.
- Google Docs Voice typing is a feature built into Google Docs itself, found under
Tools → Voice typing. It only works in the Chrome browser, and it inserts text directly through the Docs editor — which is exactly why it succeeds where Apple Dictation fails.
Knowing which one you are trying to use changes the fix entirely. If you specifically want to talk into a Google Doc on Chrome, the built-in Voice typing tool is the path of least resistance.
Fix checklist: get voice typing working in Google Docs
Fix 1: Use Google Docs' built-in Voice typing
This is the most direct fix because it is purpose-built for the Docs editor and only runs in Chrome.
- Open your document in Google Docs in Chrome.
- Go to the
Toolsmenu and choose Voice typing (or press the keyboard shortcut shown next to it). - A microphone box appears. Click it once so it turns active, then start speaking.
- Click the microphone again to stop.
If the Voice typing option is missing or greyed out, you are almost certainly not in Chrome — Google restricts this feature to its own browser. Switch from Safari or another browser to Chrome and the option returns. For a deeper walkthrough, see voice typing in Google Docs on Mac, and if the built-in feature itself misbehaves, Google Docs voice typing not working covers the common failure points.
Fix 2: Grant Chrome microphone permission
Voice typing needs the browser to access your mic. macOS and Chrome both have to allow it.
- In macOS:
System Settings → Privacy & Security → Microphoneand make sure Google Chrome is toggled on. - In Chrome: click the icon at the left of the address bar (or open
Settings → Privacy and security → Site Settings → Microphone) and confirmdocs.google.comis set to "Allow." - Reload the document after changing permissions.
If you have multiple microphones (built-in, AirPods, an external interface), check that the one Chrome is using is the one you are actually speaking into.
Fix 3: Click directly into the document body first
Both Apple Dictation and Google Voice typing need a clearly placed cursor. Before you start talking, click inside the document text so you see the blinking insertion point. If your cursor is in a comment box, a title field, or no field at all, dictated text has nowhere to go.
Fix 4: Re-enable and reset Apple Dictation
If you would rather use macOS Dictation than the Docs feature, make sure it is actually on:
- Go to
System Settings → Keyboard → Dictationand confirm the toggle is on. - Note the shortcut and test it first in Notes to confirm Dictation works at all.
- If it is greyed out, Voice Control may be enabled and blocking it. See why Mac Dictation conflicts with Voice Control to resolve that.
Even when Apple Dictation is healthy, expect it to be hit-or-miss inside the Docs editor for the structural reason described above. Notes confirms the feature works; Docs is where the editor gets in the way.
Fix 5: Disable interfering Chrome extensions
Ad blockers, privacy extensions, grammar tools, and other voice or accessibility add-ons can intercept the microphone or block the script Voice typing relies on. Open the document in an Incognito window (with extensions disabled) and test. If voice typing works there, re-enable your extensions one at a time until you find the one causing the conflict.
Fix 6: Update Chrome and macOS
An outdated browser is a frequent cause of voice features silently failing. Update Chrome (Chrome menu → About Google Chrome triggers the update) and install any pending macOS updates under System Settings → General → Software Update. Restart the browser afterward.
Fix 7: Match the dictation language to your document
If recognition produces gibberish rather than nothing, the language setting may be wrong. In Google Docs Voice typing, click the language label above the microphone and set it to the language you are speaking. For Apple Dictation, set the language under System Settings → Keyboard → Dictation. A mismatch here looks like a malfunction but is really a configuration issue.
Fix 8: Restart, then test in a clean document
If several things have been toggled, restart your Mac to clear any stuck microphone session, then open a brand-new blank Google Doc and test there. A fresh document rules out an issue with one specific file (a huge document, a corrupted state, or a shared file with restricted permissions).
The honest limitation of the built-in options
Even after every fix, two annoyances tend to remain. First, Google Docs Voice typing only works inside Google Docs in Chrome — the moment you switch to Slack, Gmail's compose window, a CRM, or a different browser, you are back to fighting Apple Dictation. Second, Apple Dictation's reliability in web editors is fundamentally limited by how those editors handle text, so Docs will likely keep being the place it stumbles.
If you bounce between a Google Doc, a chat app, an email, and a project tool all day, having one voice feature that works in Chrome and a different, flaky one everywhere else is its own kind of friction. What most people actually want is a single way to talk and have text appear, wherever the cursor happens to be.
The reliable fix: type at the cursor in any app
Voice Keyboard Pro takes a different approach that sidesteps the Google Docs problem entirely. It is a native macOS app that lives in your menu bar. You hold a hotkey, speak, and release; your words are inserted at the cursor in whatever app and field you are working in — including Google Docs in Chrome, Gmail, Slack, Notion, and apps where Apple Dictation gives up.
Because it places text the same way no matter where you are, it does not depend on Google Docs being open in Chrome and it does not rely on Apple's Dictation pathway that the Docs editor blocks. A few things that make it a practical replacement here:
- One hotkey, everywhere. The same speak-and-release flow works in a doc, a comment, an email, and a chat window without changing tools.
- Smart Vocabulary. Teach it names, acronyms, and replacement rules once so it stops mangling the terms you use constantly.
- Fast and accurate. Voice Keyboard Pro's advanced AI transcription returns text in about a second, fast enough that dictating feels like typing.
- Private by design. Your transcribed text stays on your machine; the servers store only operational pings, not your audio or your words.
For a broader picture of dictating into the editors and browsers you use every day, see how to dictate in any Mac app and our overview of voice typing in Google Docs.
Frequently asked questions
Why does Apple Dictation work in Notes but not Google Docs?
Notes uses a standard macOS text field, which Apple Dictation can write into directly. Google Docs uses a custom editor that does not present a standard field, so dictated text has nowhere reliable to land. The microphone may still activate, but the text never inserts.
Does Google Docs Voice typing work in Safari?
No. Google restricts the built-in Voice typing feature to the Chrome browser. In Safari or other browsers, the Tools → Voice typing option is missing or greyed out. Switch to Chrome to use it.
Why do my dictated words appear in the wrong place in Google Docs?
This happens when the cursor is not clearly placed in the document body, or when macOS Dictation hands text to the editor and the editor re-renders the cursor position. Click directly into the document text before dictating, and prefer a tool that inserts at the active cursor reliably.
Is Google Docs Voice typing the same as Apple Dictation?
No. Apple Dictation is a system-wide macOS feature meant to work in any text field. Google Docs Voice typing is built into Google Docs and only runs in Chrome. They are separate features with separate settings and separate microphone permissions.
What is the most reliable way to dictate into Google Docs on a Mac?
If you only ever write in Google Docs in Chrome, the built-in Voice typing tool is the simplest option. If you also dictate into email, chat, and other apps, a dedicated tool like Voice Keyboard Pro that types at the cursor system-wide is more reliable because it works the same in every app, not just inside Docs.
Voice typing should not depend on which app or browser you happen to have open. Get the built-in tools working if Docs is your only writing surface, and if you want one consistent way to dictate everywhere, try Voice Keyboard Pro free and watch your words land at the cursor on the first try.