Short answer: Mac dictation writes in whichever language is selected in System Settings, Keyboard, Dictation. Open that panel, click the Languages menu, remove the wrong entry, and add the one you want. If the language is right but the words are wrong, you almost certainly have the wrong regional variant selected.
There are two very different complaints hiding inside the phrase "Mac dictation is typing in the wrong language," and the fix depends on which one you have. In the first, you speak English and the screen fills with Spanish, or French, or a script you cannot read at all. In the second, the output is technically English, but it is not your English. Words come out mangled, spellings are off, and the whole thing feels like it is guessing. That second case is the more common one and the one people rarely diagnose correctly, because at a glance it looks like a general accuracy problem rather than a language problem.
This guide separates the two, then works through the fixes in the order most likely to solve it. If you have the same problem on your phone, we covered the iPhone version separately in iPhone dictation typing in the wrong language, and the settings live in a completely different place there.
First, tell the two problems apart
Dictate one clean test sentence into TextEdit or Notes. Say something with a few distinctive words in it, at a normal pace, close to the microphone. Then look at what appeared.
- Actual foreign words or a foreign script. You said "let me check the schedule" and got a line of Spanish, German, or Chinese. This is a language selection problem. Jump to fix one.
- Right language, wrong words. You got English, but it wrote "colour" when you say "color," or turned "route" and "schedule" and proper nouns into things you did not say. This is almost always a regional variant mismatch. Jump to fix two.
- Right language most of the time, but it flips mid-session. You are getting bursts of another language inside otherwise correct text. That is usually a multi-language setup with automatic switching enabled. Fix three.
- Total nonsense in no identifiable language. Not really a language problem. That is a microphone path or speech-asset problem, and it belongs with Mac dictation typing the wrong words.
Doing this test in TextEdit matters. If you only ever test inside the app where you noticed the problem, you cannot tell whether the app is doing something of its own, such as applying its own autocorrect or a language-specific spell check on top of what dictation produced.
Fix 1: Set the dictation language explicitly
Dictation on Mac keeps its own language list, and it is not the same list as your keyboard input sources or your system display language. That is the single biggest source of confusion. You can have your Mac entirely in English, type on a US keyboard, and still have dictation set to something else, because at some point a second language got added to that specific list.
Open System Settings, go to Keyboard, and find Dictation. Click the Language menu. You will see the currently enabled dictation languages. Choose Edit or the language list, uncheck everything you do not want, and check the one you do. Close the panel, wait for any download to finish, and test again in TextEdit.
Two things people miss here:
- The menu is a multi-select, not a single choice. If two languages are enabled, dictation is free to hand you either one. Reducing the list to exactly one language removes the ambiguity entirely, and for most people that is the whole fix.
- Turning dictation off and on again does not reset the language. The list persists. If you toggled dictation off in frustration and back on, you came back to exactly the same configuration.
If the language you want is greyed out, missing, or refuses to become active, that is a separate download problem and we walk through it in Mac dictation language not available.
Fix 2: Match the regional variant to how you actually speak
This is the fix that solves the "right language, wrong words" case, and it is worth understanding why it works so well.
English is not one recognition target. English (United States), English (United Kingdom), English (Australia), English (India), English (Singapore) and the rest are separate configurations, each tuned to a different set of vowel sounds, a different set of common phrases, and a different spelling convention. When your speech does not match the variant that is selected, the system spends its effort mapping your sounds onto the wrong expectations. The result is not random noise. It is confident, plausible, wrong text, which is the most annoying failure mode there is.
The tell is words that are consistently wrong rather than occasionally wrong. If "schedule," "data," "route," "either," or "advertisement" come out mangled every single time, that is a vowel and stress pattern that the selected variant is not expecting. Spelling drift is the other tell: getting "organise" when you meant "organize," or "center" when you meant "centre," means the output side of the variant does not match you either.
The fix is to choose the variant that matches how you speak, not the country you currently live in and not the country the Mac was bought in. Someone with an Indian English accent working in Berlin should try English (India) before English (United Kingdom). Someone with a British accent working in Texas should try English (United Kingdom) rather than leaving the default US variant in place.
Change one variant, then dictate the same paragraph you dictated before and count the corrections. Comparing corrections on the same paragraph is a much better test than a general sense of whether it "feels better." If the count drops meaningfully, keep the new variant. If it does not, try the next closest one. This takes about five minutes and is the highest-leverage thing you can do to Mac dictation without installing anything.
Fix 3: Turn off automatic language switching
If you have more than one dictation language enabled, the system has to decide which one you are speaking at any moment. That decision is made from the audio, and it is made fast. A short utterance, a noisy room, or a sentence that begins with a proper noun gives it very little to work with, and it will sometimes pick wrong. When it picks wrong, you get a burst of the other language in the middle of otherwise correct text.
If you genuinely dictate in two languages, this behaviour is a feature and you may want to keep it. If you only ever dictate in one and a second language is enabled because you set it up once for a trip or a class, remove it. A one-language list cannot guess wrong.
For people who really do work across languages every day, switching manually is more reliable than letting the audio decide. It costs a click, and it removes an entire class of errors. We go deeper on multi-language workflows in multilingual voice typing on Mac.
Fix 4: Check your input source, not just dictation
The keyboard input source and the dictation language are separate settings, but they interact in a way that produces convincing false alarms. If your input source is set to a different language, the text field may apply that language's autocorrect and spell check to whatever dictation inserts. Dictation transcribed you correctly, and then something downstream rewrote it.
The tell here is timing. Watch the text as it lands. If the correct word appears and then changes a beat later, dictation was never the problem. Open System Settings, Keyboard, Input Sources, and make sure the active input source matches the language you are dictating in. Also check the spelling language in the app itself if it has one, since apps like Word and Pages carry their own per-document language setting that overrides the system.
Fix 5: Restart after a language change
Changing the dictation language while apps are already open is a common source of "I changed it and nothing happened." Running apps can hold onto the previous configuration until they are restarted. Quit the app you are testing in, reopen it, and dictate again. If it is still wrong across a fresh app, restart the Mac before concluding the setting did not take.
This is worth doing before any of the heavier fixes below, because it is thirty seconds of work and it rules out a stale state that otherwise makes you chase a problem you have already solved.
Fix 6: Re-download the language assets
Mac dictation downloads support files for each enabled language. A download that was interrupted by sleep, a network drop, or low disk space can leave a language half-installed. The symptom is usually worse than a variant mismatch: quality is poor across the board, or the language appears enabled but behaves like a different one.
To force a clean re-download, remove the language from the dictation language list, quit System Settings, wait a moment, then reopen and add the language back. Leave the Mac awake and on a stable network until the download completes. Check available disk space first. If the drive is nearly full, the download will fail quietly and you will repeat this loop forever.
Fix 7: Rule out a conflicting accessibility feature
Voice Control is a separate macOS feature from dictation, and it has its own language setting. When both are active, they compete for the microphone and for your speech, and the resulting text can look like a language problem when it is really two systems fighting. If Voice Control is enabled and set to a different language than dictation, turn Voice Control off in System Settings, Accessibility, and test again. We cover the interaction in more depth in the Mac dictation and Voice Control conflict fix.
Fix 8: Look for a text replacement rule that is rewriting you
Text Replacement entries under System Settings, Keyboard, Text Replacements apply to dictated text just like typed text. An old entry created for another language, or a short trigger that happens to match a common word, will silently rewrite output after dictation has done its job correctly. Scan the list and delete anything you do not recognise. This is a small cause but it produces genuinely baffling symptoms, because the wrong word is always the same wrong word.
Fix 9: Test with a different microphone path
Language identification is done from audio, so anything that degrades the audio makes a wrong-language pick more likely. Bluetooth headsets are the classic offender: when a headset switches into its two-way call mode, the microphone quality drops sharply, and thin audio gives the language detector less to work with. If you are on AirPods or a Bluetooth headset, dictate one test paragraph using the built-in microphone with the headset disconnected. If the language problem disappears, the audio path was contributing.
Same logic applies to an external interface, a dock with a microphone input, or a webcam microphone that macOS chose automatically. Open System Settings, Sound, Input, and confirm the selected device is the one you are actually speaking into.
The design limit behind all of this
Work through those nine and most wrong-language problems are gone. But it is worth naming what is left over, because a lot of people keep tweaking settings looking for a fix that does not exist.
Built-in dictation asks you to declare, in advance, exactly one thing about how you speak: a language and a region. Everything downstream is built on that declaration. If you are a bilingual speaker whose English carries the rhythm of another language, or you use vocabulary from a field the variant has never seen, or you switch languages inside a single sentence the way multilingual people actually do, there is no setting that covers you. You pick the closest option and absorb the errors.
The other limit is that it does not learn. Correct the same misheard word two hundred times and the two hundred and first attempt is identical to the first. The system has no memory of your corrections, so the errors that survive the settings work are permanent.
A language setting describes a population. Your corrections describe you. Software that only reads the first one will keep making the same mistakes forever.
That is the gap Voice Keyboard Pro is built to close. On Mac it sits in the menu bar: hold your hotkey, speak, release, and the text lands at your cursor in whatever app is in front of you, without any per-app setup. Because it uses its own transcription engine rather than the system dictation stack, it is not bound to the one variant you declared in System Settings, which removes the most common cause of the problem this article is about.
Smart Vocabulary handles the residue. It is a personal dictionary with replacement rules, so the names, jargon, product names and place names that a regional variant will never know become things you enter once and stop correcting. That is precisely the error class no language setting can fix, because the problem was never your accent, it was that the word is not in anybody's general vocabulary.
On iPhone, the same app installs as a keyboard with a built-in mic button, and adds two-way translation across 24 languages while you dictate, plus Voice Edit for speaking a correction instead of poking at the text with your thumb. If you routinely work across languages, that is a different model than fighting an automatic switcher.
Quick reference
- Test in TextEdit and classify: foreign language, wrong variant, mid-session flip, or general garbage.
- System Settings, Keyboard, Dictation, Language: reduce the list to exactly one language.
- Choose the regional variant that matches how you speak, not where you live.
- Remove second languages you do not use so automatic switching cannot guess wrong.
- Check the keyboard input source and the app's own spelling language.
- Restart the app, then the Mac, after any language change.
- Remove and re-add the language to force a clean asset download.
- Disable Voice Control while testing.
- Audit Text Replacement entries.
- Test on the built-in microphone with Bluetooth disconnected.
If you have done all ten and a specific set of words is still wrong every time, you have hit the vocabulary ceiling rather than a configuration bug. Voice Keyboard Pro has a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. Nothing you dictate is stored on our servers, only operational pings, so the words themselves stay on your machine.