Mac dictation keeps stopping

Why Mac dictation keeps stopping mid-sentence

There are a handful of causes, and only some of them are yours to fix. The first is the one almost everyone hits: macOS Dictation ends the session after a stretch of silence. Apple's support page states it plainly — Dictation "stops automatically when no speech is detected for 30 seconds." That's not a fault on your machine. It's the feature deciding that a long enough pause means you've finished. A beat to think, a glance at a reference, a sip of coffee — any of those can cross the line.

The second cause catches people off guard: Voice Control. That's a separate macOS accessibility feature (System Settings > Accessibility > Voice Control) for steering your Mac entirely by voice. When Voice Control is on, keyboard Dictation is disabled — the two are mutually exclusive in current macOS, and Apple's own settings warn you when one turns the other off. So if you (or someone) ever switched Voice Control on, your normal Dictation shortcut may do nothing, or behave erratically. The third cause is the language model. On Apple Silicon, general dictation can run on-device once the speech model for your language has downloaded; a model that started downloading and never finished, or got corrupted by an interrupted update, leaves Dictation flaky. The fourth is the background speech process — corespeechd, the daemon that handles Dictation, Siri, and Voice Control. If it stalls, the features it feeds stall with it.

Worth saying out loud, because it saves you an afternoon: if your microphone works fine on a call, this is almost never broken hardware. A loose USB mic or a low input level can read as silence and trip the 30-second timeout, so it's worth checking — but the stop is usually upstream, in how Dictation decides a session is over. That's also why the fixes below split into two buckets: the ones that genuinely help (disable unused Voice Control, re-download the language, restart the daemon, check the mic) and the one limitation you simply can't remove, which is the by-design silence timeout.

The fast fix that works for most people

You can't delete the 30-second timeout, but you can clear the things that make Dictation quit unpredictably, and you can avoid tripping the timer for one long passage. Here's the order I'd run it, all reversible, none of it touching system files:

First, toggle Dictation off and on — go to System Settings, Keyboard, scroll to Dictation, turn it off, wait a few seconds, turn it back on. This is the single most reported fix, and it nudges the speech stack to start fresh. Second, check Voice Control: open System Settings, Accessibility, Voice Control, and if it's on and you don't use it, turn it off, since it disables keyboard Dictation while it's running. Third, if it's still cutting out, reboot — a restart clears the speech daemon completely, which a toggle alone sometimes can't. And while you're dictating, don't go fully silent for more than a few seconds at a stretch, because that silence is exactly what ends the session; keep a steady flow and finish the thought before you pause. When those line up, a single uninterrupted burst usually holds for as long as you keep talking.

That's the remediation that gets you through the immediate task. The overlay above is from a different tool — a system-wide dictation app — and it's here to make one contrast. A hold-to-talk recorder is on for exactly as long as you hold the key, silence or not. There's no countdown running every time you pause to think, because it never decided on its own that you were finished, and it doesn't fight Voice Control for the microphone. If you're losing the same fight every single day, the durable answer in the next section is a tool that doesn't auto-stop in the first place.

The permanent fix: dictation that doesn't auto-stop

If you dictate long passages and you're tired of macOS Dictation quitting on you every half minute, the durable fix is a tool with a different on/off model. A hold-to-talk hotkey stays recording for as long as you hold it — through pauses, through thinking, through reaching for your coffee — and a local engine transcribes on your own machine, so there's no silence timer to trip and no Apple speech daemon in the loop to stall. You need a Mac on Apple Silicon and a working microphone. Here's the four-step setup with Whisper.

The only slow part is the one-time model download. After that the recording stays on while you hold the keys, and the transcription happens on your Mac, so the two things that kept stopping built-in Dictation — a silence timer and a shared speech daemon — simply aren't in the design. Hold, talk, pause, keep talking, release. That's the whole loop. And because it doesn't run through Apple's Dictation stack, it never collides with Voice Control either.

If you'd rather repair built-in Dictation

Plenty of people just want macOS Dictation to behave and don't want another app. Fair. Here's the deeper, feature-by-feature troubleshooting, in the order I'd try it, all from Apple's own support pages and community threads. None of this deletes a system file, so there's nothing here that can break your Mac — and I'll flag the one limitation you genuinely can't fix. Start by confirming the basics: open System Settings, Keyboard, Dictation, make sure it's on, and that the right language and dialect is selected under the Languages list.

Next, rule out Voice Control, because it's the cause people miss. Open System Settings, Accessibility, Voice Control; if it's on and you don't rely on it, turn it off, since it disables keyboard Dictation while active. Then re-download the language model, which is the classic fix for flaky Dictation. In System Settings, Keyboard, Dictation, click Edit next to Languages, remove the language you use, then add it back so macOS fetches a fresh copy — on Apple Silicon, general dictation runs on-device once that model is downloaded, and a corrupt or half-finished model is exactly what leaves it stalling. While you're checking, make sure your microphone is right: under System Settings, Sound, Input, select the correct input and confirm the level is high enough, since Apple's own guidance notes a mic that's obstructed, too quiet, or in a noisy room can make Dictation misbehave, and suggests a headset microphone if a built-in one keeps dropping.

