Short answer: Mac dictation deletes text you already dictated because macOS treats each session as a live, replaceable block and re-renders the last phrase when you resume, overwriting nearby words. Deselect text first, dictate in short bursts, or use an app that inserts each phrase as final.
You dictate a sentence. It looks perfect. You pause to think, start speaking again, and watch in disbelief as the words you just dictated vanish and get replaced by your new sentence. Or worse: half of the previous paragraph disappears entirely. If Mac dictation keeps deleting text you already dictated, you are not imagining it, and you did not do anything wrong. It is a side effect of how Apple's built-in Dictation was designed to work.
This guide explains exactly why macOS overwrites text mid-dictation, walks through nine fixes that stop it, and shows you the one approach that sidesteps the problem completely. Most people can solve this in two minutes once they understand the mechanism.
Why Mac Dictation Deletes Text You Already Dictated
To fix the problem, it helps to understand what is actually happening under the hood. Apple's Dictation does not insert your words the way a person typing would. It maintains a live, editable buffer of your current utterance and continuously rewrites that buffer as it processes more audio. This is the same behavior that lets dictation correct "their" to "there" a half-second after you say it. The buffer is a feature. The deletion is the cost.
Here are the specific situations where that buffer turns destructive.
1. Resuming after a pause re-renders the last phrase
When you stop talking and then start again within the same dictation session, macOS sometimes treats the new audio as a continuation of the previous utterance rather than a fresh one. It re-evaluates the whole phrase, and if its second-pass interpretation is shorter than the first, the difference gets deleted from your document. You said two sentences, it kept one, and the cursor ate the rest.
2. Selected text gets overwritten
Dictation always replaces the current selection, exactly like typing does. If any text is highlighted when you trigger dictation, including text the previous dictation pass auto-selected as a "correction candidate," your spoken words wipe it out. This is the single most common cause of the "it deleted my paragraph" complaint.
3. The interim-results overwrite
While you speak, dictation shows tentative words and then finalizes them. In rich text fields and some web editors, the transition from tentative to final does not happen cleanly. The editor and the dictation engine disagree about where the cursor is, and the finalize step deletes a chunk of already-committed text in the process.
4. Autocorrect and Text Replacement collisions
If you have Text Replacement entries or aggressive autocorrect, the system may select a previously dictated word to "fix" it and then replace a wider span than intended. The replacement reaches backward into text you considered done.
5. Non-standard text fields
Browsers, Electron apps, and custom editors do not implement Apple's text input protocol perfectly. When dictation tries to update its buffer inside one of these fields, the field can drop or misplace the edit, deleting characters around the insertion point. This overlaps with a related issue worth reading about separately: voice to text not working in third-party apps on Mac.
6. Continuous dictation hitting its time limit
Classic (server-based) Dictation cuts off after a fixed window. When it does, the buffer flushes, and on some macOS versions the flush truncates the visible text. This is closely tied to the behavior covered in Mac dictation cutting off mid-sentence.
Nine Fixes That Stop the Deletion
Work through these in order. The early ones solve the problem for most people in under a minute.
Fix 1: Deselect before you speak
Before triggering dictation, click once at the exact spot where you want new text to appear so nothing is highlighted. If you just finished a dictation pass, press the Right Arrow key to collapse any lingering selection to the cursor. This single habit eliminates the most destructive version of the bug, because dictation can no longer replace a selection that does not exist.
Fix 2: Dictate in short bursts, then stop the session
Instead of leaving dictation running while you think, speak one or two sentences, then explicitly end the session (press the dictation key again or click Done). Start a brand-new session for the next chunk. A finalized session cannot be re-rendered, so previous text becomes untouchable. The trade-off is more start/stop friction, but it is the most reliable manual workaround.
Fix 3: Turn Dictation off and back on
A stuck or corrupted dictation buffer often clears with a clean restart of the feature:
- Open System Settings → Keyboard → Dictation.
- Toggle Dictation off. Wait ten seconds.
- Toggle it back on and confirm the language and shortcut.
This forces macOS to rebuild the dictation session from scratch and resolves buffers that have gotten into a bad state.
Fix 4: Review Text Replacement and autocorrect
Go to System Settings → Keyboard → Text Input → Edit and look for replacement rules that might be firing on dictated words. Temporarily disable "Correct spelling automatically" under the same panel and test whether the deletions stop. If they do, a correction rule was reaching backward into finalized text.
Fix 5: Dictate into a plain text field, then paste
Rich text editors are where the cursor-position bugs are worst. Dictate into a plain text field first (TextEdit in plain text mode, or the Notes app), confirm the text is intact, then copy and paste it into your real document. It is a workaround rather than a cure, but it sidesteps the editor-versus-engine disagreement entirely. If your destination app is a known offender, see the notes in why dictation text appears in the wrong place.
Fix 6: Update macOS
Several dictation buffer bugs have been fixed in point releases. Open System Settings → General → Software Update and install anything pending. If the deletion started right after an update, this is also worth reading: Mac dictation not working after a macOS update.
Fix 7: Check for a conflicting Voice Control session
Voice Control and Dictation both want to drive your text fields, and running them together produces exactly the kind of phantom edits and deletions described here. Open System Settings → Accessibility → Voice Control and make sure it is off unless you specifically need it. Running both at once is a recipe for the system stepping on its own edits.
Fix 8: Slow down and avoid long pronoun-heavy runs
Because the re-render is most aggressive when the engine second-guesses ambiguous words, dictating slightly slower and breaking on natural sentence boundaries gives the engine less reason to rewrite a finalized phrase. It is not a real fix, but it reduces the frequency while you implement the structural ones above.
Fix 9: Restart the dictation daemon (or the Mac)
If a single app is misbehaving, quit and reopen it. If the whole system is, a restart clears the dictation daemon and the accessibility services it depends on. A surprising number of "dictation is eating my text" reports clear after one reboot because a background service had wedged itself into a bad state.
The Real Problem: A Buffer That Never Commits
Notice that almost every fix above is a workaround for the same root cause. Apple's Dictation keeps your current utterance in a mutable buffer so it can correct itself, and any time that buffer re-renders, your finalized text is at risk. You are managing the buffer manually: deselecting, restarting sessions, dictating into safe fields. The feature is fighting you, and you are spending energy keeping it in line.
There is a fundamentally different design that does not have this failure mode at all: insert each phrase as final, the instant you finish speaking, and never touch it again.
A Different Approach: Insert Once, Never Re-Render
Voice Keyboard Pro is a native macOS app that lives in your menu bar. You hold a hotkey, speak, and release. The moment you release, your words are inserted at the cursor as a single finalized block of text. There is no live buffer hovering over your document, no second pass that shortens what you already said, and nothing that reaches backward to "correct" text you considered done. Each dictation is a discrete insert, the same way pasting from the clipboard is discrete. Once the text lands, it stays exactly as it landed.
That design choice is the whole point. Because there is no continuously rewriting buffer, there is nothing that can delete text you already dictated. You can dictate one sentence, click somewhere else, dictate another, and the first one is never at risk. It also means dictation behaves the same in every app, because the text is placed at your cursor rather than negotiated with each editor's input protocol. That is why it works in editors where Apple's Dictation struggles, a topic covered in how to dictate in any Mac app.
A few things follow naturally from that model:
- No accidental replacement. Nothing is selected behind your back, so nothing gets overwritten.
- Consistent behavior across apps. The same cursor-insert works in browsers, Slack, code editors, and rich text documents, the same places Apple's buffer tends to misbehave.
- Smart Vocabulary. Build a personal dictionary with replacement rules so names, jargon, and product terms come out right the first time, instead of being "corrected" into the wrong word by a generic autocorrect pass.
- Privacy by design. Our servers store only operational pings. Your audio and transcribed text are not retained on the server.
The transcription itself is fast and accurate, using Voice Keyboard Pro's advanced AI transcription engine, so the finalized text that lands at your cursor is usually right without any second-guessing pass. And because dictation is genuinely faster than typing once it stops fighting you, this is the moment a lot of people stop typing for routine writing altogether. If you are curious about the speed argument, how voice typing inserts text at the cursor in any app goes deeper.
Apple's dictation keeps your words editable so it can fix them. The cost is that it can also delete them. An insert-once model gives up the live correction and gets reliability in return.
Quick Reference: Stop the Deletions Today
If you only do three things from this guide, do these:
- Deselect before every dictation. Click to place a plain cursor with nothing highlighted.
- End each session before pausing to think. A finalized session cannot be re-rendered.
- Turn off Voice Control if you are not using it, so two systems are not editing the same field.
Those three habits eliminate the large majority of "Mac dictation keeps deleting text I already dictated" cases. For the rest, the structural fix is to stop relying on a buffer that re-renders at all.
If you would rather not babysit the dictation buffer every time you speak, Voice Keyboard Pro has a free tier. Dictate a paragraph, pause as long as you like, dictate another, and watch the first one stay put. The deletion problem simply does not exist when text is inserted once and left alone. For more troubleshooting, our full guide to fixing Mac dictation covers the other common failure modes.
Frequently Asked Questions
Does turning off autocorrect stop dictation from deleting text?
Sometimes, but not always. Disabling "Correct spelling automatically" removes one cause, the backward-reaching correction pass that can overwrite a finalized word. But it does not touch the bigger cause, which is the dictation buffer re-rendering your last phrase when you resume. If the deletions continue after you disable autocorrect, the problem is the buffer, not your spelling settings, and the structural fixes (ending each session, deselecting first) are what will help.
Why does dictation delete text only in some apps?
Because each app implements Apple's text input protocol to a different degree. Native apps like Notes and Mail handle the dictation buffer cleanly, so the re-render rarely damages anything. Browsers, Electron apps, and custom editors handle it loosely, so the same buffer update that is harmless in Notes can delete characters in Slack or Google Docs. If your deletions are concentrated in one app, that app's text field is the weak link, which is closely related to voice to text not working in third-party apps.
Is this the same problem as dictation cutting off mid-sentence?
They share a root cause but show up differently. Cutting off mid-sentence is the buffer flushing early and stopping; deleting text you already dictated is the buffer re-rendering and shortening what was there. Both come from the same mutable-buffer design. If you see both symptoms, read this alongside why Mac dictation cuts off mid-sentence and apply the session-ending habit, which helps with each.
Will a different dictation app actually fix it, or just move the problem?
It depends entirely on the design. Any tool built on the same live, mutable buffer will have the same risk. The fix is a tool that inserts each phrase as a single finalized block at the cursor and never edits it afterward, which is the model Voice Keyboard Pro uses. When there is no buffer hovering over your document, there is nothing that can reach back and delete finalized text.