Dictated words land in the wrong app or the wrong spot
· 6 min read
Dictated text goes wherever the keyboard would go, which is not always where you are looking. On macOS the words land in the window that has keyboard focus and at the insertion point inside it, so when a sentence turns up in the wrong app, a search box or the middle of a paragraph you had already finished, focus moved without you noticing.
Four causes account for nearly all of it: focus sitting in a different window, a text field that refuses dictated input on purpose, a web editor that handles keystrokes its own way, and a cursor that was never placed. They have different fixes, so it is worth identifying which one you have.
Check where focus actually is
The window with focus has a colored, fully drawn title bar and toolbar. Background windows look faded. Before dictating, look for that difference rather than assuming the window under the pointer is active, because on a Mac the pointer does not carry focus with it.
Things that steal focus quietly:
- A notification banner that you clicked, or that opened an app in the background.
- An app finishing a launch several seconds after you clicked it, which pulls focus forward mid-sentence.
- Switching Spaces or displays. Moving the pointer to another monitor does not change focus. Click once in the target window first.
- Stage Manager grouping windows, where clicking the strip on the left brings a whole set forward.
- A dialog that opened behind the main window and is waiting for a keystroke.
The reliable habit is one click into the exact field you want before you start speaking. Not the window, the field. Clicking a window’s background gives the window focus with no insertion point, and the text has nowhere to go.
If you regularly dictate into an app that is not frontmost, that is not a supported way to work on macOS. Bring it forward with Command-Tab and speak then.
Fields that refuse dictated text by design
Some text fields will not accept synthesized keystrokes, and this is a security feature rather than a bug.
Password fields. When a password field is active, macOS turns on secure input, which blocks other processes from seeing or inserting keystrokes. Dictation into a password box will not work, and it should not. Type those.
Terminal with Secure Keyboard Entry. Terminal has a Secure Keyboard Entry option in its Terminal menu. When it is checked, the same protection applies to every Terminal window, and dictated text will not land there. Uncheck it if you want to dictate commands and you accept what that means.
The awkward part is that secure input is sticky. If an app enables it and does not release it cleanly, dictation can stop working system-wide even after you leave the password field. The tell is that nothing types anywhere. Click into a normal text field in a different app, then click back. If it persists, quitting the app that held the password field usually releases it, and logging out and back in always does.
Web editors and rich text areas
A page that implements its own editor handles keystrokes itself rather than using a normal text field, and results vary. Common symptoms:
- Text appears but formatting collapses, or each pause starts a new line.
- The cursor jumps to the top of the document between phrases.
- Autocomplete in a chat or address field captures the first word and turns the rest into a search.
Two things help. Dictate into a plain field first and paste, which costs one extra step and is immune to whatever the page does. Or dictate in shorter bursts, since the shorter the insertion, the less the page has to reconcile.
Address bars and chat boxes deserve a specific mention because their autocomplete is aggressive. If you dictate into one and the first word triggers a suggestion, the remaining words can be swallowed. Press Escape to dismiss the suggestion list, then continue.
The cursor was never placed
This is the least interesting cause and the most common. You clicked the window, or switched to the app with Command-Tab, but never clicked inside the document. There is a window with focus and no insertion point, so nothing appears, or the text lands at whatever position was last used, which in a long document can be pages away from where you are reading.
A useful reflex: before speaking, press Command-A in the field. If the text highlights, there is an insertion point and it is in the field you think it is. Press the right arrow to deselect and continue.
If words are appearing in the middle of an earlier paragraph, that is the same problem. Scrolling does not move the insertion point on a Mac. Click where you want to write, then dictate. Voice commands while dictating covers steering the cursor by voice once you are in the right place.
Hold the key rather than toggling it
A toggle is a state you have to remember. Turn dictation on, switch windows to check something, come back, keep talking, and the text goes wherever focus ended up. That is the mechanism behind most misplaced paragraphs, and it is a design problem rather than a mistake on your part. Hold-to-talk dictation makes the case in full.
With a held key, the window you are in when you press is the window you are in when you release, because you cannot hold a key and reorganize your desktop at the same time. Voice Keyboard Pro works this way on the Mac: hold a key you choose (Left Control by default), speak, release, and the words land at the cursor in whatever app is in front, including Slack, Gmail, VS Code, Terminal and browsers. Most dictations land in 200 to 500 ms after release. It never types without the key held, so there is no always-on state to lose track of.
It is a menu bar app for macOS 14 Sonoma or later. By default audio goes over an encrypted connection to a transcription provider and is discarded after transcription; Offline Mode in Settings runs transcription entirely on the device with no network. There is a free tier of five dictations a day, and Pro is a subscription covering Mac and iPhone together with a seven-day trial. It is the one subscription in this studio, which is worth knowing before you try it.
None of this removes the need to click into the right field first. It removes the window in which focus can drift away between starting and finishing.
Questions
Dictation stopped working in every app at once. What changed? Almost always stuck secure input from a password field. Quit the app that had the password box, or log out and back in. If it happens repeatedly with one app, that app is the culprit.
Why does the text arrive several seconds late and in the wrong place? Focus moved during the delay. If you start dictating and then click elsewhere while the transcription is still being produced, it lands at the new insertion point. Stay put until the words appear.
Can I dictate into an app on a second display without clicking it first? No. The pointer being over a window does not give it focus on macOS. Click once, then dictate.
Does turning off Secure Keyboard Entry in Terminal put me at risk? It removes a protection that stops other processes reading keystrokes in that window. On a Mac you control, with software you trust, many people leave it off. Turn it back on before typing anything sensitive, and see dictating code and shell commands for where voice input in a terminal is worth it at all.