32

What command would you use in cmd.exe to find the number of files in the current directory?

Is there a PowerShell option here?

Update: I was hoping to avoid dir, as I know there are 10,000+ files in the current directory. Wanted to avoid the enumeration output to the cmd window. T

Dave M
  • 4,494
p.campbell
  • 4,447

13 Answers13

35

If you want to do it with cmd, then the following is the trivial way to do it:

set count=0 & for %x in (*) do @(set /a count+=1 >nul)
echo %count%

That's assuming the command line. In a batch file you would do

@echo off
setlocal enableextensions
set count=0
for %%x in (*) do set /a count+=1
echo %count%
endlocal

which does things a little nicer. You can drop the >nul in a batch, since set /a won't display the result if run from a batch file—it does directly from the command line. Furthermore the % sign in the for loop has to be doubled.

I've seen quite a few instances where people try nifty tricks with find /c. Be very careful with those, as various things can break this.

Common mistakes:

  1. Using find /c /v and try finding something that is never included in a file name, such as ::. Won't. Work. Reliably. When the console window is set to raster fonts then you can get those character combination. I can include characters in a file name such as :, ?, etc. in their full-width variants for example, which will then get converted to their normal ASCII counterparts which will break this. If you need an accurate count, then don't try this.

  2. Using find /c and try finding something that is always included in a file name. Obviously the dot (.) is a poor choice. Another answer suggests

    dir /a-d | find /c ":"
    

    which assumes several things about the user's locale, not all of which are guaranteed to be true (I've left a comment detailing the problems there) and returns one result too much.

Generally, you want to use find on dir /b which cuts away all the non-filename stuff and avoids fencepost errors that way.

So the elegant variant would be:

dir /b /a-d | find /c /v ""

which will first output all file names, one line each. And then count all lines of that output which are not empty. Since the file name can't be empty (unless I'm missing something, but Unicode will not trip this up according to my tests).

Joey
  • 1,893
18

Ask and ye shall receive: http://technet.microsoft.com/en-us/library/ee692796.aspx

Counting the Number of Items in a Folder

Well, what do you know: it looks like the sun is finally coming out, which means it’s almost time for us to go. Before we do, however, let’s show you one last little trick with the Get-ChildItem cmdlet. Sometimes you don’t really need to know much about the files in a folder; all you really need to know is how many files (if any) can be found in a particular folder. Here’s how you can quickly count the number of files in a folder:

(Get-ChildItem C:\Scripts).Count

What are we doing here? We’re simply using Get-ChildItem to return a collection of all the items found in the folder C:\Scripts; because this is a collection, all we have to do is echo back the value of the Count property, which tells us the number of items in the collection. Note the use of parentheses: we enclose the Get-ChildItem command in parentheses to ensure that Windows PowerShell first grabs the collection and only then echoes back the value of the Count property for that collection.

And sure, you can include a filter when calling Get-ChildItem. Need to know how many .PS1 files are in the folder C:\Scripts? Okey-doke:

(Get-ChildItem C:\Scripts -filter "*.ps1").Count

FYI .. I googled "powershell count files".

Trevoke
  • 419
12

The fastest method I have found is to run the following in the PS console.

[System.IO.Directory]::GetFiles($path).Count

where $path is a local path or UNC share.

p.campbell
  • 4,447
11
dir /a-d | find "File(s)"

A word of warning about using PowerShell for simple file operations like this - it is incredibly slow compared to cmd.exe, especially over network connections or when there are thousands of files in the directory. See this forum post for more info.

rossnz
  • 659
  • 4
  • 7
7

dir gives you the total file count at the bottom.

lorenzog
  • 2,979
3

just count lines from the dir /B output (directories included):
dir /B | find /c /v "~~~"

for just count files (with no dirs):
dir /A-D /B | find /c /v "~~~"

Garcia
  • 31
2

Found this on the net:

dir /a-d | find /c ":" > NUMfiles.###
set /p count=<NUMfiles.###
echo %count%

I tested and it seems to work.

Kelsey
  • 153
2

Just a caveat for those who might use Trevoke's PowerShell answer above (Windows command prompt: how to get the count of all files in current directory?): by design, echoing the Count property of a collection returned by Get-ChildItem can give misleading results if the value is 1 or 0. This is because the Count property is only available on arrays. If fewer than 2 items are returned by Get-ChildItem, the result is scalar, and .Count returns nothing. To get around this, explicitly cast it into an array, e.g., @(Get-ChildItem C:\Scripts).Count.

For more info, see http://connect.microsoft.com/PowerShell/feedback/details/354672/get-childitem-count-problem-with-one-file or http://www.vistax64.com/powershell/266379-get-childitem-count-not-working-one-file.html.

Heather M.
  • 21
  • 1
0

dir returns the number of files and dirs at the bottom

dyasny
  • 19,257
0

DIr will of course work

Without installing something on the server but having powershell on your workstation you could do:

(gwmi -computer theserver -query "select *from cim_datafile where path = '\\'").count

that command will give you all the files (system and hidden included) and as previously mentioned if powershell is on the machine you can simply

(GCI c:\*.*).count

Note that if you do not include the . you will get a count of all files and all directories. You will not include hidden and system files you need to add -force to count them all

Jim B
  • 24,276
0

If I only needed this once I'd just use dir, otherwise I'd consider rolling my own, probably as a C# app because that's what I would be most familiar with (although VBScript or PowerShell would also be viable).

(By the way - it's not DOS if you're using cmd.exe)

0

I believe you can use attrib to get the file count:

attrib.exe /s /D *.*|find /c /v "" >> filecount.txt

This will create a file called filecount.txt in the current directory with the number of files and folders in the current directory (including the newly created file). You can change the

*.*

to

<full_path>\*.*

in order to get the file count of a particular directory. Remove the "/D" option if you don't want to count folders. The "/s" option processes files in all directories in the specified path. So remove it if you only want files in the specified path and don't want to include files in sub folders.

So for example if you want to find out how many files are in your C:\ drive and not any subfolder you would use the command:

attrib.exe C:\*.* | find /c /v "" >> filecount.txt
smoak
  • 656
-2

I'm doing something similar and this works with any number of files instantly.

Setlocal enabledelayedexpansion

Dir /A | find "File(s)" >tmp

For /F "tokens=1" %%i in (tmp) do set n=%%i

Del tmp

If !n! GEQ 10 echo Too many files in directory.