Why Apple Dictation stops after 30 seconds

Search for this and you get two kinds of page. One tells you to toggle a setting. The other tells you to buy something. Neither explains why a dictation session has a length in the first place, which is the part that tells you whether the toggle will help you.

The setting

Open System Settings, go to Keyboard, then Dictation. There is an option that ends dictation automatically when it decides you have stopped talking. Turn it off. The label has been renamed across macOS releases, so if the wording on your Mac does not match, look for the switch about ending dictation, and check Apple’s own dictation page for your version.

For a lot of people that is the whole fix and the rest of this is unnecessary.

Why the length exists at all

It is worth understanding, because it explains why the fix is partial.

A dictation session has to end somehow. The system cannot know whether the pause after a comma means you are thinking, checking a figure, or finished, so it picks a rule based on silence and applies it to everyone. Any rule chosen centrally will be wrong for somebody, and it is reliably wrong for the same people: those who speak in long sentences, who read from a document, or who pause to look something up.

Speech recognition on a phone inherited this, because a phone assistant genuinely does need to know when your request has ended. Dictation on a desktop does not, but it grew out of the same machinery.

The two things that override the setting

If you turned it off and it still stops, the cause is one of these.

The microphone changed. A session ends when its input disappears. That happens more often than people expect: a headset switching between its call profile and its music profile, a video app taking exclusive use of the microphone, a dock being unplugged, a Bluetooth device reconnecting and quietly becoming the default input. From the outside it is indistinguishable from a timeout. Open Sound in System Settings, check which input is selected, and try again with the suspect device disconnected.

It is running on a server. On Apple silicon, Apple states that dictation runs on device. On older hardware, and for some languages, it goes to Apple’s servers instead. A round trip to a server having a bad minute produces exactly the symptom people describe as a cut off: it works, then it stops, then it works later and you never find out why. There is no setting that fixes a network.

The other approach

Let the person decide. That is how Zumbo works: you hold your shortcut and it listens until you let go, or tap to start and tap again to stop. There is no session length, no silence detector ending things early and nothing to configure. A long paragraph is one press, and you can pause to think without it concluding you are done.

The shortcut is whichever key you choose in Settings, and you can change it whenever you want.

The transactional version of this, with the steps in order, is the fix page. The broader comparison is Zumbo against Apple Dictation.

12:04

10:32Speaker 1We are holding the release until the migration lands.

10:33Speaker 2Then the changelog goes out Thursday, not Tuesday.

10:33Speaker 1Agreed. I will move the announcement.