What's new in 18.11
Microsoft's October Update 18.11.0 release notes say you can reorder the active tab in the document well without the mouse. Separately, Ctrl+NumPad1 through Ctrl+NumPad9 activate the matching visible document tab in the active document group.
The first feature is about arrangement and the second is about recall. You put two or three working files side by side, then reach each one by position instead of cycling through every open tab.
Moving the active tab
Press Ctrl+Shift+PgUp to move the active tab one visual position left. Press Ctrl+Shift+PgDn to move it one position right. Microsoft's shortcut reference says these commands reorder tabs without switching focus. The tab you are on moves, and you stay on it. Ctrl+PgUp and Ctrl+PgDn still do the switching.
- Vertical tabs: The same shortcuts move the tab up or down.
- Tool windows: They work for documents and for tool windows hosted in the document well.
Where movement stops
The commands work inside your existing layout rather than overriding it. Microsoft's documentation lists these limits:
- Movement preserves the boundary between pinned and unpinned tabs. Your pinned set can't be broken by accident.
- With vertical tabs, a tab stays within its project group.
- Manual reordering is unavailable when alphabetical sorting is enabled.
- Preview tabs can't be moved.
If the shortcut seems to do nothing, check these four conditions first. A preview tab, an alphabetical sort setting, or a tab already at its pinned or project-group edge are the likely causes. That is my inference from the documented rules, not a Microsoft troubleshooting list.
Jumping to a tab by position
Numbering follows the document well's visual order and counts both pinned and unpinned tabs. Preview tabs don't use up a slot, and switching to another document group changes the mapping. The daily.dev summary of Microsoft's post puts it well: the numbers target positions, not filenames.
Moving a tab changes which file sits at, say, position 2. The same number can also point to a different file in another document group. Arrange first, then navigate.
A short workflow
- Open the two or three files you need for the task, such as a class, its test file and an interface.
- Make sure none of them is a preview tab. Edit the file or open it explicitly from Solution Explorer.
- Move each tab into the order you want with Ctrl+Shift+PgUp and Ctrl+Shift+PgDn.
- Use Ctrl+NumPad1, Ctrl+NumPad2 and so on to switch between them.
- If you change document groups, recheck the order before trusting the numbers.
Note that the shortcuts use the NumPad keys. Microsoft's release notes mention keyboards without a number pad in another context, the zoom-reset shortcut, and say you can remap in the Keyboard options page. The numbered-tab commands are documented as Ctrl+NumPad shortcuts. If your laptop lacks a number pad, check the Keyboard options page for an alternative binding. I haven't verified the exact command names for the numbered shortcuts, so I won't guess at them.
The shortcut conflict
The new defaults take over the earlier Text Editor bindings for Edit.ViewTopExtend and Edit.ViewBottomExtend. Microsoft's reference says Ctrl+Shift+PgUp and Ctrl+Shift+PgDn now move tabs, and that the editor commands remain available. Those two commands previously extended the selection to the top or bottom of the view. If that was part of your editing routine, you will notice.
To fix it, open Tools > Options > Environment > Keyboard. There you can reassign either the move commands (Window.MoveTabLeft and Window.MoveTabRight) or the editor commands. The documentation doesn't say what happens to a customized keymap on upgrade. Check your own bindings after updating rather than assuming they survive.
Context
This is a familiar convention. Microsoft's release notes say Ctrl+Shift+PgUp/PgDn is the same binding most browsers use. VS Code's shortcut sheet lists the same keys for moving an editor left or right. Developers who split time between the two tools get a more consistent habit.
Microsoft's notes thank people who voted for the feature on Developer Community. It is a small change, but a frequently requested one. Mads Kristensen's blog post also mentions separate tool-window tab sizing, a uniform 24-pixel tab height and high-contrast fixes. I couldn't verify those against Microsoft Learn, so treat them as claims from the blog post alone.
Bottom line
- Requires: Visual Studio 2026 version 18.11 or later.
- Move tab: Ctrl+Shift+PgUp for left or up, Ctrl+Shift+PgDn for right or down.
- Jump to tab: Ctrl+NumPad1 to Ctrl+NumPad9, by visual position in the active group.
- Watch for: preview tabs, alphabetical sorting, pinned and project-group boundaries, and the displaced Edit.ViewTopExtend and Edit.ViewBottomExtend bindings.
It won't change how you write code. It will spare you a few mouse trips an hour, and that is the kind of small saving that adds up over a long working day.