Direct answer

The short version

Command-Tab switches to a running application. It does not promise which of that app’s windows, tabs, files, or documents will be active. If the app is correct but the window is wrong, use Command–grave accent, the Window menu, App Exposé, Mission Control, or a window-aware history.

Key takeaways

  • The app switcher and window switcher operate at different layers.
  • Minimized, full-screen, hidden, and multi-Space windows can change what becomes visible.
  • Browser tabs and editor files are nested below the window layer.
  • Choose a window control immediately after the correct app activates.

Command-Tab stops at the application layer

Apple describes Command-Tab as switching among open apps. An app can own multiple standard windows, full-screen windows, minimized windows, panels, and windows distributed across desktop Spaces. The app and macOS determine which available window comes forward.

That behavior is not evidence that the app switcher lost a detailed window history. Detailed window selection is a separate task and has separate controls.

  • Known app: Command-Tab.
  • Another window in the active app: Command–grave accent or Window menu.
  • Visually recognizable window: App Exposé or Mission Control.
  • Known tab, file, or document: use the app’s picker or search.
  • Previous chronological location: navigation history.

Check Spaces, full-screen state, and minimized windows

A target window may live in another Space or full-screen desktop. Mission Control reveals that structure. A minimized window may require selection from the Dock or Window menu, and some apps handle minimized or closed-last-window states differently.

Multiple monitors add another spatial clue but not a permanent identity. Displays disconnect, Spaces move, and windows can be rearranged, so verify the window title and content rather than relying only on screen position.

Recover the intended context in two layers

First select the app, then select the window or nested object. If this happens repeatedly, name project windows and reduce indistinguishable duplicates. For a recent detour, window-aware chronological history can skip manual scanning.

ReturnFast can match windows and provides deeper restoration in supported browsers, editors, and Finder. When only window-level data is available, app-native controls remain the final step to a tab, thread, pane, or document position.

  1. Confirm the app

    If Command-Tab chose the wrong app, repeat the app selection.

  2. Select its window

    Use window cycling, the Window menu, App Exposé, or Mission Control.

  3. Select nested state

    Use tabs, Quick Open, sidebars, or in-app history for the final object.

Further reading and product details

Apple’s official window guideReview Command-Tab, Command–grave accent, Mission Control, and App Exposé.Mac window switching field guideChoose the right control at the app, window, and nested-content layers.Command-Tab vs Command–grave accentCompare application switching with current-app window cycling.

Frequently asked questions

Can Command-Tab choose a specific window?

Its primary selection unit is the application. Use a window-specific control after activating the app.

What is the shortcut for another window in the current app?

Command–grave accent commonly cycles windows in the active app, but keyboard layout, app behavior, and customized shortcuts can affect it.

Why is the browser window correct but the tab wrong?

Tabs are nested inside the window and are not selected by Command-Tab. Use the browser tab strip, tab search, or tab history.