The dir command in Windows 10 lists files and folders in the current directory by default. It does not recurse into subdirectories unless you explicitly use the /S switch. To view only the immediate contents of a folder without descending into child directories, simply run dir or dir /B for bare format output.
Understanding Default Behavior
When you open Command Prompt and typedir, the system queries the file system for entries in the active working directory. This is a non-recursive operation by design. The command reads the directory entry block for the current path and returns information about each item found there. It does not traverse deeper into the tree structure. Many users confuse this with the recursive behavior seen in other operating systems or shell environments where listing might imply depth-first traversal. In Windows CMD, depth is strictly controlled by switches.
The output includes the volume serial number, total bytes, free space, and a list of files with attributes like hidden, system, or archive. If you see subdirectory names listed, they are merely entries in the parent folder, not their contents. For example, if you have a folder named Documents, dir will show that name but will not show the files inside it. This distinction is crucial for scripting and quick navigation tasks where you want to inspect the top level only.
Verifying Non-Recursive Output
To confirm that recursion is disabled, create a test structure. Make a main folder with two subfolders, each containing a text file. Navigate to the main folder in CMD. Rundir. You will see the two subfolder names and any files directly in the main folder. You will not see the text files inside the subfolders. This proves the command stops at the first level. If you need to see those inner files, you must change your approach using specific parameters.
Common Switches for Directory Listing
While the basicdir command is non-recursive, several switches modify its behavior. Understanding these helps you avoid accidental recursion or unwanted verbosity. The most common switch is /W, which displays the list in wide format. This saves screen space by showing multiple columns per line. It remains non-recursive. Another useful switch is /O, which sorts the output. You can combine it with letters like G for groups (directories first) or S for size.
The /A switch controls attribute filtering. Using /A:D lists only directories. Using /A:-D lists only files. This is helpful when you want to separate the two types of items visually. However, even with these filters, the command stays within the current directory boundary. It does not look inside the directories it lists unless told otherwise.
Using Bare Format for Scripts
For automation or piping results to other commands, use/B. This removes headers, footers, and summary lines. It outputs just the file and folder names, one per line. This format is clean and easy to parse. It is particularly useful when you want to feed a list of files into another tool. Remember that /B does not enable recursion either. It respects the same non-recursive constraint as the standard display mode.
When Recursion Is Actually Needed
Sometimes you do want to see everything. If your goal is to find a specific file buried deep in the hierarchy,dir alone is insufficient. You must add /S. This flag tells CMD to process the current directory and all its subdirectories recursively. Be cautious with this switch on large drives, as it can take significant time and generate massive output. It is the primary way recursion occurs in CMD.
If you use /S, every file in every subfolder will be listed. This is different from the default behavior. There is no middle ground where CMD automatically recurses partially. It is either fully non-recursive (default) or fully recursive (/S). Some users mistakenly believe there are flags for "one level deep" recursion. CMD does not support this natively. You would need to use PowerShell or a loop in a batch file for limited depth recursion.
Alternatives for Advanced Navigation
If you finddir too limited for complex browsing needs, consider using PowerShell. The Get-ChildItem cmdlet offers more granular control. You can use -Recurse for full recursion or omit it for non-recursive listing. PowerShell also allows you to filter by depth or type more elegantly than CMD switches. However, for simple, quick checks, CMD remains faster and lighter.
Another alternative is using the File Explorer GUI. It provides a visual representation of the directory tree. You can expand folders manually to see contents. This is less efficient for scripting but better for human exploration. If you are troubleshooting file visibility issues, ensure that hidden files are shown in Explorer settings. CMD respects the same hidden file rules as Explorer unless you use /A to override them.
Frequently Asked Questions
Does dir show hidden files by default?
No, thedir command excludes hidden files and system files from its output by default. To include them, you must append the /A switch. Specifically, dir /A shows all files regardless of attributes. Without this switch, you will miss important configuration files stored in hidden folders.
How do I sort files by size using dir?
Use the/O switch combined with the letter S. The command dir /O:S sorts the output by file size in ascending order. You can reverse the order by adding a minus sign, like /O:-S. This helps identify large files quickly without opening each folder individually.
Can I limit dir to show only subdirectories?
Yes, use the/A:D switch. Running dir /A:D filters the output to display only directories. This is useful when you want to navigate through folder structures without seeing individual files cluttering the list. It keeps the output clean and focused on folder names.
Is dir an alias for Get-ChildItem?
No,dir is a built-in internal command of the Windows Command Prompt. It is not an alias for PowerShell's Get-ChildItem. While both list directory contents, they operate in different shells with different syntax and capabilities. Confusing them can lead to errors when switching between CMD and PowerShell scripts.
Why does dir take so long to run?
If you accidentally used the/S switch, the command is recursing through all subdirectories. This causes significant delay on large drives. Remove the /S flag to return to fast, non-recursive listing. Also, check if network drives are mapped, as accessing remote shares can slow down local directory queries significantly.