MORE Command Guide - Display Output One Screen at a Time in Windows

The more command is a Windows Command Prompt utility that displays text output one screen at a time, pausing between pages and allowing you to navigate through large amounts of text. Use more filename.txt to page through file contents, or command | more to paginate any command's output.

Whether you're reading long log files without scrolling endlessly, reviewing large directory listings screen by screen, or examining command output in manageable chunks, mastering the more command provides essential text pagination capabilities directly from the command line. IT professionals and system administrators rely on this command for readable output when working with verbose logs, configuration files, and lengthy command results in terminal sessions.

This comprehensive guide covers more syntax, all interactive options and extended features, practical examples for files and piped output, comparison with similar commands, troubleshooting tips, common use cases, related commands, and frequently asked questions. By the end, you'll confidently page through text output from the command line for more readable terminal sessions and efficient text review.

What Is the More Command?

The more command is a text pagination utility available in all Windows versions since MS-DOS. It displays text one screen (page) at a time with pause controls:

• Screen-by-screen display – Shows one console window of text, then pauses
• Interactive navigation – Press keys to advance, scroll, search, or quit
• Works with files and pipes – Read files directly or paginate any command output
• Extended mode – Advanced features like line numbers, search, and precise scrolling

The command pauses at each screen boundary displaying -- More -- prompt with percentage indicator. Press Space to continue, Enter for line-by-line scrolling, or Q to quit.

More vs. Type Command

Feature	more	type
Pagination	Yes (pauses per screen)	No (dumps all content)
Large file handling	Readable, paginated	Floods screen with text
Interactive navigation	Yes (Space, Enter, Q, etc.)	No
Search capability	Yes (in extended mode)	No
Speed	Slower (interactive)	Faster (no pauses)

When to use more: Large files, lengthy output, interactive reading, searching within output.

When to use type: Small files, piping to other commands, fast non-interactive display.

The command works in Command Prompt (CMD), PowerShell (as external command), and batch scripts. Available in Windows 11, Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP, and all Windows Server editions.

More Command Syntax

The basic syntax for the more command is:

more [/c] [/p] [/s] [/tn] [+n] [file(s)]
command | more [/c] [/p] [/s] [/tn] [+n]

Parameters and Switches

Parameter	Description
file(s)	File(s) to display. Can specify multiple files
/c	Clear screen before displaying page (extended mode)
/p	Expand form-feed characters (page breaks)
/s	Squeeze multiple blank lines into single blank line
/tn	Expand tabs to n spaces (default is 8)
+n	Start displaying from line number n
/?	Display help information

Interactive Commands at -- More -- Prompt

Once paused, use these keys to navigate:

Key	Action
Space	Display next screen (page)
Enter	Display next line (single line scroll)
Q	Quit (exit more command)
=	Show current line number
?	Show available commands (help)
F	Display next file (when multiple files specified)
S n	Skip next n lines, then display screen
P n	Display next n lines

Note: Advanced interactive commands (like search) may not work in all Windows versions. Extended features work best in newer Windows releases.

Displaying Files

Basic File Display

To page through a file:

more readme.txt

Output:

[First screen of text content...]
-- More (45%) --

Press Space to see next screen, Enter for next line, or Q to quit. Percentage shows how much of file has been displayed.

Start from Specific Line

To begin display at a certain line:

more +100 logfile.log

Starts displaying from line 100, skipping the first 99 lines. Useful when you know approximately where relevant content begins in large files.

Display Multiple Files

To page through multiple files sequentially:

more file1.txt file2.txt file3.txt

After reaching end of first file, press F at -- More -- prompt to advance to next file. Useful for reviewing related configuration or log files in sequence.

Clear Screen Between Pages

To clear screen before each page display:

more /c document.txt

Provides cleaner reading experience by removing previous screen content. Helpful when reviewing structured data or code where context per screen matters.

Squeeze Blank Lines

To compress multiple consecutive blank lines:

more /s data.txt

Replaces sequences of blank lines with single blank line. Improves readability of text files with excessive whitespace formatting.

Expand Tabs to Spaces

To control tab width:

more /t4 source.js

Expands tabs to 4 spaces instead of default 8. Essential for code files where indentation matters and default tab width causes misalignment.

Using More with Pipes

Page Directory Listings

To make long directory listings readable:

dir /s | more

Pauses directory output per screen. Essential when listing recursive directories with hundreds of files. Press Space to continue through results.

Page System Information

To review verbose system details:

systeminfo | more

Systeminfo produces 50+ lines; more makes it readable. Navigate section by section instead of scrolling through terminal backlog.

Filter and Page

To combine filtering with pagination:

dir /s | find ".exe" | more

