← Back to Blog

Short answer: Mac dictation does not reliably add punctuation on its own. In most languages you must speak the marks aloud, saying "comma" and "period" as you go. Check your dictation language, speak the commands clearly, and pause briefly before each one. For punctuation added automatically, use a dictation tool that infers it from context.

You dictate a paragraph. It comes back as one long unbroken run of words with no commas, no periods, and no paragraph breaks, reading like a telegram written by someone in a hurry. You go to System Settings looking for the switch labelled "add punctuation" and it is not there, because it does not exist in the form you are imagining.

This is the most misunderstood behavior in macOS dictation, and the fix depends entirely on which of two problems you actually have. Work through this page in order and you will land on the right one.

First: which problem do you have?

There are two completely different failures that both look like "punctuation is not working," and the fixes have nothing in common.

The rest of this article is about Problem A, which is by far the more common of the two, and about the fact that the honest answer to it is not a setting.

Why macOS does not punctuate for you

Apple's dictation was built around explicit voice commands. The design assumption is that you, the speaker, will tell it where the punctuation goes: you say the words "comma" and "period" out loud and it converts them into marks. It is not trying to interpret your pauses, your intonation, or the grammatical shape of your sentence. It is transcribing the words it hears and swapping recognized command words for symbols.

That means there is no toggle to hunt for. When people search System Settings for an automatic punctuation switch and cannot find it, they usually conclude that something is broken or that a recent macOS update removed it. Neither is true. The capability was never there in the form they want.

Some languages and some contexts get a degree of automatic punctuation, and the behavior has shifted across macOS releases, which is exactly why the internet is full of contradictory advice on this. Do not build your workflow on it. If you need punctuation to be reliable, you need either the spoken commands or a different engine.

Fix 1: Learn the punctuation commands

If you are staying with Apple's dictation, this is the actual fix, and it takes about a day to become automatic. Speak these words aloud where you want the mark:

So the sentence you want is spoken like this: "Hi Sarah comma thanks for the update period Can you send the revised numbers by Friday question mark"

It works. It also permanently changes what dictation feels like, and that is the part nobody warns you about. You are no longer speaking, you are narrating markup. It is difficult to hold a thought and simultaneously remember to say "comma" in the right places, which is why so many people try dictation for a week and quietly give up. The tool is not failing. It is asking you to do a job the tool should be doing.

Fix 2: Pause briefly before each command

If you are saying the commands but getting inconsistent results, run the words together less. A short beat before "period" helps the recognizer treat it as a command rather than as part of the surrounding phrase. This matters most with words that are ambiguous in context, which is why the sentence "the period of the study was six months period" is the kind of thing that produces nonsense.

Fix 3: Check your dictation language

Open System Settings → Keyboard → Dictation and look at the language list. Punctuation-command handling and any automatic punctuation behavior vary by language, and if your Mac is set to a variant you did not intend, such as a different regional English, results get erratic.

Two things to check while you are there:

Fix 4: Speak in complete sentences, not fragments

Recognition quality drops when input arrives in short bursts. If you dictate three words, pause, dictate four more, pause, the engine has very little to work with. Longer continuous phrases give any transcription system more context to resolve ambiguity, which improves both word accuracy and, where automatic punctuation exists at all, the placement of marks.

Practically: think of the sentence before you start talking, then say the whole thing. This single habit does more for dictation quality than any setting on this page. Our broader dictation accuracy guide goes through the rest.

Fix 5: Fix your microphone situation

Punctuation commands are short words. Short words are the first thing lost to a bad audio path. If "comma" is being dropped or misheard, the microphone is a real suspect.

Fix 6: Rule out the app you are dictating into

Some applications interfere with text insertion in ways that mangle punctuation specifically, usually by fighting with autocorrect or by re-formatting text as it arrives. Rich text editors and browser-based editors are the usual suspects.

The diagnostic is thirty seconds: open TextEdit, dictate the same sentence with the same commands, and see what happens. If punctuation works in TextEdit and fails in your target app, the problem is the app, not dictation. Word is a repeat offender here and has its own guide at dictation not working in Microsoft Word on Mac.

Fix 7: Turn off the settings that are rewriting you

macOS has text substitution features that alter what dictation inserts. In System Settings → Keyboard → Input Sources → Edit, look at:

If your punctuation is appearing but appearing wrong, this section is where to look before you blame the dictation engine.

Fix 8: Restart dictation properly

When dictation has been running for a long session and starts behaving oddly, including dropping commands it was handling correctly an hour ago, reset it. Toggle Dictation off in System Settings, wait a few seconds, and toggle it back on. A logout or restart clears the rest. This is unsatisfying advice, but the failure is real and the fix is quick.

If dictation has stopped responding entirely rather than just dropping punctuation, start with Mac dictation not working: the full fix list instead.

Fix 9: Stop dictating punctuation

Every fix above is a workaround for a design decision. The commands are learnable, the microphone is fixable, the app conflicts have answers. But none of it addresses the actual problem, which is that you are being asked to do the machine's job.

Consider what you are really doing when you say "comma" out loud. You are performing a manual conversion from spoken language into written punctuation, in real time, while also trying to think about what you are saying. Nobody speaks that way. It is the reason dictation feels unnatural to most people the first time they try it, and the reason they conclude that voice typing is not for them.

The alternative is an engine that punctuates from context. You speak the sentence the way you would say it to a colleague, and the punctuation is inferred from the structure of what you said. No commands, no narration of symbols, no learning a second language made of the words "period" and "new paragraph".

That is how Voice Keyboard Pro works. Hold your hotkey, speak the sentence normally, release, and the text arrives at your cursor with commas, periods, and question marks already in place. It is a menu bar app, it works system-wide in any application, and it does not require you to think about punctuation at all. You can still say "new paragraph" when you want a specific structure, but you are no longer obliged to.

The best punctuation setting is the one you never have to think about.

Two more things worth knowing, because they solve the problems that show up right after punctuation is fixed:

The quick diagnostic table

To recap, matched to what you are seeing:

One last thought on the speed math

The reason any of this matters is throughput. Most adults type around 40 words per minute, and professional typists reach 80 to 100. Everybody speaks at 130 to 150. That gap is the entire argument for dictation, and saying "comma" out loud gives a meaningful slice of it back, because you are now spending mental effort on formatting instead of on the sentence.

Punctuation should be invisible. You should be able to think a sentence, say it, and watch it land correctly formatted, with the same lack of ceremony you would have if you had typed it. That is a solved problem now. If you have been fighting your Mac's dictation for months, the fix might not be another setting.

Voice Keyboard Pro has a free tier with daily limits if you want to test that claim against your own writing. Dictate a paragraph the way you would say it out loud, without saying "comma" once, and see what comes back. Pro is $4.99/month or $34.99/year.

Keep reading