Why Does Mac Dictation Stop After a Few Seconds?

Short answer: Mac dictation stops after a few seconds for three reasons: the classic server mode has a hard time limit near 60 seconds, streamed audio can drop on a network hiccup, and voice activity detection ends the session the moment it hears a pause. A dictation app that records continuously on-device avoids all three.

The three reasons dictation cuts out

When people search for why dictation Mac sessions keep dying, they usually assume it is a bug. It rarely is. There are three separate mechanisms, and any one of them can end your session early.

1. The 60-second server limit. Apple's classic dictation streams your voice to Apple's servers and turns it into text. That server session has historically been capped at roughly one minute. Hit the ceiling and it stops, drops your text in, and waits for you to trigger it again.

2. Network interruptions. Because that same mode depends on a live connection, any blip in your Wi-Fi can end the session. This is also why dictation sometimes feels sluggish or refuses to start on a captive network. If you want the fuller picture on connectivity, our guide on whether voice-to-text works offline on a Mac walks through what actually needs the internet.

3. Voice activity detection (VAD). Every dictation system listens for silence to decide when you are done. This is the one that catches people who dictate slowly. Pause two seconds to find the right word and the system assumes you finished the sentence, so it stops and commits the text. That is why it can feel like it stops "after a few seconds" even when there is no hard time limit at all.

Does Apple Dictation have a time limit?

Yes and no, which is exactly why this is confusing. The classic server-based mode has that practical limit near 60 seconds. If you turn on the on-device option in System Settings under Keyboard, that hard cap goes away and your Mac transcribes locally instead. But the on-device mode still uses silence detection, so it can end when you stop talking. Removing the time cap does not remove the pause cutoff.

On-device speech recognition is a big improvement for privacy as well as for length. The underlying models have become remarkably accurate, in part thanks to research like OpenAI's Whisper paper on robust speech recognition, which showed that local models can rival cloud transcription. If you want to know exactly what leaves your machine, our piece on whether Mac dictation is private breaks it down.

How the options compare

Here is how the common ways to dictate on a Mac stack up on the exact things that cause cutoffs: the time limit, whether a pause stops you, and whether audio is streamed to a server.

Method	Hard time limit	Stops on a pause	Needs network	Long-form friendly
Apple Dictation (classic server)	~60 sec	Yes	Yes	No
Apple Dictation (on-device)	None	Yes	No	Partly
Web dictation tools	Varies	Yes	Yes	No
BlaBlaType	None	No	No	Yes

The pattern is clear. Anything that streams to a server inherits both a time limit and a network dependency, and almost everything ends on silence. A tool built to record continuously on-device sidesteps all three, which is what you want when you are drafting more than a sentence at a time. If you regularly write longer text, our guide on how to dictate long documents without errors goes deeper.

How to stop dictation from timing out

If you want to keep using the built-in tool, a few habits reduce the cutoffs:

• Switch to on-device. In System Settings, enable the on-device dictation option so you are not capped by the 60-second server session.
• Keep a steady cadence. Long silent gaps trigger VAD. Speaking in continuous phrases keeps the session alive longer.
• Check your mic. A weak input signal can be read as silence. Pick the right microphone and get closer to it.
• Avoid flaky networks. If you are on the classic mode, an unstable connection will keep ending your session.

These help, but they are workarounds. You are still fighting a system that is designed to stop when you pause. The cleaner fix is a tool that never assumes a pause means you are finished.

Do this, not that

When dictation keeps cutting out, small choices decide whether you fight it all day or forget the problem exists.

Do	Do not
Use a shortcut you hold or toggle so the mic stays open on your terms.	Rely on silence to end dictation, then lose your train of thought to a cutoff.
Enable on-device transcription so there is no server clock ticking.	Dictate a long paragraph over the classic 60-second server mode.
Speak naturally, pauses included, and let AI add the punctuation after.	Force yourself to talk without breathing just to beat the timeout.
Keep your audio on your Mac for private notes and drafts.	Stream sensitive dictation to a server on an unstable connection.

A dictation flow that does not stop on you

The reason BlaBlaType does not cut out is architectural. You press one shortcut to start and the mic stays open until you press it again. There is no server session counting down and no network to drop, because speech recognition runs on your Mac with local Whisper and Parakeet models. Because it is not guessing that a pause means you are done, you can think mid-sentence and keep going.

On-device AI cleanup then removes filler, fixes punctuation and adapts tone, so a long, rambling take comes out as clean text. It works system-wide in any app or text field, handles 90+ languages, and lets you add a custom dictionary for names and jargon. It is worth remembering that most people speak around three to four times faster than they type, so removing the cutoffs is what finally lets that speed pay off. This is also handy in places the built-in tool struggles, like technical work where you might want to dictate into Terminal on a Mac. If any of the jargon here is new, our speech-to-text glossary explains terms like VAD in one line each. For keyboard-driven control fans, tools such as Talon take a different, command-focused approach. You can compare plans on the pricing page.