Keyboard shortcuts for Chrome on a Mac, and their limits

Anyone searching for a keyboard shortcut for Chrome has usually already skimmed the official list once and come away with the same feeling: the keys are there, but the thing that actually slows the day down is not on the page. The reachable set is smaller than it looks, a few of the most wanted actions have no binding at all, and the two ways to add your own each carry a hard limit. Knowing where those limits sit saves an evening of trying to script around them.

The reachable set on macOS

Chrome's own documentation splits its Mac shortcuts into four groups, and it is worth reading them as four separate tools rather than one long table.

Tab and window keys move between things that are already open. Command + T opens a tab, Command + W closes one, Command + Shift + T reopens closed tabs in the order they were closed, and Command + Option + Right arrow or Left arrow steps to the next or previous tab. Command + 1 through Command + 8 jump to a specific tab, and Command + 9 jumps to the last one.

Feature keys reach parts of the browser rather than parts of a page. Command + Shift + B shows or hides the bookmarks bar, Command + Y opens history, Command + Shift + J opens downloads, and Command + comma opens settings. Command + Shift + M opens the panel for switching user, browsing as a guest, and reaching saved passwords and payment details.

Address bar keys are the fastest route in the whole list and the most underused. Command + L puts the cursor in the address field. Typing a search engine name and pressing Tab searches that site directly, which turns the address field into a launcher for any site with its own search.

Page keys act on the document: Command + F to find, Command + D to bookmark, Command + Shift + D to bookmark every open tab into one folder, Command + P to print. Two less familiar ones are worth adding: Control + F2 moves focus to the main menu bar, and Command + Option + N opens split view in the active tab.

Where the tab keys stop scaling

The tab shortcuts were designed for a browser holding a handful of pages, and that assumption shows.

Command + 1 through Command + 8 addresses eight positions. Command + 9 is not the ninth tab; it is the last one, whatever number that happens to be. So direct access covers nine tabs at most, and only while nothing moves. Open one page in the middle of the strip and every number after it shifts, which means the muscle memory built over a week is wrong the moment a link opens in the wrong place.

Command + Option + arrow keys have no such ceiling, but they are serial. Reaching the twenty third tab means twenty two presses, or a guess and a correction. That is not faster than the mouse, and for most people it is slower, because the mouse at least has the favicon as a target.

What is left is Command + Shift + A, which opens the tab search list, and typing part of the title. It works, and it is the honest answer for a browser with forty tabs, but it is a search, not a shortcut. Two keystrokes plus a query plus a selection is a different kind of action from a single binding that lands somewhere known.

The pattern behind all three is the same. Tab shortcuts address position, and position is unstable. Anything that is open all day, such as a chat client or a mail client, deserves an address that does not move, and no tab based key can offer one.

The keys Chrome does not have on a Mac

Three absences send people looking for third party fixes.

There is no built in key that switches directly to another profile. Command + Shift + M opens the panel, and the choice is then made with the pointer or the arrow keys. The Profiles menu in the Mac menu bar lists each profile by name, which matters for the custom route described below.

Tab groups have no key bindings on macOS. Chrome's documentation describes group handling on the Mac through VoiceOver focus navigation rather than through a combination, in contrast to Windows and ChromeOS, which have documented sequences. Anyone who organises work by tab group on a Mac is using the mouse for it.

There is no key that jumps to a named site. Bookmarks in the bar can be opened with the pointer, but a bookmark inside a folder has no address a key can reach. This is the absence that hurts most, because "go to the ticket queue" is what people actually want to bind.

A fourth gap is easy to miss because it looks solved. Command + Shift + T restores closed tabs in order, which covers the accidental close, but there is no key that reopens a specific window, and no key that moves the current tab into another window. Both of those are pointer work, and both come up constantly for anyone who separates work by window rather than by tab position.

Two ways to add your own

Both routes are documented, and both come with a boundary that decides which one applies.

