Before You Start
Folder size is a calculated total, not a simple label stored on an ordinary folder. Windows must enumerate accessible files in the selected hierarchy.
Choose a parent folder you understand, such as your user profile, a project root, or an external archive. Avoid beginning in protected Windows or application directories.
- Know the complete pathFolders with the same visible name can exist on different drives, profiles, or synchronized locations.
- Allow timeLarge hierarchies, cloud content, and slow storage can make Properties calculations take longer.
- Pick one size valueUse Size consistently for a logical folder comparison unless allocation is the specific question.
Understand Parent, Child, and Recursive Totals
Do not add the 82 GB parent total to its children—the children are already included.
A parent folder contains direct files and child folders. Each child can contain more levels. A recursive calculation descends through accessible levels and adds the file data to the parent total.
If a parent is 82 GB and one child is 48 GB, do not add 82 and 48. The child’s data is already represented in the parent. To explain the parent, compare children that share that parent.
This model also clarifies why a deeply nested project can dominate a broad folder. The top-level name may be small in number, but the branch beneath it can contain thousands of assets.
Calculate a Folder with Properties
Open the known parent location
Use File Explorer to reach your user profile, Documents, a project root, or another location whose purpose is clear.
Expected result: The path and scope are visible.
Open folder Properties
Right-click the folder and choose Properties.
Expected result: Windows begins enumerating accessible content.
Wait for values to settle
Watch the file and folder counts and the Size values. Large trees can continue updating for a while.
Expected result: The recorded total reflects the completed snapshot as closely as practical.
Record the context
Write down the complete path, date, Size, and relevant cloud or external-drive state.
Expected result: The value can be interpreted and compared later.
Repeat for sibling folders
Measure other children of the same parent using the same value and method.
Expected result: You obtain a fair comparison without double-counting.
Why Files Sort by Size but Ordinary Folders Do Not
A file has a size property that File Explorer can read for the current list. A folder total requires a recursive walk through descendants, which could be slow, trigger storage access, encounter permissions, or involve cloud content.
For that reason, the standard Size column normally displays values for files and leaves ordinary folder rows blank. Sorting the column sorts files; it does not silently calculate and rank every folder.
Use Details view for file-level comparison and Properties for selected folder-level questions. Trying to make one view answer both questions is a common source of confusion.
| Display | Scope | Calculation | Use it for |
|---|---|---|---|
| File Size column | One file | Read from file information | Sorting files |
| Folder Properties: Size | Selected hierarchy | Recursive enumeration | Comparing folder branches |
| Folder Properties: Size on disk | Allocated blocks for accessible files | File-system allocation | Investigating allocation differences |
| This PC capacity | Whole volume | Volume allocation | Used and available drive space |
Compare Siblings and Follow the Largest Relevant Branch
Account for Cloud Files, Permissions, and Changing Content
- The total never seems to stopAn application may be writing files, synchronization may be active, or the hierarchy may be very large. Close relevant work and retry when activity is lower.
- The result differs from another accountPermissions and profile-specific access can change which content is enumerated.
- A cloud folder has many files but little local usageOnline-only placeholders represent remote content without storing every file locally.
- The parent does not equal a simple sumDirect files, inaccessible items, links, allocation differences, or measurements taken at different times can affect the comparison.
- A protected folder is largeDo not change permissions or ownership solely to inspect or reduce it. Use guidance for the owning Windows feature or application.
Frequently Asked Questions
Does a folder have its own fixed size?
An ordinary folder’s useful total is calculated from accessible files beneath it. The result can change as content, access, or cloud state changes.
Why can Size on disk be smaller than Size?
Compression and sparse-file behavior can reduce allocated storage. Allocation units can also make Size on disk larger for collections of small files.
Can I compare a Windows Storage category with a folder?
You can use them together, but they are different scopes. A category can combine several paths and should not be expected to match one folder exactly.
What is the safest comparison?
Measure sibling folders under a parent you understand, using the same Properties value at approximately the same time.