Firefox Ctrl+Tab jumps to recent tabs: choose adjacent or recently used order
By ON Lab · Sources checked November 8, 2026
Firefox documents a setting that makes Control+Tab cycle through recently used tabs instead of their position in the window. To use Control+Tab for the adjacent tab and Control+Shift+Tab for the previous tab, clear that setting. Verify it with a visit order that differs from the tabs' visual order, rather than relying on two tabs that behave the same either way.
A historical reader wanted the earlier adjacent-tab behavior instead of a switcher-like sequence. We checked Mozilla's current tab settings page, which explicitly documents the two orders. This is an official-source guide: we did not change a Firefox installation or reproduce the reader's operating system.
Find the setting in your current layout
Open Firefox Settings and find the Tabs area. In the current Mozilla page checked for this guide, the navigation section is Tabs and browsing, with the relevant option in the Interaction portion of Tabs. The label is Ctrl+Tab cycles through tabs in recently used order.
Mozilla's current note says to clear the checkbox for adjacent-tab Control+Tab and previous-tab Control+Shift+Tab behavior. Select it when you deliberately want the visit-history order. Read the label in your installed version; older help answers may describe an earlier settings layout.
The source page displayed a macOS-specific route through the Firefox menu to Settings, while the setting itself describes the Control+Tab shortcut. Do not substitute Command+Tab, which is an operating-system application-switching shortcut on macOS. Use the shortcut and setting documented for Firefox.
Verify with three harmless tabs
- Keep any real work open and use a few harmless pages for the comparison.
- Arrange three tabs in an obvious left-to-right order, such as A, B and C.
- Click A, then C, then B so the recent visit order differs from the visual order.
- Use the intended keyboard shortcut and observe which tab receives focus.
- After changing the setting, repeat the same visit pattern and compare the result.
This is a suggested verification, not a claim that we executed it in Firefox. The deliberately different visit order makes the preference observable. With only two tabs, toggling between them can look identical under both rules.
Keep three different controls separate
| Observed behavior | Relevant question |
|---|---|
| Keyboard cycling follows recent visits | Is the recently used order setting selected? |
| A thumbnail appears when the pointer rests on a tab | Is the separate mouse-hover preview setting selected? |
| A new link becomes active immediately | What is the new-tab foreground switching preference? |
Mozilla lists these as separate tab preferences. Clearing a hover-preview option is not evidence that keyboard traversal order changed. Likewise, choosing adjacent traversal does not establish how a link from another application will open.
This guide answers the reader's order question. If your requirement is specifically to keep recently used order while changing a keyboard switcher's visual presentation, that is a different requirement. We did not verify an advanced preference for that combination and do not infer it from an older forum answer.
If the documented setting does not explain the result
Record the Firefox version, operating system, setting state, exact key combination and observed tab sequence. Confirm the browser has keyboard focus and repeat with ordinary pages. Keep a shortcut interception or a version-specific regression separate from the documented order choice.
Do not downgrade Firefox or edit several advanced preferences merely because a historical answer names an old preference. Start with the supported visible setting and a repeatable comparison. If the setting is already clear but adjacent traversal still fails, the general instruction above has not established the cause of your specific failure.
Changing the tab order does not close tabs, restore a lost session or modify the page content. If the real problem is missing tabs after a restart, preserve that symptom as a separate session-restoration investigation. A traversal-order setting has not established why a session was lost.
Checked November 8, 2026 against current Mozilla documentation. No Firefox settings or user tabs were changed for this article. The historical reader question supplies the order preference, not current demand measurements or proof of every Firefox version's behavior.