First finds executables, then pages results. Combines search functionality with readable output for large result sets.

Page Network Status

To review network connections without flooding terminal:

netstat -an | more

Netstat can produce hundreds of lines. More allows careful review of each connection, port, and state without missing details.

Page Task Lists

To review running processes readably:

tasklist /v | more

Verbose task list with full details benefits from pagination. Review each screen of processes methodically.

Page Help Output

To read lengthy command help:

help dir | more

Or:

dir /? | more

Makes long help text readable. Many commands have extensive help that overflows single screen.

Practical Examples

Read Log Files

Page through application or system logs:

more C:\Logs\application.log

Review log entries screen by screen. Start from specific date by calculating approximate line number with /+n option.

Review Configuration Files

Examine config files methodically:

more C:\Windows\System32\drivers\etc\hosts

Read system configuration files in controlled manner. Useful for audit or troubleshooting without text editor.

Check Script Contents

Preview batch or PowerShell scripts:

more deploy.bat

Review script logic before execution. Safer than running unknown scripts immediately.

Page Through CSV Data

Review data files:

more sales_data.csv

Examine CSV structure and sample data. Useful for data validation before import operations.

Combine with FIND for Context

Search and display with context:

type largefile.txt | find "ERROR" | more

Find error entries, then page through results. Combines search precision with readable pagination.

Review Environment Variables

Page through environment settings:

set | more

Environment variable list can be lengthy. More makes it readable for review or auditing.

Examine PATH Variable

Review PATH components:

echo %PATH:;=^& echo.% | more

Displays each PATH entry on separate line, paginated. Helps audit or troubleshoot PATH configuration issues.

Read README Files During Installation

Review documentation before proceeding:

more README.txt
pause
install.exe

In installation scripts, let users read documentation before continuing. Professional installer pattern.

Page Through Registry Exports

Review exported registry settings:

more registry_backup.reg

Examine registry entries before importing. Safer import workflow when reviewing changes.

Review Text-Based Reports

Display generated reports:

more monthly_report.txt

Read formatted text reports in terminal. Useful for automated reporting systems that output to text files.

Common Use Cases

Log File Analysis

Page through server or application logs for troubleshooting: more error.log. Start from recent entries with more +1000 error.log if logs are timestamped and you know approximate line count. More readable than opening in text editor for quick checks.

System Administration Output

Review lengthy command results: wmic product get name,version | more pages through installed software list. Essential for systems with hundreds of installed applications where output exceeds screen buffer.

Code Review in Terminal

Quickly review script or configuration file contents: more deploy.ps1. Useful when SSH'd into remote systems or working in environments without GUI text editors available.

Batch File Documentation

Display usage instructions in batch scripts: more usage.txt at start of complex scripts. Provides users with documentation before execution; professional script practice.

Data Validation

Preview large data files before processing: more customer_data.csv. Check format, validate headers, spot-check sample rows before running import or ETL operations.

Configuration Auditing

Review system or application configuration files: more config.ini | find "setting" combined with pagination. Audit settings without modifying files or starting text editors.

Pre-Deployment Checks

Display deployment plans or changelogs before applying: more deployment_plan.txt in automation scripts. Gate step requiring user review before proceeding with changes.

Network Troubleshooting

Page through verbose network diagnostics: ipconfig /all | more or route print | more. Review network configuration section by section without losing details off screen.

Windows Event Log Text Exports

Review event logs exported to text: more exported_events.txt. Examine event details methodically when troubleshooting system issues or security incidents.

Documentation Viewing

Read markdown or plain text documentation in terminal: more CONTRIBUTING.md. Quick documentation reference without leaving command line environment.

Multi-File Comparison

Review multiple related files sequentially: more file1.log file2.log file3.log then press F to advance between files. Compare log entries or configurations across multiple sources.

Search Result Review

Paginate search results for readability: dir /s *.dll | more. When searching file systems with find, findstr, or dir filters, page results for careful review.

Tips and Best Practices

Use Space for Full Screens, Enter for Precision

Press Space to advance full screen when scanning; use Enter to advance line by line when you need careful reading. Enter is precise; Space is fast.

Start from Relevant Line with +n

