Mac dictation not working: fixes by symptom

By Techguyver28 September 2026 · 9 min read

You hold the key, you talk, and nothing appears. Or it worked yesterday and stopped today. The fix depends on which one is actually happening.

Short answer: Mac dictation usually fails for one of five reasons: it got turned off or the shortcut changed, the wrong microphone is selected, the offline language model never finished downloading, Screen Time is blocking it, or the app you are typing into cannot receive it (a terminal over SSH is the classic case). Check System Settings, Keyboard, Dictation first, since that single screen surfaces the first three.

Apple dictation is not one feature with one failure mode. It is a chain: a hotkey, a permission, a downloaded model, a network call in most cases, and an app on the other end that has to accept the text. Any link can break on its own, which is why "it stopped working" covers a dozen different actual problems.

Below is every symptom worth checking, in the order to check them, each with the fix straight from Apple's own Dictation troubleshooting page where one exists. Find your symptom, skip the rest.

Dictation does nothing when you press the key

Start here even if you are sure it is on. This is the fastest check and it catches the most common cause.

Open System Settings, Keyboard, Dictation and confirm the toggle is on.
If it is already on, turn it off, wait a few seconds, and turn it back on. This resets the dictation session and is Apple's own first suggested step.
Check the shortcut shown on that same screen. It is easy to change by accident (a modifier key remap, a conflicting app shortcut) and once it changes, the key you are used to pressing does nothing.
If the shortcut opens Siri instead of starting dictation, that is a separate key (usually the same physical key, Fn or Globe) doing double duty. Set a distinct Dictation shortcut on the same settings screen.

Still nothing? Open a Terminal window and run killall corespeechd. This restarts macOS's speech recognition process; macOS relaunches it automatically within a few seconds, and a wedged instance of it is a known cause of dictation going silent with no error.

It used to work, then stopped mid-session

Apple dictation is not always-on. Per Apple's own docs, it stops automatically after 30 seconds of no speech. If you talk in short bursts with thinking pauses between them, you will hit this constantly and it will look like the feature "gave up" rather than a timeout doing exactly what it is built to do. If what you actually want is dictation that stays listening while your hands are busy, that is a separate setup, covered in hands-free dictation on a Mac.

Keep talking, or restart it: the fastest recovery is tapping the shortcut again rather than waiting to see if it resumes on its own. It will not.
If a whole sentence vanished, that is a separate issue from the timeout: check the microphone fixes below before assuming it is the pause limit.
For long-form dictation where you pause to think, the 30-second limit is a hard ceiling in Apple's dictation, not a setting you can extend.

Dictation hears you in one app but not another

This is a permission problem, not a dictation problem. macOS grants microphone access per app, so Notes working while Chrome or Slack stays silent means the app in question never got asked, or had access revoked (often after an update).

Open System Settings, Privacy & Security, Microphone.
Find the app and make sure its toggle is on. If the app is not listed at all, it has never requested the permission, and quitting and relaunching it is usually what triggers the prompt.
Click into the app and make sure a text field actually has focus before you dictate. Apple dictation writes into the focused field; nothing is selected, nothing arrives.

Wrong microphone, or an external mic that will not work

If your Mac has no built-in microphone, or you plugged one in and dictation went quiet, this is almost always a selection or volume issue rather than dictation itself failing.

Open System Settings, Sound, Input and confirm the mic you expect is the one selected. macOS does not always default to a newly connected device.
Watch the input level meter while you talk. If it stays flat, the OS is not hearing the mic at all, which points at a connection or driver issue rather than dictation.
Per Apple's guidance, if the input volume is too low, raise it on that same Sound settings screen. A mic that is "on" but too quiet behaves identically to dictation being broken.
For Bluetooth microphones and headsets specifically, audio routing is a known extra failure point; a wired USB microphone rules that variable out if you are troubleshooting.

The language never downloaded (offline dictation)

macOS can dictate fully offline, but only after it has downloaded a language-specific model, and that download can silently fail to complete, especially over a slow or interrupted connection.

Open System Settings, Keyboard, Dictation and check the language shown matches what you are speaking.
Look for a download indicator or an option to enable offline dictation for that language. If it is stuck or was never triggered, toggling the language off and back on restarts the download.
Until that download finishes, dictation falls back to needing a live internet connection, per Apple's own note that dictation "may need an internet connection." A flaky Wi-Fi connection at that point looks exactly like dictation being broken, when the actual cause is the model never finished arriving.

It stopped working after enabling Screen Time

On a managed or family Mac, this is worth ruling out early because the fix is nowhere near the Dictation settings screen. Apple's Screen Time App & Feature Restrictions page lists Siri & Dictation as a togglable item under Content & Privacy.

Open System Settings, Screen Time, Content & Privacy, App & Feature Restrictions.
In the Allowed section, confirm Siri & Dictation is switched on.
On a company-managed Mac (MDM), the same restriction can be pushed by an IT profile, which will not show a toggle you can flip yourself. That points you at asking IT rather than more local troubleshooting.

It stopped hearing you at all, in every app

