Short answer: Mac dictation usually stops because of a built-in silence timeout: pause for a few seconds while thinking and the session ends itself. Other common causes are a Bluetooth mic dropping to call mode, an app stealing focus, sleep settings, and a Voice Control conflict.
You start a sentence, stop to think about how to phrase the next clause, and the microphone indicator vanishes. Or you dictate a paragraph and it quits halfway through, mid-word, for no reason you can see. Either way you end up doing the one thing dictation was supposed to eliminate: reaching back for the keyboard every twenty seconds.
"Mac dictation keeps stopping" is really three different complaints wearing the same shirt, and the fix depends on which one you have. Before changing any settings, spend thirty seconds classifying your version of the problem. It saves you from working through eight irrelevant fixes.
First, figure out which kind of stopping you have
Watch what happens the next two or three times it quits and match it against these:
- It stops when you pause. You are mid-thought, you go quiet for a couple of seconds, and the session ends. Text already dictated stays put. This is the silence timeout and it is by far the most common case.
- It stops after a fixed stretch of time regardless of whether you are still talking, often somewhere around the minute mark on longer passages. This points at a session length limit or a resource issue rather than at you.
- It stops randomly, mid-word, sometimes seconds after starting. Text may be truncated or garbled at the cut. This is almost always the audio input path: a Bluetooth device switching modes, a device disconnecting, or another app grabbing the mic.
A related but distinct symptom is dictation that stays on but drops the middle of what you said. That is a truncation problem, not a stopping problem, and it has its own causes worth reading about in our guide to Mac dictation cutting off mid-sentence.
Now work through the fixes below in order. They are sorted by how often they turn out to be the answer, not by how technical they are.
1. Understand the silence timeout before you fight it
Built-in dictation on the Mac is designed as a short-burst tool. It listens, and when it hears nothing for a few seconds it assumes you are finished and closes the session so the microphone is not left running. That behaviour is not a bug and there is no setting to extend it.
This is why the problem feels so much worse when you are writing something hard. Dictating a text message to a friend involves almost no pausing. Dictating a performance review, a legal paragraph, or a technical explanation involves a lot of pausing, because you are composing rather than transcribing. The harder the writing, the more the timeout fires.
There are only two real responses. The first is to change how you speak: draft the sentence silently in your head, then say the whole thing in one continuous pass. It works, and it is a genuinely useful habit, but it fights against how most people think while writing.
The second is to use a tool where you control the session boundaries instead of a timer. That is the model Voice Keyboard Pro uses on the Mac: you hold a hotkey while you speak and release it when you are done. Silence in the middle of the hold is just silence. Pause for ten seconds to find the right word and nothing closes, because nothing is guessing at your intent. The session ends when your thumb says it ends.
2. Check whether you are on a Bluetooth microphone
If the stopping is random rather than pause-related, suspect the audio path first, and suspect Bluetooth above everything else.
When a Bluetooth headset switches from playback mode to microphone mode, it drops to a much lower-quality hands-free audio profile. On some devices that switch is not clean. The input stream stutters or briefly disappears, and dictation interprets the gap as either silence or a device change and closes the session. AirPods are especially prone to this when they are also connected to an iPhone that might steal them back mid-sentence.
The test takes fifteen seconds. Open System Settings → Sound → Input, select the Mac's built-in microphone, and dictate the same passage again. If the stopping goes away, your headset was the cause. Options from there:
- Use wired earbuds with a mic instead. A cheap wired set will out-perform an expensive Bluetooth one for dictation because it skips the codec downgrade entirely.
- Turn off Bluetooth on your iPhone while dictating on the Mac, so the headset cannot be pulled away.
- Keep the Bluetooth headset for calls and use the built-in mic for dictation. At a quiet desk the built-in mic is genuinely good, as we covered in the guide to choosing a microphone for dictation.
3. Rule out another app holding the microphone
Only so many things can use the input device at once, and macOS does not always resolve the contest gracefully. If you have a video call app running in the background, a recording tool minimised, or a meeting client that grabs the mic when a scheduled event starts, dictation can be shut out mid-session.
Quit rather than minimise: video conferencing apps, screen recorders, audio interfaces and their control software, and anything that shows a microphone indicator in the menu bar. Then look at the orange dot macOS shows in the menu bar when the mic is live, and click the Control Center icon to see which app is listed as using it. If something other than the app you are dictating into appears there, that is your culprit.
This is also the most likely explanation for dictation that fails only at certain times of day. If your calendar app auto-launches a meeting client at the top of the hour, dictation will keep dying at the top of the hour.
4. Check for a Voice Control conflict
Voice Control and dictation are separate features that both want the microphone and both want to interpret your speech. Running them at the same time produces exactly the symptoms in this article: sessions that end without warning, commands firing when you meant to dictate words, and text that stops appearing partway through.
Go to System Settings → Accessibility → Voice Control and confirm it is off unless you deliberately rely on it. If you do use Voice Control for navigation, treat the two as alternating modes rather than concurrent ones. Turn one off before using the other.
5. Re-download the speech assets
Dictation depends on downloaded language assets. A partial or corrupted download produces flaky behaviour that looks like hardware failure: recognition works for a few words, then the session collapses.
The clean reset is to remove and re-add the language. In System Settings → Keyboard → Dictation, open the language menu, remove your current language, restart the Mac, then add it back and let the download finish completely before testing. Do this on a stable connection and give it a few minutes; the download is not small, and interrupting it is what causes the problem in the first place.
While you are on that screen, check that the selected language variant matches how you actually speak. A mismatch between, say, English (US) and English (UK) does not usually stop a session outright, but it degrades recognition enough that the system may treat your speech as noise.
6. Look at sleep, Low Power Mode, and lid behaviour
If dictation dies after long silences that are not really silences on your end, energy settings deserve a look. A Mac that dims and sleeps aggressively will close a dictation session on the way down. Low Power Mode also throttles background activity in ways that can interrupt continuous audio processing.
Open System Settings → Battery (or Energy Saver on a desktop) and, at least temporarily, lengthen the display sleep interval and turn off Low Power Mode. Then reproduce the problem. If dictation now survives, you have your answer, and you can decide whether to keep the setting changed or simply keep the display awake during long dictation sessions.
The same applies to using a MacBook in clamshell mode with an external display. Anything that causes the display configuration to change mid-session, including a monitor waking or a dock renegotiating, can knock the session over.
7. Test in a neutral app to isolate the variable
This one fixes nothing by itself but it saves hours. Open TextEdit, create a blank document, and dictate the same paragraph you were dictating when it failed.
If dictation runs fine in TextEdit and dies in your real target app, the problem is the app, not the system. Browser-based editors, Electron apps, and anything with heavy JavaScript-driven text handling are the usual suspects: they intercept keystrokes, rewrite the field contents as you go, or move focus out from under the cursor. Rich text editors that autosave frequently can pull focus at the moment of the save.
If dictation dies in TextEdit too, it is system-level and you should keep working through this list.
The narrower version of this test is worth running as well: does it fail in one specific field, such as a search box or a comment box, and work in the main document body of the same app? If so, the field itself is the problem, and the practical workaround is to compose in a plain document and paste across.
8. Deal with background noise, which ends sessions two ways
Noise is an underrated cause of stopping, and it works through two separate mechanisms.
First, if the room is noisy enough, the system may never register a clean silence boundary, so it keeps trying to interpret ambient sound as speech and produces garbage until it gives up. Second, and more common in open offices, other people's speech competes directly with yours. Steady noise like a fan or air conditioning is comparatively easy for a recognition engine to ignore; nearby conversation is not, because it has all the same acoustic properties as the thing the system is trying to transcribe.
The single most effective change costs nothing: get closer to the microphone. Sound intensity falls off sharply with distance, so halving the gap between your mouth and the mic meaningfully improves the ratio of your voice to everything else. That beats most hardware upgrades. Our full write-up on fixing dictation in a noisy environment goes through the per-environment specifics.
9. Restart properly, then check for updates
Leave this to last, because it is the fix that gets recommended first everywhere else and it rarely explains a persistent problem. Still, an audio daemon in a bad state does produce exactly these symptoms, and a full restart clears it. Restart, do not just log out, and do not just close the lid.
Then check System Settings → General → Software Update. Speech and audio subsystems get fixed in point releases, and running several versions behind on a machine that used to work fine is worth ruling out.
What to do when none of it holds
Here is the uncomfortable part. If your version of the problem is the silence timeout, everything above is a workaround rather than a fix, because the timeout is the intended design. Built-in dictation was built for short bursts: a reply, a search query, a note. It closes the session when you stop talking because leaving a microphone open indefinitely would be the wrong default for a system feature.
That design is a poor match for composing. Writing at length is not a continuous stream of speech, it is speech with thinking in the gaps, and a tool that treats every gap as an ending will interrupt you at exactly the moments you least want to be interrupted.
The problem is not that dictation stops. It is that something other than you decides when it stops.
The alternative is push-to-talk. With Voice Keyboard Pro on the Mac you hold a hotkey, speak for as long as you need, and release. Text appears at your cursor in whatever app you are in, system-wide, no per-app setup. Silence inside the hold is just you thinking. There is no timer waiting for an excuse to close the session, so a ten-second pause in the middle of a difficult sentence costs you nothing.
Two other things tend to matter once the stopping problem is out of the way. Smart Vocabulary lets you build a personal dictionary with replacement rules, so recurring proper nouns, client names, and jargon come out right instead of being re-guessed every time. And Meeting Mode handles the longest-form case of all, with speaker detection and AI notes, which is a different job from dictating into a text field but suffers from the same session-length constraints when you try to do it with a burst-oriented tool.
On privacy: audio is processed for transcription and the server keeps only operational pings. No audio and no transcript content is stored server-side. If you are dictating client work or anything sensitive, that boundary is worth knowing before you pick any dictation tool, including this one.
Quick reference
If you only have five minutes, run these in order:
- Switch input to the built-in microphone and retest.
- Quit every app that could be holding the mic, then check the Control Center mic indicator.
- Turn Voice Control off.
- Test the same passage in TextEdit to isolate app versus system.
- Turn off Low Power Mode and lengthen display sleep.
- Remove and re-add your dictation language, then restart.
If the answer to all six is "still stops when I pause," you have not found a bug. You have found the design ceiling, and the way past it is a tool that hands the on-off decision back to you. Voice Keyboard Pro has a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year if you end up using it every day. Try dictating one difficult paragraph, with all the pauses you normally take, and see whether it survives to the end.
The same push-to-talk logic applies on iPhone through the Voice Keyboard Pro keyboard, which has a built-in mic button that works in any iOS app, plus Voice Edit for speaking a correction instead of tapping at it. If your stopping problem follows you across devices, the guide to iPhone dictation that keeps stopping covers the mobile side of the same story. And if your Mac sessions survive but feel sluggish, Mac dictation running slow is the companion piece to this one.