Dictating into Slack, mail and a code editor on a Mac
· 6 min read
Dictation on a Mac types into whatever field holds the cursor, so the app itself is rarely the problem. What changes from app to app is everything around the words: whether the Return key sends a message, whether automatic punctuation helps or ruins the line, and whether the field accepts inserted text at all. Get those three straight and voice typing works everywhere you write.
Dictation follows the cursor
There is no separate dictation window and no per-app setting to hunt for. You click into a text field so the insertion point is blinking there, start dictation, and the words appear at that point as though you had typed them. Click somewhere else halfway through a sentence and the rest of the sentence lands in the new place.
Two exceptions are worth knowing before you blame an app. Password fields refuse dictated text on purpose, along with most fields an app has marked as secure; that is macOS protecting you rather than a bug. And a field without focus receives nothing, which explains most cases of speaking a paragraph at an app that still shows an empty box.
Turn it on and pick a shortcut you can reach
- Open System Settings, Keyboard, and find Dictation. Turn it on. The first time, macOS shows a note about where speech is processed and may download a language file.
- Set the language. Add a second if you write in two; you can switch between them while dictating.
- Set Microphone Source. Automatic is fine at a desk. If you wear a headset, choose it explicitly, so that closing a laptop lid or connecting a display does not quietly move you to a worse microphone.
- Choose the shortcut. The menu offers a few key combinations, such as pressing Control twice, and lets you set your own. Pick something your hands find without looking.
- Click into Notes or TextEdit and dictate a paragraph before you try it on a colleague.
The built-in shortcut is a toggle: press once to start, press again to stop, and it stops on its own after a stretch of silence. That detail matters in chat, where you speak in bursts of eight words with long pauses between them.
Slack: the words are fine, the Return key is not
Dictation puts text into a Slack message box without any trouble. The friction is that Slack sends the message when you press Return, and dictating encourages you to think in short lines and reach for Return between them.
Three habits fix it.
Use Shift-Return for a line break inside a message, or open Slack’s preferences and change which key sends. Either is fine; what is not fine is switching between them, because muscle memory here is exactly what fires off half a thought.
Say “new line” and “new paragraph” instead of touching the keyboard. macOS treats both as commands and inserts a break rather than typing the words.
Read the message before it goes. Dictated text is usually right and occasionally very wrong, and chat is the medium where people reply before you can fix it.
Names are the other weak point in chat: colleagues, project codes, internal acronyms. Built-in dictation has no vocabulary you can teach it, so the same surname comes out wrong the same way every day.
Mail and text fields in a browser
A mail window is several fields, and dictation only fills the one with focus. Dictate the body, then click or tab to the subject line and dictate that separately. Trying to speak an entire email including its subject produces a subject line containing the whole message.
Web mail and other browser fields behave the same way. Rich editors on the web occasionally do something odd with an inserted block of text, usually around bullet lists and quoted replies, so dictate a paragraph at a time rather than a page.
Two commands are worth memorizing here: “select all” and “undo”. When a paragraph comes out badly, saying either is faster than reaching for the mouse.
A code editor, and why Terminal is different
For the prose that lives inside a code repository, dictation is genuinely useful: commit messages, pull request descriptions, comments, docstrings, the section of the README you have been avoiding for a month. Those are sentences, and sentences are what speech recognition is built for.
For code itself it is poor. The reason is punctuation density and exact spelling: handleRetryPolicy is not a word, braces and brackets are not sounds, and a name that is nearly right is worse than nothing because it compiles into a different bug. Automatic punctuation compounds it by dropping a comma wherever you paused for breath. The workable rule is to dictate the sentence and type the symbols.
Terminal deserves a specific warning. Its Terminal menu has a Secure Keyboard Entry option, and while that is on, tools that insert text into the front window can be blocked from doing so. It looks like a broken dictation app rather than a setting you turned on months ago. The other warning is plainer: a dictated command you have not read before pressing Return is a bad way to find out what a homophone does to a path.
Where a dictation app changes the picture
What is built into macOS covers the common case at no cost, and if you dictate a few messages a day you can stop here. Two things push people to something else: the toggle, and vocabulary.
Voice Keyboard Pro is built around a held key instead. You hold a key you choose (Left Control by default), speak, then release, and the text lands at the cursor in whatever app is in front, usually within 200 to 500 ms of the release. Because the microphone is open only while your finger is down, the shape of it fits chat and code review, where you talk for six seconds and then read for a minute. It keeps a personal vocabulary, which is how a project code or a colleague’s surname stops arriving mangled, and it understands spoken commands such as “new line”, “select all” and “undo”.
The limits, said plainly: it needs macOS 14 Sonoma or later, it types nothing unless the key is held (there is no always-on listening), and the free tier is 5 dictations a day. Unlimited use is a subscription that covers the Mac and iPhone apps together, with a 7-day trial. It is the one subscription in our lineup, which is worth saying rather than burying.
For longer stretches of writing, writing a first draft by voice covers the technique. If you want to know what leaves the machine when you speak, where your audio goes when you dictate on a Mac goes through it.
Questions
Nothing appears when I dictate into a password field. Is dictation broken? No, that is deliberate. Password and other secure fields refuse inserted text so that nothing sitting between your microphone and the field can capture or supply a credential. Type passwords, or use a password manager’s own fill.
Can I dictate in one language and type in another? Yes. Add both languages under Dictation in Keyboard settings and a picker appears while you dictate. The app you are typing into does not care; it receives characters either way.
Does a Bluetooth headset work as the dictation microphone? It does, with one caveat: many headsets switch into a call mode when their microphone opens, and on some models that noticeably degrades what the Mac hears. If accuracy drops the moment you put the headset on, try the built-in microphone in a quiet room and compare.
How do I stop it inserting punctuation I did not ask for? Turn off Auto-punctuation in the Dictation settings and say the punctuation aloud instead. In a code editor that is nearly always the better setting, because inferred commas land in the middle of arguments.