To collapse the preview pane in Visual Studio Code, you can use the dedicated toggle command or a keyboard shortcut. The most reliable method is using
Ctrl+K followed by
P on Windows/Linux or
Cmd+K then
P on macOS. This action hides the peek view without closing the file, allowing you to reclaim screen space while keeping the context accessible for quick edits.
Understanding the Peek View
The preview feature in VSCode is designed for quick inspections rather than full editing sessions. When you open a file from an external reference, such as a definition in code or a link in documentation, it opens in a "peek" window. This window is smaller and typically displays only the relevant lines of code. Understanding this distinction is crucial because standard window management commands like
Alt+F4 or clicking the close button will permanently close the file tab, whereas the preview toggle simply hides the overlay. Many users confuse these two states, leading to frustration when they cannot find their recently viewed file.
Keyboard Shortcuts for Toggling Preview
Using keyboard shortcuts is the fastest way to manage your workspace layout. VSCode allows you to toggle the preview pane without moving your hands away from the home row. On Windows and Linux, press
Ctrl+K, release both keys, and then press
P. On macOS, use
Cmd+K followed by
P. If you prefer a single key combination, you can search for the command
Peek: Toggle Peek in the command palette. This command directly controls the visibility of the preview pane. It is important to note that this does not affect the main editor area where your primary files are located.
Customizing the Shortcut
If the default keybinding conflicts with your workflow, you can change it. Open the Keyboard Shortcuts editor by pressing
Ctrl+Shift+P (or
Cmd+Shift+P on Mac) and typing
Preferences: Open Keyboard Shortcuts. Search for
Peek: Toggle Peek and assign a new key combination. This ensures that you can quickly hide the preview pane whenever it becomes distracting during long coding sessions. For more information on navigating your code efficiently, consider reading
Navigating Among Functions in Visual Studio Code for .sh Files.
Configuring Auto-Peek Behavior
By default, VSCode automatically opens certain files in preview mode if you have other files open. This behavior helps keep the sidebar clean but can be annoying if you frequently need to edit those files. You can control this setting via the user settings. Access the settings by pressing
Ctrl+, (or
Cmd+, on Mac). Search for
workbench.editor.enablePreview. Setting this to
false disables the auto-preview feature entirely. All files will then open in regular tabs instead of the peek view. This is useful for developers who prefer a traditional tab-based workflow over the peek interface.
Disabling Peek from References
Another related setting is
workbench.editor.enablePreviewFromOpenFiles. However, this specific setting has been deprecated or removed in recent versions of VSCode. Instead, focus on the general
enablePreview setting. If you still encounter issues with files opening in preview unexpectedly, check your workspace settings for any overrides. Some extensions may also influence how files are opened, so disabling unnecessary extensions can help stabilize the behavior. For troubleshooting launch issues that might interfere with settings, see
Visual Studio Code Not Launching: Troubleshooting with No Diagnostics.
Alternative Methods to Manage Space
While toggling the preview is the direct solution, there are alternative ways to manage your visual space. You can minimize the sidebar by pressing
Ctrl+B (or
Cmd+B). This hides the entire explorer panel, giving you more room for the main editor. Additionally, you can enter Zen Mode by pressing
Ctrl+K Z (or
Cmd+K Z), which hides all UI elements except the editor. This is ideal for deep work sessions where distractions must be minimized. These methods provide flexibility depending on your current task requirements.
Why Your Preview Might Not Close
Sometimes users report that the preview pane refuses to close despite pressing the correct keys. This usually happens when multiple peek views are open simultaneously. VSCode allows you to open several definitions at once, stacking them in the same area. To resolve this, you must close each peek view individually. Look for the small X icon in the top right corner of each peek window. Alternatively, use the
Peek: Hide Peek Widget command repeatedly until all instances are cleared. Ensuring no background processes or extensions are interfering is also recommended.
Frequently Asked Questions
How do I permanently disable preview mode?
You can disable preview mode by setting
workbench.editor.enablePreview to false in your user settings. This forces all files to open as regular tabs, eliminating the peek view behavior entirely.
What is the difference between peek view and normal tabs?
Peek views are temporary overlays used for quick inspection and do not occupy a permanent tab in the editor header. Normal tabs remain open in the tab bar and allow for full editing capabilities and persistent state.
Can I open multiple files in preview mode at once?
Yes, VSCode supports opening multiple peek views simultaneously. Each additional peek view appears stacked within the same area, requiring individual closure or the use of the hide command for each instance.
Does toggling preview close the file?
No, toggling the preview pane only hides the visual overlay. The file remains open in the background and can be accessed again through the tab bar or by reopening the reference.
How do I reset my keyboard shortcuts for peek?
Open the Keyboard Shortcuts editor, search for
Peek: Toggle Peek, and click the trash icon next to your custom binding. This restores the default
Ctrl+K P or
Cmd+K P keybinding.