You start dictating a report, you pause to think about the next sentence, and when you start talking again nothing appears. The microphone icon is gone. You press the shortcut, carry on, and two paragraphs later it happens again.
Most people conclude that Mac dictation has a 30-second time limit. It doesn’t, quite, and the difference matters, because the fix depends on which limit you are actually hitting.
This guide is only about length: why dictation sessions end before you do, and how to dictate a 2,000-word document anyway. If dictation won’t start at all, see Mac dictation not working? 9 fixes instead.
The short version
- There is no length cap on modern Macs. Apple’s own documentation says you can “dictate text of any length without a timeout” on Apple silicon.
- There is a silence cap. Dictation stops automatically when no speech is detected for 30 seconds. That is the “30-second limit” almost everyone is hitting: not 30 seconds of talking, but 30 seconds of not talking.
- Other things also end a session: clicking or switching to another window, changing microphones mid-dictation, and on Intel Macs, typing while you speak.
- Older and Intel Macs are different. Before on-device dictation, Apple’s guidance was to speak “no more than 40 seconds at a time”, and Intel Macs still send dictation to Apple’s servers.
- For long documents, change the workflow, not just the settings: outline first, dictate one section per session, keep a “parking” phrase for when you need to think, and edit only at the end.
What Apple actually says
Apple’s Mac User Guide is unusually clear on this, and the wording has been stable since macOS Monterey through the current release:
- On a Mac with Apple silicon, general text dictation is processed on the device for many languages, with no internet connection required.
- You can dictate text of any length without a timeout.
- Dictation stops automatically when no speech is detected for 30 seconds.
So the session itself is unlimited, but it has a dead-man’s switch. As long as you keep producing speech, it keeps going. Stop for half a minute, and it ends.
That explains the pattern most people describe: dictation works perfectly for short messages, then “randomly” dies during long documents. Long documents are exactly where you stop to think, re-read the previous paragraph, check a figure in another window, or answer a colleague. Short messages almost never contain a 30-second pause.
The older 40-second guidance
If you are on an older version of macOS, the documentation for Catalina (10.15) gives a different instruction: for best results, speak for no more than 40 seconds at a time. That reflects the older, server-based model, where each utterance was sent to Apple for processing and long requests degraded or were cut off.
Apple’s “any length” sentence is written for Apple silicon. Intel Macs running recent macOS still send dictation to Apple’s servers, and Apple does not make the same no-timeout promise for them. If you are on an Intel Mac and sessions end after a fixed stretch of continuous talking, even without pauses, you are most likely hitting that older server-side behaviour, and the workflow below (short sections, deliberate restarts) is your main remedy.
The six things that end a dictation session
Before changing anything, identify which of these is happening. Watch the microphone indicator when the session dies and note what you were doing.
1. You paused for 30 seconds
The most common cause by far. Thinking pauses in long-form writing are often longer than they feel: re-reading a paragraph, finding a statistic, deciding how to structure the next section. Thirty seconds passes quickly.
What helps: keep a “parking” habit. When you need to think, say a placeholder you will delete later, such as “note to self, check the Q3 number here”, rather than going silent. Or simply accept that thinking ends the session and restart deliberately with the shortcut when you are ready. The second option is cleaner; the first is useful when you are in flow and don’t want to break it.
2. You clicked somewhere else
Dictation inserts text into the field that has focus. Click into another window to look something up, switch apps with Command-Tab, or let a notification steal focus, and the session typically ends because the text field it was writing into is no longer active.
What helps: do your research before a dictation section, not during it. Put reference material on a second screen or in a printout so you can read it without clicking. Turn on a Focus mode so notifications don’t grab the window mid-sentence.
3. You changed microphones
Connecting or disconnecting AirPods, a headset or a USB microphone mid-session changes the input device, and dictation tends to end or go silent when the device it was listening to disappears. Bluetooth headsets that drop and reconnect are a frequent hidden cause of “random” cut-offs.
What helps: pick one microphone for long dictation and stick to it. A wired or USB microphone removes the Bluetooth reconnection problem entirely. In System Settings, set the dictation microphone explicitly rather than leaving it on “Automatic”.
4. You typed while dictating (Intel Macs)
On a Mac with Apple silicon, Apple says you can use the keyboard while you speak without stopping dictation. On Intel Macs, typing a key generally ends the session. If you habitually fix a word with the keyboard mid-sentence, that is your cut-off.
What helps: on Intel, don’t touch the keyboard during a section. Fix everything in a dedicated editing pass afterwards (see the workflow below).
5. The app doesn’t support continuous dictation well
Some web apps and text fields handle inserted text poorly: rich editors in browsers, fields that reformat as you type, or apps that refresh their content periodically. The session may end or text may land in the wrong place.
What helps: dictate long drafts into a simple, native editor (Notes, TextEdit, Pages, or your word processor’s desktop app), then paste into the final destination.
6. You are on an older Mac or older macOS
Covered above: Catalina-era guidance was 40 seconds per utterance, and Intel Macs remain server-dependent. If none of the first five causes fits and you are on Intel, this is the likely explanation.
A workflow for dictating long documents
Getting a 2,000-word report out of your mouth and onto the page is less about beating the timer and more about structuring the work so the timer stops mattering. This is the approach that holds up with any dictation tool.
Step 1: Outline before you speak
Write (or dictate) a bullet outline first: section headings and two or three points under each. This is the single biggest improvement for long dictation, because almost all of the long pauses that kill sessions are structural ones: “what comes next?” With an outline, you never have to decide that mid-sentence.
Step 2: One section per session
Treat each section as its own dictation session. Look at the outline, start dictation, speak the section through from start to finish, stop. Then read your next bullet points and start again.
Sessions of two to five minutes are the sweet spot. They are long enough to keep a natural flow and short enough that a 30-second pause rarely happens inside one. They also limit the damage when something does cut you off: you lose a sentence, not a page.
Step 3: Speak in complete paragraphs
Spoken drafting goes wrong when people dictate the way they type, a few words at a time with long gaps between. Instead, say a whole paragraph as you would explain it to a colleague across the table. The text will be wordier than your typed prose, which is fine at this stage.
Step 4: Don’t edit while you dictate
Every correction during dictation is a pause, a click or a keystroke, which are three of the six session killers. Leave errors in. Mark doubtful spots verbally (“check this”, “rephrase”) if you want to find them later.
Step 5: Edit in one pass at the end
Once the whole draft exists, switch to the keyboard and edit everything together: fix transcription errors, tighten wordy sentences, sort out punctuation and paragraph breaks. Editing a complete draft is much faster than editing fragments, and it is the stage where typing genuinely beats talking.
Step 6: Save often
Long dictation sessions in an unsaved document are a bad combination. If the app crashes or you accidentally select and overwrite text, you lose more than a timeout ever cost you. Save after every section.
Settings worth checking
These won’t remove the silence timeout, but they remove a few avoidable cut-offs:
- Set the microphone explicitly in System Settings > Keyboard > Dictation, instead of Automatic.
- Use a Focus mode while writing so notifications don’t take focus.
- Check the language. If the dictation language doesn’t match what you speak, recognition gets patchy, and the “pause” between recognised words can stretch long enough to look like silence.
- Keep macOS up to date on Apple silicon so you get on-device dictation, which is where the “any length” behaviour applies.
When Voice Control is the better built-in option
If what you actually need is a microphone that stays on for an hour, macOS has a second built-in system: Voice Control (System Settings > Accessibility > Voice Control). It is designed for people who operate the whole Mac by voice, so it stays listening until you turn it off or tell it to go to sleep, rather than ending after a silence.
The trade-offs are real. Voice Control is command-oriented, has a steeper learning curve, and expects you to dictate punctuation and formatting by voice. It is a strong option for accessibility needs such as RSI, and an awkward one if you just want to write a report faster. Try it for a day before committing.
How Dikto handles long dictation
Dikto approaches length differently, and it is worth being precise about what is and isn’t different.
What’s different:
- No session time limit and no silence timeout. Dikto records until you press your shortcut again. A long pause to think doesn’t end the session; you can stop talking for a minute, re-read your outline, and carry on.
- It splits at your pauses, not at a timer. While you speak, Dikto cuts the audio into segments at natural pauses and transcribes each one while you keep talking, so a long session doesn’t arrive as one huge block at the end. If a segment runs past about a minute without a pause, it is split at the next brief gap rather than in the middle of a phrase. The pause length used for splitting is adjustable in the advanced dictation settings (Silence Gap).
- A dropped connection doesn’t lose your words. If a segment can’t be sent because the network drops mid-session, it is kept and retried, rather than silently vanishing.
- Cleanup happens on the whole thing. Dikto removes hesitations, fixes punctuation and formats the text, so the editing pass in step 5 is shorter. You don’t have to say “comma” or “new paragraph”.
What’s the same, or worse:
- Changing microphones still ends a session. If your input device changes mid-recording, Dikto stops, shows a notice, and delivers what it already captured. Pick one microphone, as above.
- Dikto is cloud-only. There is no offline mode: audio is sent to our backend and then to the selected AI provider for transcription. Apple’s on-device dictation works without a connection; Dikto doesn’t. Check our privacy policy and your organisation’s rules before dictating anything sensitive.
- The free plan is the real limit for long documents. For the first 7 days you get 60 minutes of dictation a day. After that, the free plan is 15 minutes (about 2,000 words) a week, which a single long report can use up. Pro (€9/month or €89/year) has unlimited dictation. If you are on the free plan, check your remaining minutes on your account page before starting a big document.
The outline-first, section-by-section workflow still helps with Dikto, but for a different reason: not to beat a timer, but because structured speech produces a better first draft.
Frequently asked questions
Is there a time limit on Mac dictation? Not on Apple silicon Macs. Apple says you can dictate text of any length without a timeout. What does exist is a 30-second silence timeout: if no speech is detected for 30 seconds, dictation stops.
Can I turn off the 30-second silence timeout? There is no setting for it in Keyboard > Dictation. Your options are to avoid long silences within a session, restart deliberately when you are ready, use Voice Control (which stays listening until you turn it off), or use a third-party tool without a silence timeout.
Why does dictation stop when I’ve only been talking for a few seconds? That is almost never the timer. Check whether you clicked another window, whether a notification took focus, whether your Bluetooth headset reconnected, or, on an Intel Mac, whether you pressed a key.
Why does my Intel Mac cut off long dictation even without pauses? Apple’s “any length” guarantee is written for Apple silicon, where dictation runs on the device. Intel Macs send dictation to Apple’s servers, and Apple’s older guidance was to speak for no more than 40 seconds at a time. Short, deliberate sections are the most reliable approach on Intel.
What is the fastest way to dictate a long document on a Mac? Outline first, dictate one section per session, speak in full paragraphs, don’t correct as you go, and do a single editing pass at the end. The workflow matters more than the tool.
Bottom line
Mac dictation doesn’t have a 30-second limit on how long you can talk. It has a 30-second limit on how long you can stay quiet, plus a handful of other triggers (focus changes, microphone changes, typing on Intel) that end a session without warning. Fix the trigger you are actually hitting, structure long writing as an outline dictated in sections, and the cut-offs stop costing you more than a sentence.
If you want a session that keeps listening while you think, and text that arrives cleaned up rather than raw, you can try Dikto for free, with no credit card. For a broader look at the built-in tool, see our complete guide to voice dictation on macOS and the Dikto vs Apple Dictation comparison.