The first is Chrome's own extension shortcut dialog at chrome://extensions/shortcuts. Every installed extension lists its commands there, and any of them can be given a combination. Chrome's developer documentation notes that an extension may suggest at most four default shortcuts, that users can add more from that dialog, and that a command shortcut must include Ctrl or Alt, with Command or Option accepted in their place on macOS. A command can also be marked global so it fires while Chrome is in the background, and those are limited to Ctrl + Shift + a digit to avoid stealing keys from other applications.

The second is macOS App Shortcuts, in System Settings under Keyboard, Keyboard Shortcuts. A combination is matched to the exact text of a menu item in a chosen application. Apple's guidance is explicit about the ceiling: shortcuts can be created only for existing menu commands. If the action is not written as text in a menu, no combination can reach it.

Getting the menu title right is where most attempts fail. Apple's instructions require the text exactly as the application prints it, including punctuation, and a nested command is written with the levels joined by an arrow typed as a hyphen and a greater than sign. An ellipsis has to be typed as three separate periods rather than as the single character the menu appears to use. One wrong space produces an entry that looks correct in the settings list and does nothing at all in the browser.

Conflicts are the second failure. macOS gives system level bindings priority, and a handful of combinations are already taken by Spotlight, screenshots, Mission Control, and input source switching. A newly assigned key that appears to do nothing is often being intercepted before Chrome ever sees it, which can be confirmed in Keyboard Shortcuts by looking at the system categories in the same panel. Choosing combinations with Control and Option together avoids most of the crowded space, at the cost of a slightly awkward hand position.

Route	Reaches	Breaks when
Extension shortcuts	Commands an extension declares	The extension is removed or updated
macOS App Shortcuts	Any menu item, by exact title	The menu wording changes
Built in Chrome keys	A fixed list, unchangeable	Never, but cannot be extended

The practical reading of that table is that App Shortcuts is the more durable of the two custom routes, because it depends on the browser's own menus rather than on third party code. Its weakness is brittleness of a different kind: rename a profile, or update to a version that rewords a menu item, and the binding silently stops working with no error to explain why.

What the extension route lost

For years the standard answer to a missing shortcut was an extension. That answer got narrower.

Chrome's own deprecation timeline sets out the sequence. Manifest V2 extensions were disabled for all users on all channels with Chrome 138 in July 2025, and support was removed outright in Chrome 139, at which point the enterprise policy that had kept them alive was gone. On 31 August 2026 the remaining Manifest V2 extensions were removed from the Chrome Web Store.

For shortcut and tab management extensions this matters more than for most categories, because many of them were small, old, and no longer maintained. An extension that has not shipped an update since 2023 is not coming back, and a replacement written against the current platform may not have the same keys or the same behaviour.

The lesson is not that extensions are a bad idea. It is that a keyboard layout built entirely on third party code is rented, not owned. Anything load bearing, meaning the two or three combinations used hundreds of times a day, is safer in the browser's own bindings or in App Shortcuts, where nothing can be delisted from underneath it.

The jump that no key can make

Underneath all of this sits one problem the shortcut list cannot solve. Command + Tab moves between applications. Command + grave accent, the key above Tab, switches between the windows of the application in front. Both are fast, both are already in muscle memory, and neither can reach a web application, because a web application is not an application. It is a tab inside one.

That is why the shortcut hunt so often ends in disappointment. The action people want is "go to chat", and the browser can only offer "go to tab position seven", which is a different and less stable thing. No amount of remapping closes that gap, because the gap is in what the units are, not in which keys are assigned.

The alternative is to change the unit. When each web app gets its own window and its own session, the system level switchers start addressing them directly, and a browser organised into per app workspaces is built on exactly that premise. For anyone whose day is mostly keyboard driven, the feature list is the place to check which actions become window level, and the built in terminal is worth a look for the same reason: fewer trips to another application in the first place.

What to change first

Pick the two or three actions repeated most often and give them stable addresses, starting with App Shortcuts matched to menu titles, since those survive extension churn. Learn Command + L and search engine keywords before adding anything custom, because the address field already reaches more places than most people's shortcut sheets. If the actions being chased are really "go to a specific web app", the fix is structural rather than a binding, and SpaceDeck approaches it from that side.