To review the largest files directly inside a Windows folder, list file objects with PowerShell, sort their numeric Length property in descending order and select the first ten. This is a read-only investigation: it does not delete, compress, move or open the listed files.
Start with one folder rather than an entire drive. A narrow listing is easier to interpret and less likely to produce a confusing mixture of application data, protected system locations and files belonging to other people. A large file is a candidate for investigation, not proof that it is unnecessary.
Choose the exact folder before listing files
Open PowerShell as your normal user. There is no reason to elevate merely to inspect a folder you already have permission to read. Set a variable to the intended directory; this example uses the Downloads folder under your user profile, but change it if your Downloads location is redirected elsewhere.
$folder = Join-Path $HOME 'Downloads'Run the following as a separate command after assigning the variable:
Get-ChildItem -LiteralPath $folder -File -ErrorAction Stop | Sort-Object -Property Length -Descending | Select-Object -First 10 -Property Name, Length, FullName-LiteralPath treats the supplied folder as a literal location rather than interpreting wildcard characters. -File excludes directory objects. With no -Recurse, the command examines files directly inside that folder, not the files in every subfolder. The Length column is a file’s reported byte length, which allows a numeric comparison without formatting or rounding first.
Read the order before acting on the result
For a hypothetical folder containing three ordinary files of 100, 2000 and 30 bytes, descending Length order places the 2000-byte file first, then the 100-byte file and finally the 30-byte file. It does not sort the displayed digits alphabetically. Files with equal lengths need not appear in a meaningful secondary order.
Keep the FullName column so similarly named files are not mistaken for each other. If your console truncates a long path, request a list-style display with this alternative command:
Get-ChildItem -LiteralPath $folder -File -ErrorAction Stop | Sort-Object -Property Length -Descending | Select-Object -First 10 -Property Name, Length, FullName | Format-ListThe number ten is just a review limit. If the folder contains fewer than ten visible files, fewer rows are expected. An empty result is not automatically an error or proof that no data exists below the folder.
Decide whether hidden files belong in this review
The ordinary listing does not include hidden items by default. If hidden files are relevant to your investigation, explicitly add Force:
Get-ChildItem -LiteralPath $folder -File -Force -ErrorAction Stop | Sort-Object -Property Length -Descending | Select-Object -First 10 -Property Name, Length, FullNameForce can reveal items normally omitted from the listing, but it does not override security restrictions. Do not change permissions or disable protection just to make a size report look complete. Investigate a denied location with its owner or administrator instead.
Keep scan scope and disk consumption separate
A direct-file listing does not measure a folder tree’s total consumption. A small set of files at the top level can sit above very large subfolders. If you later decide to recurse, treat that as a new, broader investigation, account for errors and follow your organisation’s policy before scanning shared or sensitive storage.
Reported file length also is not a promise of physical space reclaimed by deleting the file. Compression, sparse allocation, links and cloud-file behaviour can make logical length different from local allocation. A cloud-backed filename can represent data that is not all downloaded locally. This report is not a free-space measurement.
Similarly, a successful listing is only a point-in-time view. Files can grow, disappear or be replaced while you review the output. Do not use an old size report as authority for an automated deletion job.
What to check when the command fails
- Path not found: confirm the actual folder location, including any account or cloud redirection, rather than assuming the example matches your machine.
- Access denied: stop and check ownership or access arrangements. A partial or failed investigation is not a complete inventory.
- Unexpectedly few results: check the nonrecursive scope and hidden-file setting before assuming files were lost.
- Bracket characters in a path: retain LiteralPath. See the related explanation of exact filenames and PowerShell LiteralPath.
Review checklist and references
Before considering cleanup, establish who owns the file, which application uses it, whether retention rules apply and whether a recoverable backup exists. Do not add Remove-Item to this pipeline. Choose a separate, reviewed cleanup procedure only after identifying what is safe to remove.
Microsoft documents the listing and filtering behaviour in Get-ChildItem and numeric property ordering in Sort-Object. These examples follow that documented behaviour; they are not a report of a scan performed on your Windows computer.
This tutorial is for educational purposes. Test carefully before production use. The site owner is not responsible for misuse, damage, data loss or production issues.