If you know where content begins (e.g., today's logs start around line 500), use more +500 logfile.log. Saves time skipping irrelevant header or old entries.

Combine with FIND or FINDSTR First

Filter before paginating for efficiency: dir /s | findstr /i "report" | more shows only matching lines, then pages. More effective than paging all output then visually searching.

Use /s to Clean Up Messy Files

Files with excessive blank lines become more readable with /s option. more /s verbose.log improves readability of poorly formatted text files.

Q is Faster Than Ctrl+C

Press Q to cleanly exit more; Ctrl+C works but Q is cleaner termination. Q closes more gracefully without breaking pipe chains.

Page Help for Unfamiliar Commands

Always pipe help to more for new commands: commandname /? | more. Makes learning new commands easier; you can read entire help documentation methodically.

Set Tab Width for Code Files

Use /t4 for code files with 4-space indentation. more /t4 source.py displays Python or JavaScript correctly. Adjust tab width to match coding standards.

Remember Percentage Indicator

The -- More (45%) -- shows progress through file. Useful for estimating remaining content length and deciding whether to continue or search differently.

Use = to Check Current Position

At -- More -- prompt, press = to see current line number. Helpful when taking notes or documentation that references specific line numbers.

Consider PowerShell Out-Host -Paging

In PowerShell, Get-Content file.txt | Out-Host -Paging provides richer pagination with better interactive features. More is CMD-native; Out-Host is PowerShell-native.

Batch Script Pauses

Use pause command instead of more when you just need "Press any key to continue." More is for reading content; pause is for simple continuation prompts.

Clear Screen Option for Presentations

When displaying sequential information screens in demos or presentations, more /c provides cleaner screen-by-screen experience without previous content lingering.

Troubleshooting Common Issues

More Doesn't Pause on Small Files

Problem: More displays entire file without pausing.

Cause: File content fits within one screen. More only pauses when content exceeds console window height.

Solution:

• Reduce console window height temporarily (drag window smaller)
• This is expected behavior; no issue to fix
• Use type command if pagination isn't needed

Prevention: More is only necessary for files larger than screen height. For small files, type is more appropriate.

Can't Search or Use Advanced Features

Problem: Some interactive commands (like search) don't work at -- More -- prompt.

Cause: Advanced features limited in Windows CMD version of more. Full-featured more exists in Unix/Linux but Windows version is simplified.

Solution:

• Use findstr or find to search before piping to more: type file.txt | findstr "pattern" | more
• Consider PowerShell: Get-Content file.txt | Select-String "pattern" | Out-Host -Paging
• Accept Windows more has fewer features than Unix counterpart

Prevention: Plan to filter with find/findstr before pagination rather than expecting in-more search.

More Output Looks Misaligned

Problem: Columns or code indentation appears incorrect.

Cause: Tab character width mismatch. Default 8-space tabs don't match file's expected tab width.

Solution:

• Use /tn option to adjust tab width: more /t4 file.txt for 4-space tabs
• Convert tabs to spaces in source file if persistently problematic
• Check file in text editor to determine proper tab width

Prevention: Use /t4 by default for code files; most modern code uses 4-space indentation.

More Hangs or Stops Responding

Problem: More command freezes and doesn't respond to keypresses.

Cause: Rare console input buffer issue or terminal state corruption.

Solution:

• Press Ctrl+C to terminate more
• Close and restart Command Prompt
• Avoid combining more with commands that produce binary output

Prevention: Don't pipe binary data through more; use more only for text files and text command output.

Cannot Exit More with Q

Problem: Pressing Q doesn't quit more command.

Cause: Console input not focused, or keyboard input redirected.

Solution:

• Click on console window to ensure focus
• Try Ctrl+C as alternative exit
• Press Space repeatedly to reach end of content (more exits automatically)

Prevention: Ensure Command Prompt window has focus before using interactive more commands.

More Doesn't Work in Scripts

Problem: Batch script with more command behaves unexpectedly.

Cause: More is interactive; doesn't work well in non-interactive scripted contexts without input.

Solution:

• Remove more from automated scripts; more is for interactive terminal use
• Use output redirection to files instead: command > output.txt
• If user interaction needed, use pause or explicit user prompts

Prevention: Reserve more for interactive terminal sessions. Scripts should redirect output or use non-interactive commands.

Related Commands

type – Display File Contents

type displays entire file without pagination. Use type file.txt for small files or when piping to other commands. Faster than more but floods screen with large files. More is interactive; type is for non-interactive output.

find – Search Text in Files

find searches for specific strings in files. Use type file.txt | find "error" | more to search then paginate results. Find filters; more displays. Combine both for filtered, readable output.

findstr – Advanced Text Search

findstr provides regex and multi-pattern searching. Use findstr /i "error warning" log.txt | more to find multiple patterns, then page results. More powerful search than find; combine with more for readability.

clip – Copy Output to Clipboard

clip copies command output to clipboard. Use type file.txt | clip to send content to clipboard for pasting into editors. Alternative to more when you want content elsewhere, not terminal display.

Out-Host -Paging (PowerShell)

PowerShell's native pagination cmdlet. Use Get-Content file.txt | Out-Host -Paging for richer interactive features. Better navigation than CMD more, but requires PowerShell environment.

less (Third-Party)

less is powerful Unix/Linux pager. Install via Git Bash, WSL, or third-party Windows ports for advanced features: bidirectional scrolling, search, line numbers. More feature-rich than Windows more but requires separate installation.

Frequently Asked Questions

What does the more command do in Windows?

The more command displays text output one screen at a time, pausing between pages for interactive navigation. Use more filename.txt to page through files or command | more to paginate any command's output. Press Space to advance screens, Enter for lines, Q to quit.

How do I exit the more command?

Press Q to quit more command and return to command prompt. Alternatively, press Ctrl+C to terminate, or press Space repeatedly until reaching end of content (more exits automatically at end of file).

What's the difference between more and type?

Type displays entire file content immediately without pausing; more displays one screen at a time with interactive navigation. Use type for small files or piping to commands; use more for large files requiring readable pagination.

How do I page through command output?

Pipe command output to more using | operator: command | more. For example, dir /s | more pages directory listings, systeminfo | more pages system information. Any text-producing command can pipe to more.

Can I start displaying from a specific line?

Yes, use the +n parameter: more +100 file.txt starts from line 100. Useful for skipping headers or jumping to relevant sections in large files when you know approximate line numbers.

How do I display multiple files with more?

Specify multiple filenames: more file1.txt file2.txt file3.txt. At the end of each file, press F at -- More -- prompt to advance to next file. Useful for reviewing related files sequentially.

What does -- More (45%) -- mean?

The percentage indicates how much of the file has been displayed. -- More (45%) -- means you've seen 45% of the content; 55% remains. Helps gauge remaining content length.

Can I search within more output?

Windows CMD more has limited search capability. Use find or findstr before piping to more: type file.txt | findstr "pattern" | more. Unix/Linux more has built-in search; Windows version does not.

How do I make more clear the screen between pages?

Use the /c option: more /c file.txt. Clears screen before displaying each page, providing cleaner reading experience without previous content visible.

What does /s option do in more command?

/s squeezes multiple consecutive blank lines into single blank line. Use more /s file.txt to improve readability of files with excessive whitespace. Makes text denser and reduces unnecessary scrolling.

How do I adjust tab width in more?

Use /tn parameter where n is number of spaces: more /t4 source.py expands tabs to 4 spaces. Default is 8. Essential for code files where indentation and alignment matter.

Does more work in PowerShell?

Yes, more works in PowerShell as external command, but PowerShell has native Out-Host -Paging cmdlet with better features. In PowerShell, prefer Get-Content file.txt | Out-Host -Paging for richer pagination experience.

Quick Reference Card

Command	Purpose	Example
more file.txt	Page through file	Display file with pauses
command | more	Page command output	Paginate any text output
more +100 file.txt	Start from line 100	Skip to specific line
more /c file.txt	Clear screen per page	Clean page-by-page display
more /s file.txt	Squeeze blank lines	Reduce whitespace
more /t4 code.js	Set tab width to 4	Align code properly
Space	Next screen	Advance full page
Enter	Next line	Advance one line
Q	Quit more	Exit pagination

Try More in Our Simulator

Want to practice using the more command without affecting your system? Try our interactive Windows Command Simulator to experiment with text pagination, file display, and various options in a safe, simulated environment. Practice navigation commands, test different switches, and understand pagination techniques before using on actual systems.

For more file management commands, browse our comprehensive Commands Reference with over 200 Windows commands, syntax guides, and practical examples.

Summary

The more command provides essential text pagination capabilities for displaying large amounts of output in readable, screen-sized chunks directly from the Windows command line. By pausing output and providing interactive navigation, you can review log files, command results, and text documents methodically without overwhelming terminal windows or losing content off-screen.

Key takeaways: Use more filename.txt to page through files or command | more to paginate any command's output. Press Space to advance full screens when scanning quickly; press Enter to advance line by line for careful reading. Press Q to quit cleanly at any point. The percentage indicator shows progress through content.

Start from specific lines with more +n when you know where relevant content begins. Use /s to squeeze excessive blank lines in messy files. Adjust tab width with /tn for code files to maintain proper alignment. Clear screen between pages with /c for cleaner presentations or structured data review.

For system administrators and power users, more is essential for readable terminal sessions when working with verbose command output: systeminfo | more, netstat -an | more, dir /s | more. Combine with find or findstr to filter before paginating: type log.txt | findstr "ERROR" | more provides filtered, readable results. Use in interactive troubleshooting where careful review matters more than speed.

Master the more command to control output flow, review large files readably, and navigate command results methodically—all through simple pagination that transforms overwhelming text floods into manageable, screen-sized chunks for efficient terminal work.