Mac Keeps Switching Keyboard Language? 5 Causes and Fixes

You set your keyboard to English. You switch to Telegram, type half a message, and it comes out in the wrong alphabet. You'd swear you didn't touch anything - and you're probably right. macOS has several features that change your input language for you, and most people have at least one of them turned on without knowing it.

Here are the five causes, in order of how often they're the culprit. Check them top to bottom - for most people it's the first one.

1. Per-app input memory ("Automatically switch to a document's input source")

This is the big one. macOS can remember a separate input language for every app - and even for every document. Typed Ukrainian in Telegram once? Telegram now "belongs" to Ukrainian. Switch back from your English-language editor, and the layout silently follows the app, not you.

The setting sounds helpful, and for some workflows it is. But if you didn't consciously choose it, it just feels like your Mac has a mind of its own.

Fix: System Settings → Keyboard → Input Sources → Edit → turn off "Automatically switch to a document's input source". From now on, the layout only changes when you change it.

2. Caps Lock is switching your layout

Since macOS Sonoma, there's a setting that makes Caps Lock double as a layout switcher: press it to switch language, hold it for actual caps. If it's on, every accidental Caps Lock tap changes your language - and you won't notice until the text comes out wrong.

Fix: System Settings → Keyboard → Input Sources → Edit → turn off "Use the Caps Lock key to switch to and from" your layout.

3. A shortcut conflict is switching it for you

The default layout-switch shortcut is Ctrl+Space (or Fn/Globe). Ctrl+Space is also a popular shortcut inside apps - code editors use it for autocomplete, some launchers and window managers grab it too. Depending on which app wins, you either don't switch when you meant to, or you switch when you meant to autocomplete.

Fn/Globe has its own trap: tap it accidentally on its way to a function key, and you've switched languages without noticing.

Fix: System Settings → Keyboard → Keyboard Shortcuts → Input Sources - set a deliberate combo you never press by accident. Then check what the Globe key does under Keyboard → "Press 🌐 key to" and set it to something harmless if you keep hitting it.

4. You have layouts installed that you never use

Every layout in your input menu is one more stop in the rotation. If you have three layouts but only type in two, a third of your layout switches land on a keyboard you never wanted - and the "my Mac switched to some weird language" feeling is often just this.

Fix: System Settings → Keyboard → Input Sources - delete everything you don't actively type in. Two languages? Keep exactly two layouts.

5. It's not switching - you just can't see what's active

Sometimes the layout didn't change at all; you just assumed it was English because the last thing you remember typing was English. The input indicator in the menu bar is a tiny icon in the corner, and when you're typing, your eyes are on the text - not the corner.

Fix: make the state visible. System Settings → Keyboard → Input Sources → keep "Show input menu in menu bar" on. Some third-party tools can also show the layout near the cursor or flash it on switch, which helps more than the menu bar icon ever will.

And when the wrong-layout text still happens

All five fixes make the problem rarer. None of them make it disappear - because the root cause is that your hands and the active layout can disagree, and you find out only after the words are on the screen.

That last mile is what our app Boomkey handles. When a word does come out in the wrong layout, you hit space and it fixes itself (beta, English ↔ Ukrainian, Belarusian, Hebrew, Russian) - or you double-tap Shift and the selected text converts between any two layouts you have installed. Retyping stops being part of the routine.

It's a native menu bar app, everything runs locally on your Mac, one-time purchase with a 7-day trial - no card, no account.

Fix the settings above first, though. A calmer input setup plus a safety net for the leftovers - that combination is what actually ends the problem.