If it's still stalling, restart the speech daemon. Open Activity Monitor (in Applications, Utilities), find corespeechd, select it, click the stop button, and choose Quit — it relaunches itself within seconds, which is expected, since it's a background daemon that's supposed to restart. If you'd rather use Terminal, killall corespeechd does the same thing and the process comes straight back. A reboot accomplishes the same reset if you'd prefer not to touch either. Keep macOS updated too, because some of these glitches trace to a botched update that a later point release fixes. Now the honest part: none of these removes the 30-second silence timeout. That one is intentional — Apple documents it as how the feature works, and there's no setting to disable it. Until you stop going silent mid-dictation, it will keep ending the session. If that's the dealbreaker, a hold-to-talk tool is the only real escape, which is the whole point of the section above. And I'd skip any guide that tells you to delete files out of the system Library to "reset" speech; that's how a misbehaving feature becomes a broken Mac.

Local or cloud: which mode actually avoids this

If the reason you're here is a feature that quits the moment you pause or collides with Voice Control, the answer leans local. Both local engines run entirely on your machine and don't touch Apple's speech stack, so there's no 30-second timer and no daemon to share. Here's how the three paths the app makes you choose between differ for this specific problem.

The app makes you pick, so here's how I'd think about it when the complaint is "it keeps stopping":

• Local Parakeet — NVIDIA's TDT engine, around 600 MB, and the fastest local option — 5 to 10 times faster than Whisper on CPU. Covers English plus 24 other European languages, 25 in total. No translate-to-English. Fully offline, so nothing routes through macOS Dictation or its timeout. If you speak English or a European language, this is the quickest way off the stop-start treadmill.
• Local Whisper — slower than Parakeet on the same Mac, but the multilingual builds cover 99 languages and can translate to English. The English-only builds are English-only, not 99. Pick this for Chinese, Japanese, Korean, or any translation work, which Parakeet can't do. Default English model is around 480 MB. Also fully offline.
• Cloud (OpenAI, BYOK) — best accuracy and web access, using your own OpenAI key billed straight by OpenAI. Transcription runs on gpt-4o-mini-transcribe by default. It needs internet, so it leaves your machine — but it still doesn't depend on macOS Dictation, so no 30-second cutoff. The Cloud surface is part of Whisper Pro.

The boring truth is that for the specific frustration that brought you here, local is the actual cure. A 30-second silence timer can't stop a recording that stays on while you hold a key, and a tool with its own engine never wrestles Voice Control for the microphone. Cloud earns its place when you want top-tier accuracy on a hard recording or a fact pulled off the web mid-sentence. But if your whole complaint is "it stops when I pause to think," the local route removes the cause instead of working around it. Start local.

Cleaner text once dictation stops cutting out

Once dictation actually runs end to end — built-in or otherwise — you hit the next reality: raw speech comes out as a run-on. You say "okay so reply to the landlord confirm the viewing saturday and ask about parking," and that's the unpunctuated wall any speech engine hands you. Cleaning it up is where tools differ.

macOS Dictation handles basic punctuation when you say "comma" or "period" out loud. For heavier cleanup — stripping the "ums," fixing the run-ons, turning a spoken paragraph into something you'd actually send — Whisper can run an AI pass before the text lands. Say the activation phrase "Hey whisper" and the text gets enhanced first. On a local model that runs through Ollama; in cloud mode it's gpt-5-mini by default.

The cleanup step is part of why a dedicated tool earns its keep beyond just not stopping on you. You're not only getting capture that holds through your pauses; you're getting text that's closer to done. If you want the broader version of this, the same speak-then-clean flow is what lets you type faster with voice across every app you open, not just whichever field macOS Dictation happened to land in before it timed out.

And because it pastes at the cursor in any field and never auto-stops, the same flow holds where you'd reach for built-in Dictation most — dictating into Apple Notes behaves the same as dictating into Mail or a browser tab, with no 30-second cutoff to break your train of thought.

When the built-in one is enough

Here's the part where I talk you out of installing anything. If you dictate in short bursts and the 30-second timeout never gets in your way, you don't need another app. A sentence or two before the silence timer kicks in is exactly what macOS Dictation is built for. It's free, built into your Mac, and on Apple Silicon it can run on-device once the language model is downloaded. I'm not going to tell you to install software to dictate a two-line message.

The built-in route is the right call when a few things are true: you dictate short text, you don't pause much mid-sentence, you're not running Voice Control, and your language model has finished downloading. If a glitch was a one-off and the toggle-and-reboot fix made it behave, that's your answer — don't go hunting for a second tool. The fork is really about length and rhythm. Below a sentence or two, the built-in feature is plenty. Past that, the 30-second timeout starts deciding for you.

Reach for a hold-to-talk, offline tool when the stopping starts hurting on repeat: you dictate long passages and keep hitting the silence timeout, you need Voice Control on for something and can't run Dictation alongside it, or you'd rather your dictation never route through the OS speech stack at all. Below that bar, use what's free — the workarounds earlier in this guide are there precisely so you can.

If the problem is bigger than stopping — Dictation typing nothing at all, no microphone icon, or the wrong language coming out — the wider checklist in voice to text not working on Mac covers the rest of the failure modes that aren't strictly an auto-stop.

Apple built a dictation feature that decides you're finished the moment you stop to think for half a minute, then documented that as on purpose with no way to switch it off. So we keep talking through every pause like we're afraid the line will drop, and we quietly turn off Voice Control because the two were never allowed in the room at the same time. It mostly works, for short bursts. But the first time a feature quits in the middle of your sentence because you paused to find a word, you start wanting one that waits for you. I dictated most of this guide holding two keys, pausing whenever I felt like it. It never once gave up on me.