Switching Chrome Between English and Japanese on a Mac

Someone who works across Gmail, Slack, Notion and a handful of dashboards eventually needs one of them in a different language than the rest. The obvious move is to open Chrome settings, click Languages, and switch. On a Mac that move fails, and the reason is not that the option is hidden. It does not exist there. Three different things are bundled under the phrase "change the language," they live in three different places, and only two of them are inside Chrome at all.

Three settings that all get called "language"

Before touching anything, it is worth separating what actually needs to change. The wording in search results rarely does this, which is why the same advice gets repeated and keeps not working.

What you want to change	Where it actually lives	How far it reaches
The text on the page you are reading	Google Translate controls in Chrome settings	One page at a time
Which language sites decide to serve you	Preferred languages in Chrome settings	Every site in that profile
Chrome's own menus and buttons	macOS Language and Region settings	The whole Chrome application

The first two are per profile. The third is per application, which is the source of most of the confusion. A person who splits work and personal into separate Chrome profiles can give each one a different preferred language, but both profiles will always show the same menus, because macOS decides that for the application as a whole.

There is a quick way to work out which row applies. Look at the text that is wrong and ask who wrote it. If it belongs to Chrome itself, such as the word Bookmarks in the menu bar or the labels on the settings page, that is row three. If it belongs to a website, such as the body of an article or a product page, that is row one. If it is a site that clearly has both language versions and keeps choosing the wrong one for a signed-out visitor, that is row two. Sorting the symptom this way takes a few seconds and removes most of the guesswork.

Guides written for Windows collapse rows two and three into a single checkbox, because on Windows that checkbox exists. Following those steps on a Mac produces a settings page where the promised option is simply absent, and the usual next move is to keep searching the same screen. That is the loop worth breaking early.

Why Chrome on macOS has no interface language option

This is documented, not a bug. The Chrome help page that covers translation and browser language describes the interface language procedure as a Windows procedure, and states the macOS behaviour directly.

Mac or Linux: Chrome will automatically display in the default system language for your Mac or Linux. Source: support.google.com

The same page describes an option called "Display Google Chrome in this language" and notes that it is only available on Windows computers. So the answer to "where is the toggle" is that there is no toggle to find. Chrome inherits whatever language macOS hands it.

This has a practical consequence that is easy to miss. Reordering the preferred languages list, restarting Chrome, and checking again will never change the menus. Preferred languages is a request sent to websites, not a setting for the browser chrome itself. Time spent dragging Japanese above English in that list, hoping the interface follows, is time spent on the wrong row of the table above.

Setting Chrome's language from macOS instead

macOS can assign a language to a single application without changing the language of the whole system. Apple documents this under Language and Region.

You can also choose different languages for individual apps. For example, if your system language is set to Simplified Chinese, but you prefer to use a certain app in English, you can do so. Source: support.apple.com

The steps are short. Open the Apple menu, choose System Settings, click General in the sidebar, then click Language and Region. Scroll to the Applications section, click the plus button, pick Chrome and the language from the pop-up menu, then click Add. If Chrome is already listed, select it and change the language from the pop-up instead of adding a second entry.

Two details save a second round trip. Changes do not apply to a running application, so quit Chrome completely and open it again. And this setting is about the browser's own interface only. Menus, right-click items, the settings page and warning dialogs will follow it. The contents of Gmail or Slack will not, which is the subject of a later section.

The direction works both ways. A Mac running in Japanese can have Chrome in English for screen sharing with an overseas team, and a Mac running in English can have Chrome in Japanese for a client who reads over your shoulder. The switch takes about as long as reading this paragraph, which makes it reasonable to change per project rather than living with a compromise.

Preferred languages are a signal you send to sites

Even though preferred languages do not touch the interface, they are worth setting deliberately, because they leak into everyday browsing in ways that look like bugs. A multilingual service that has not been told otherwise will often look at this list to decide whether to serve its English or Japanese pages. A signed-out documentation site, a support portal, a booking page: any of these can flip language based on the order of that list.

The list lives under Settings, then Languages. Each entry has a menu for moving it up, moving it down, or removing it. The same screen holds the translation behaviour: whether Chrome offers to translate at all, which language it translates into, which languages get translated automatically without asking, and which languages it should never offer to translate. A translation bar that appears on every English page can be silenced by adding English to that last list, rather than by turning translation off entirely.

Because this is stored per profile, it can be used as a rough separation tool. A profile used for an English-language client can put English at the top; a profile used for domestic work can put Japanese at the top. That works, up to the point where the same person is signed into three services in one language and two in another, in the same window. At that point the list stops being a solution and starts being one more thing to remember.

Typing in a language is a separate axis again

Display language and input language get treated as one problem and they are not. Switching between Japanese and Roman input on a Mac is handled by input sources under Keyboard in System Settings, which has nothing to do with Chrome's settings or with the per-application language assignment. Putting Chrome into English does not remove the ability to type Japanese, and putting Chrome back into Japanese does not restore Japanese typing if the input source is still set to Roman characters.

The practical failure looks like a broken setting. Someone changes the interface to English, keeps getting Japanese conversion candidates while writing an English document, and concludes the language change did not take. It did take. The conversion candidates come from the input source, which is unchanged, and the fix is a keyboard shortcut for switching input sources rather than another trip through the language settings.

Search behaves as a third axis. Which results come back for a query typed into the address bar depends on the default search engine and on that service's own region settings, not on how Chrome's menus are labelled. An English interface does not produce English-language results. Treating display, input, and search as three independent settings prevents a lot of pointless back and forth.

What else moves when the interface language changes

Changing the interface language touches more than the menu bar, and knowing what moves prevents a false alarm afterwards.

Spell check follows the language configuration, so a document that mixes scripts can suddenly show more red underlines than before. Right-click menus and the settings page get relabelled, which means every remembered position on that page now reads differently even though nothing moved. Error messages and help text change too, and that quietly changes the words available to search with when something goes wrong.

Extensions are the exception worth planning around. The browser's interface language does not propagate into an extension's own panels. An extension that ships only Japanese strings will keep showing Japanese inside an English Chrome, and there is no setting that fixes it from the browser side. Extensions also carry a separate risk: anything built on Manifest V2 was disabled in Chrome 138 and removed from the store on 31 August 2026. Older articles recommending a language-switching extension by name may be pointing at something that can no longer be installed at all. Check that an extension is still distributed before building a workflow around it.

When the problem is the web app, not the browser

The most common dead end looks like this. Chrome's interface is now in the right language, the preferred languages list is in the right order, and Gmail still opens in English. Nothing is broken. Web apps generally store display language on the account, not in the browser, and the account setting wins.

That means the fix is per service and outside Chrome entirely. Most services keep it under account settings or personal preferences. The awkward case is not finding the setting, it is having two accounts in the same service with different language settings, both open in the same browser. Switching between them in one window makes it genuinely hard to tell which account is answering, and a language mismatch is often the first visible symptom of having typed into the wrong one.

Handled at the browser level, the durable answer is to stop mixing them in one window. A browser that keeps each web app in its own window lets an account live in a fixed place instead of behind a tab you have to find. The Workspaces page describes how a set of services and their accounts can be pinned to a single working surface, and the Supported apps page lists which services can be added that way. Questions about how existing sign-ins carry over are covered in the FAQ.

Change one thing first

Decide which of the three rows is actually failing before opening any settings screen. If the menus are wrong, go to macOS Language and Region and set Chrome there. If a page is wrong, use the translation controls. If a web app is wrong, fix it in that service's account settings, and if two accounts keep colliding, give each one its own window with SpaceDeck rather than switching them by hand.