Restart the Mac. This clears whatever cached audio or speech-daemon state got stuck, and Apple lists it as a step for exactly this symptom.
Turn off Voice Control in System Settings, Accessibility if it is on. It listens on the same microphone and the two features conflict.
Turn off "Listen for Hey Siri" in Siri settings for the same reason: two always-listening features fighting for one microphone.
On an Intel Mac specifically, a persistent failure after all of the above can be an NVRAM issue, cleared by restarting and holding Option + Command + P + R at startup.

In Google Docs

Google Docs has its own dictation, called Voice typing, and it is separate software from Apple's system dictation, with its own failure modes. As of September 2026, Google's own help page states it works with the latest versions of Chrome, Edge, and Safari, so this is not Chrome-only the way it used to be.

In Docs, go to Tools, Voice typing and click the microphone icon, or use the shortcut shown there. This is a different toggle from your Mac's system Dictation and turning one on does not turn on the other.
If Docs shows "We're having trouble hearing you," Google's guidance is to move to a quieter space, check the mic is plugged in and not in use by another app, and confirm its input volume in your Mac's Sound settings.
If the Voice typing menu item is missing entirely, it may be turned off by a Google Workspace administrator at the organization level, which is a setting outside your Mac.

In Chrome

Outside of Google Docs, Chrome dictation issues are almost always the browser's own microphone permission, separate from the macOS-level one.

Click the lock or tune icon in Chrome's address bar and confirm Microphone is set to Allow for the site you are on.
Check System Settings, Privacy & Security, Microphone and confirm Chrome itself has access at the macOS level too. Both have to be granted; either one missing looks the same from inside the page.
A site using its own in-browser voice input (not Apple system dictation) depends on that site's code, not on your Mac settings, so if one site works and another does not, that is the site, not you.

In your terminal

This is the case none of the fixes above solve, and it is worth understanding why rather than assuming it is broken. Apple system dictation writes text into the macOS text field your cursor is in, using accessibility APIs that ask the field for its value and set it directly.

A terminal window running a local shell has a real text field under it, so dictation can work there. The moment you SSH into another machine, that stops being true: your command line is now a picture of a shell running somewhere else, not a macOS text field at all, and there is nothing for the accessibility API to write into. We wrote the full mechanism behind this in why dictation breaks over SSH, and what actually survives it.

The short version: any tool that delivers text as synthesized keystrokes rather than by writing into a text field works in a terminal, local or remote, because the remote shell cannot tell a keystroke from software apart from one you typed. Apple's system dictation is not built this way, which is why this is a real gap rather than a bug you can toggle away.

When it keeps failing anyway

If you have gone through the fixes above and dictation is still unreliable, that is worth taking as information rather than a personal failure to configure your Mac correctly. Apple dictation was built for short messages and quick notes, with a 30-second pause limit, per-app permissions, a language model that has to download correctly, and a text-field requirement that rules out a real terminal session. Those are all real design choices, not bugs, and they add up to a tool that is not built for someone dictating all day across a dozen different apps.

The honest alternative is a dictation tool built to paste at the system cursor as keystrokes rather than write into a text field, so the same 30-second timeout, per-app permission chase, and terminal gap stop being separate problems to solve. MightyMouse dictates into any Mac app, including a terminal, with transcription that runs free on your own machine using local Whisper, so there is no per-app permission to lose, no cloud round trip to time out, and no model download that can silently fail; the language model comes down once, on your machine, and you can see it happen.

It is not a strict upgrade in every direction. Apple's dictation is already installed and needs no setup at all, and for a two-sentence message in Notes, that is hard to beat. Where it falls short is consistency across apps, the terminal, and anything longer than a quick note, which is the specific set of problems above; see how MightyMouse compares to Apple's built-in dictation for the full breakdown, or how the other Mac dictation apps stack up if you are comparing more than one.

Dictation that works the same in every app, including your terminal.
Free local transcription. No card to try it.

Common questions

Why does dictation work in Notes but not in my terminal?

Apple dictation writes into a macOS text field. A terminal connected to another machine over SSH has no such field; it is a picture of a remote shell, so there is nothing for dictation to write into. A tool that sends keystrokes instead works in both.

Why does Mac dictation stop after a few seconds of silence?

Apple's own documentation states dictation stops automatically after 30 seconds without speech. This is a built-in limit, not a bug, and the only fix is restarting it or talking without long pauses.

Does Google Docs voice typing only work in Chrome?

No, not as of September 2026. Google's own help page lists Chrome, Edge, and Safari as supported, so a Mac using Safari can use Voice typing in Docs without switching browsers.

Can Screen Time block dictation on a Mac?

Yes. Screen Time's App & Feature Restrictions has a Siri & Dictation toggle under Content & Privacy. On a company-managed Mac, the same block can come from an MDM profile instead, which will not show as a toggle you can change yourself.

Will restarting my Mac fix dictation?

Often, yes, for the case where dictation has gone silent across every app rather than one specific app. It clears stuck audio and speech-daemon state. Running killall corespeechd in Terminal does the same thing without a full restart.

If Apple's dictation keeps timing out or skipping your terminal: MightyMouse types your words into any Mac app with free local transcription, no per-app permission chase and no 30-second cutoff.