How to Change Tabs With a Keyboard: Shortcuts for Every Browser and OS

Switching between browser tabs using a mouse works fine — until you're moving fast, managing a dozen open tabs, or simply want to keep your hands on the keyboard. Keyboard shortcuts for tab navigation exist across every major browser and operating system, and once you internalize them, they become second nature. The right shortcut depends on your OS, browser, and what you're actually trying to do.

Why Keyboard Tab Switching Matters

Every click to reach the mouse is a small interruption. For developers, writers, researchers, or anyone working across multiple sources at once, tab-switching shortcuts reduce friction in a measurable way. They also matter for accessibility — users who rely on keyboards rather than pointing devices need consistent, reliable navigation.

The good news: browser developers have largely standardized these shortcuts. The nuance is in the variations.

The Core Shortcuts: Windows and Linux 🖥️

On Windows and most Linux distributions, these shortcuts work in Chrome, Firefox, Edge, Opera, and Brave:

Ctrl + Tab cycles forward through your tab bar, left to right. Ctrl + Shift + Tab cycles backward. These work regardless of how many tabs are open.

The numbered shortcuts (Ctrl + 1 through Ctrl + 8) jump directly to a tab by its position — the first tab, second tab, and so on. Ctrl + 9 is a special case: it always jumps to the last tab, not necessarily the ninth one.

The Core Shortcuts: macOS 🍎

On Mac, the modifier key changes, but the logic is identical:

Safari uses Cmd + Option + → and Cmd + Option + ← as its primary tab navigation shortcuts, while Chrome and Firefox on Mac also accept Ctrl + Tab (using the Control key, not Command). This distinction catches people out when switching browsers.

Browser-Specific Differences Worth Knowing

While most major browsers align on the basics, a few distinctions affect how shortcuts behave in practice.

Firefox adds one useful variation: Ctrl + Tab (Windows) can be configured to cycle through tabs in recently used order rather than left-to-right order. This setting lives in Firefox's preferences under General → Tabs. Depending on how you work, recently-used ordering can feel more intuitive — or more disorienting.

Safari does not support Ctrl + Tab in the same way other browsers do by default. Its tab navigation is tied more tightly to the Cmd + Option + Arrow pattern, and some shortcuts require enabling full keyboard access in macOS System Settings under Accessibility.

Chrome and Edge behave nearly identically for tab shortcuts, which makes sense given their shared Chromium foundation.

Switching Tabs in Non-Browser Contexts

The concept extends beyond browsers. Tab switching with a keyboard appears in:

• Code editors (VS Code, Sublime Text, JetBrains IDEs): typically Ctrl + Tab or Ctrl + Page Up / Page Down
• Terminal emulators (like Windows Terminal or iTerm2): usually Ctrl + Tab or configurable shortcuts
• Spreadsheet and document apps (Excel, Google Sheets): Ctrl + Page Up / Page Down moves between sheet tabs
• Operating system app switchers: Alt + Tab (Windows) and Cmd + Tab (Mac) switch between application windows, not browser tabs specifically

Each environment has its own convention, and some allow full customization. The shortcut that works in Chrome won't necessarily work in your IDE or terminal.

Variables That Affect Which Shortcut You Need

No single answer fits every setup. Several factors determine which shortcuts are relevant to you:

Operating system is the most obvious variable. The Mac/Windows split in modifier keys (Cmd vs Ctrl) is fundamental, and Linux distributions can vary depending on the desktop environment.

Browser choice matters, particularly if you use Safari, which diverges from the Chromium-based norm. Firefox's optional recently-used tab cycling is a meaningful behavioral difference if you frequently return to tabs you used moments ago rather than navigating sequentially.

Keyboard layout and hardware can create friction. Some compact keyboards, 60% layouts, or laptop keyboards require additional key combinations to access function keys or certain modifiers, which can conflict with tab shortcuts or require remapping.

Accessibility settings on macOS in particular can affect whether keyboard navigation works as expected across UI elements, including tabs.

Application type changes everything. A shortcut that's muscle memory in Chrome is likely irrelevant inside a terminal or document editor, which has its own tab model and shortcut set.

Customizing and Remapping

If the defaults don't match how you work, most environments offer some level of customization:

• Browsers: Extensions like Vimium (Chrome/Firefox) let you remap tab navigation entirely, including vim-style gt and gT bindings
• VS Code: Full keybinding customization via Ctrl + K, Ctrl + S (Windows) or Cmd + K, Cmd + S (Mac)
• macOS: System-level keyboard shortcut remapping in System Settings → Keyboard → Keyboard Shortcuts
• Windows: Tools like AutoHotkey allow custom remapping at the OS level

How much customization makes sense depends on how many environments you work in and whether consistent shortcuts across all of them matter to you.

The shortcuts are well-documented and largely standardized — but which ones are worth learning, and whether the defaults serve you or need adjusting, comes down to your specific workflow, the tools you spend the most time in, and how your hardware is configured. ⌨️