How to Search in Windows Terminal Output

Windows Terminal is the modern command-line host for PowerShell, Command Prompt, and WSL, but scrolling through long output to find a specific error or value can waste time. This guide shows you the built-in search feature that lets you jump instantly to any text in the current terminal buffer, plus keyboard shortcuts and tips to make searching faster and more reliable.

What You’ll Need

• A PC running Windows 10 version 1903 or later, or Windows 11 (Windows Terminal is preinstalled, but you can also install it from the Microsoft Store).
• A terminal window with some output you want to search (for example, run systeminfo or dir to generate text).
• Basic familiarity with keyboard shortcuts (Ctrl, Shift, Enter).

Step-by-Step

1. Open Windows Terminal. Press Win and type “Terminal”, then press Enter. If you have multiple profiles (PowerShell, CMD, etc.), select the one you want.
2. Generate or display the output you want to search. Run a command that produces enough text, like ipconfig /all or Get-Process | Format-Table. The search works on whatever is currently visible in the scrollback buffer.
3. Open the search box. Press Ctrl + Shift + F. A small search bar appears at the top of the terminal window. (If you’re using an older version, you might need to right-click the title bar and select “Search”.)
4. Type your search term. Enter the exact text you’re looking for. The search is case-insensitive by default, so “error” matches “Error” and “ERROR”.
5. Press Enter to find the next match. The terminal highlights the first occurrence after your current cursor position and scrolls to it. Press Enter again to jump to the next match.
6. Use Shift+Enter to search backward. If you’ve gone too far, or want to find the previous match, hold Shift and press Enter. This moves to the previous occurrence.
7. Close the search box. Press Esc or click the X on the search bar. The highlight remains on the last found match, but you can continue working normally.
8. Use the match counter (if available). In newer versions of Windows Terminal, the search box shows something like “3/15” indicating which match you’re on and the total number of matches. This helps you know how many occurrences exist.
9. Toggle case sensitivity (optional). If you need an exact case match, click the “Aa” icon in the search bar (or press Alt + C while the search box is open). This is useful for searching for variable names like userID vs userid.
10. Search within a specific pane (if you use split panes). The search only works in the active pane. Click on the pane you want to search first, then press Ctrl + Shift + F.

Common Mistakes

• Forgetting that search is per-pane. If you have multiple panes open, the search only looks at the pane that has focus. Click on the correct pane before searching.
• Assuming search covers the entire scrollback. Windows Terminal’s search only looks at the text that has been output in the current session. If you cleared the screen with cls or Clear-Host, that text is gone and cannot be searched.
• Using Ctrl+F out of habit. In Windows Terminal, Ctrl+F is often used by the shell itself (e.g., in PowerShell it may invoke history search or nothing). The correct shortcut is Ctrl+Shift+F.
• Not closing the search box before typing commands. If the search box is open, your keystrokes go into the search field, not the terminal. Press Esc to close it first.
• Expecting regex or wildcard support. The built-in search treats your input as plain text. It does not support regular expressions or wildcards like * or ?. For regex, you’d need to use Select-String in PowerShell or findstr in CMD.

Tips

• Use the scrollback buffer wisely. The more output you have, the more there is to search. If you expect to search later, avoid clearing the screen. You can also increase the buffer size in settings (Settings > Profile > Appearance > “Scrollback lines”).
• Search for unique fragments. Instead of searching for “error”, search for a specific error code like “0x80070005” or a filename. This reduces the number of matches and gets you to the right spot faster.
• Combine with Select-String for advanced needs. If you need regex or want to search across multiple commands’ output, pipe the output to Select-String (PowerShell) or use findstr (CMD). For example: ipconfig | Select-String "IPv4".
• Use the mouse to select and search. You can also select text with the mouse and then press Ctrl+Shift+F; the selected text is automatically placed in the search box (in newer versions).
• Memorize the shortcuts. Ctrl+Shift+F opens search, Enter next, Shift+Enter previous, Esc closes. These are the core ones.
• Search in WSL too. The same shortcut works in WSL (Windows Subsystem for Linux) sessions within Windows Terminal, so you can search the output of grep or ls without leaving the terminal.

Troubleshooting

• The search box doesn’t open. Make sure you’re using a recent version of Windows Terminal. Check for updates via the Microsoft Store or GitHub. If you’re on an older build, try right-clicking the title bar and selecting “Search”.
• Search finds nothing, but the text is on screen. Check if the text is actually in the terminal buffer. If you’re using a full-screen application like Vim or a game, the output might not be in the scrollback. Exit the full-screen app first. Also, ensure the pane has focus.
• The match counter shows “0/0”. This usually means the search term is not present, or the buffer is empty. Try a simpler term or check that you haven’t accidentally cleared the buffer.
• Search is slow on huge outputs. If you have tens of thousands of lines, searching may take a moment. Be patient, or reduce the scrollback size in settings. Alternatively, use findstr or Select-String to filter output before it overwhelms the buffer.
• Keyboard shortcut conflicts with a shell. Some shells or tools might intercept Ctrl+Shift+F. In that case, you can change the shortcut in Windows Terminal settings under Actions. Search for “Search” and assign a new key combination.
• Search doesn’t wrap around. By default, search wraps from the bottom to the top. If you don’t want wrapping, there’s no built-in toggle; but you can press Shift+Enter to go backward if you overshoot.

Frequently Asked Questions

Q: Can I search in all panes at once?
A: No, the built-in search only works in the active pane. You must click on each pane and search separately.

Q: Does the search work in PowerShell, CMD, and WSL equally?
A: Yes, because it’s a feature of Windows Terminal itself, not the shell. The same shortcut works in all profiles.

Q: Can I use regular expressions in the search?
A: No, the built-in search is plain text only. For regex, use Select-String in PowerShell or findstr in CMD.

Q: How do I search for text that contains spaces?
A: Just type the whole phrase including spaces. For example, “IPv4 Address” works as a single search term.

Q: Is there a way to search the entire command history?
A: Not with the built-in search. Use Get-History in PowerShell or doskey /history in CMD, then pipe to Select-String or findstr.

Q: Why does my search not find text that was just printed?
A: The search only looks at the current buffer. If the output was very long and scrolled off the top, it’s still in the buffer (unless you cleared it). If you used cls, it’s gone. Also, ensure the text is not in a different pane.

Related

• Fix Microsoft Word Crashes and Freezes on Windows
• How to Lock Apps on iPhone (iOS 17 & 18)
• Windows To Go USB: Step-by-Step Setup Guide