Xcode keyboard shortcuts for Mac

Every other app on this site has a shortcut reference with its vendor's name on it. Xcode does not. Apple's current documentation explains how to view, change and resolve conflicts between key bindings, and stops there — it does not print the combinations themselves, in Xcode Help or in the developer documentation.

The only shortcut tables Apple ever published for Xcode sit in a retired document that was last updated in 2011, for an Xcode several major versions behind anything you can install today. A stale chord is worse than no chord: it is the one thing on a reference page a reader will actually test, and it fails in front of them.

Xcode being Mac-only removes the usual trap, which is a Windows list quietly translated into ⌘ symbols. It replaces it with a subtler one. Apple moves bindings between major releases, so a combination someone blogged about two Xcode versions ago may now belong to a different command entirely — and there is no published list to check it against.

Apple publishes no static shortcut reference for Xcode, so every chord below was read from Xcode's own Key Bindings pane in Xcode 26.6 (build 24959) — the authoritative list for any installation — rather than from a document.

That is a stronger source than it sounds, not a weaker one. The pane is not a description of Xcode's shortcuts written by somebody; it is the mechanism, the thing Xcode actually consults when you press a key. A published table can drift out of date without anyone noticing. The pane cannot.

It does mean the list is a snapshot of one installation, and yours can legitimately differ. A custom key bindings set, a set you duplicated and forgot to switch back from, a changed binding, or a system-wide shortcut claiming a combination first will all move things around. That is exactly why the pane, and not this page, is the last word — and the walkthrough below shows how to read yours in about a minute.

⇧⌘O — Open Quickly — is the chord that replaces the project navigator entirely. It matches file names and symbol names at once, so a class you can half remember is two seconds away without knowing which group it lives in.

The two history chords are the ones that make jumping safe. ⌃⌘← walks back to where you were before the last jump and ⌃⌘→ walks forward again, which is what lets you chase a definition four files deep and get home. The numbered ⌘ chords select navigators rather than files.

⌃I is the chord to reach for after every paste. It re-indents the selection to the file's own rules, which is faster and more predictable than fighting the editor line by line, and it is why pasted code stops looking pasted.

⌘/ comments the selection and uncomments it again on a second press, and ⌥⌘/ generates a documentation comment for the declaration under the cursor — parameter names, return value and all. The four format commands are separate from re-indenting, and act on a width, a selection or the whole file.

Folding in Xcode is built on ⌥⌘ plus an arrow, and the modifiers widen the scope rather than change the direction: add ⇧ to fold every method in the file, or ⇧⌃ to fold the comment blocks and leave the code alone.

⇧⌃↑ and ⇧⌃↓ extend a rectangular column selection, which is the fastest way to add the same suffix to twelve lines of a Swift enum. The three view toggles at the bottom of the table are the ones worth knowing before a demo, because a minimap and an authors gutter both eat width you may want back.

Xcode keeps two parallel find systems and gives the workspace-wide one an extra modifier: ⌘F finds in the file, ⇧⌘F finds across the workspace, and the same pattern holds for replace and for stepping through results.

⌘E is the chord that pays for itself. It loads the current selection into the find buffer, so the sequence select, ⌘E, ⌘G finds the next occurrence of whatever your cursor is on without ever opening the find bar. ⇧⌃⌘F does the same at workspace scale for a symbol, and ⇧⌃⌘H opens its call hierarchy.

⌘B builds, ⌘R runs, ⌘U tests and ⌘. stops whatever is going — four chords that cover most of a working day. The variants with ⌃ skip the build step, which is how you re-run a binary you already have without waiting for a compile you know is unnecessary.

⇧⌘K cleans the build folder and asks first; ⇧⌥⌘K cleans immediately without the dialog. Reach for the second one only when you mean it, because it is the fastest way to throw away a derived data cache you would rather have kept.

The stepping keys are F6, F7 and F8, which on a Mac laptop means fn is part of the chord unless you have turned on the option to use the top row as standard function keys in System Settings under Keyboard. That one setting is what makes the debugger usable from the keyboard.

⌘\ sets a breakpoint on the current line without aiming at the gutter, ⌘Y deactivates every breakpoint at once when you want a clean run, and ⌃⌘C continues to wherever the cursor happens to be — a one-shot breakpoint you never have to remove.

Xcode has three nested things that all look like tabs — window tabs, editor tabs and editor panes — and the New menu gives each its own chord. ⌘T adds a tab, ⌃⌘T opens an editor pane to the right, and ⌥⌃⌘T opens one below.

⌘W is deliberately vague, and the menu item says so in as many words: it closes the tab, the editor pane, the window tab or the window, whichever is innermost. When you need to be precise, the ⌥, ⌃ and ⇧ variants each name exactly one of them.

This takes about a minute and leaves you with a list that is correct for your Xcode, on your keyboard, including anything you changed and forgot about. It is worth doing once before a talk or a recording rather than discovering a conflict live.

The controls below are the whole interface, and two of them do more than they look like they do. The search options icon lets you search by combination rather than by name, and the Conflicts filter answers the most common complaint about Xcode shortcuts without any guesswork.

Four things account for almost every report that an Xcode shortcut is broken, and the Key Bindings pane settles three of them without any guessing.

Xcode is an unusually bad app to watch someone else drive. The chords run three and four modifiers deep — ⇧⌥⌃I is four — and the visible result is often a subtle reformat or a jump to a file the viewer has never seen. If you are recording a Swift tutorial, running onboarding for a new iOS hire, or pairing over a screen share, the keyboard is the half of the story that never makes it onto the video, and since Apple publishes no list, a viewer cannot look the combination up afterwards either.

Show KeyPress is a paid macOS menu bar app, for macOS 14 Sonoma or later, that draws each key you press as a keycap on top of everything else on screen. There is no Xcode plugin, no source editor extension and no recording of its own — it is a window above your other windows, which is why any display capture picks it up without being told to.