FolderSizes is a Windows disk space analyzer that maps local and network storage, ranks folders by size, and surfaces large, old, temporary, and duplicate files so administrators can reclaim capacity and plan future storage needs.
FolderSizes scans a drive, folder, or network share and reports how much space every directory consumes, ranking them by size so bottlenecks are obvious at a glance. Instead of opening Properties dialogs one folder at a time, it walks the entire tree in a single pass and includes hidden and system content that Explorer tends to hide. From that scan you can isolate the largest files, the oldest data, temporary clutter, and duplicate copies, then drill into file distribution by type, owner, attributes, age, or folder depth. Visual charts and exportable reports turn the raw numbers into something a team can act on.
Because storage decisions rarely happen in isolation, FolderSizes keeps working after the first scan. Recurring report schedules can run unattended and deliver results by email, while file system snapshots let you compare one point in time against another and watch capacity trends build over weeks or months. Saved reports can be reloaded and compared side by side, and output can be pushed to Excel, PDF, HTML, CSV, or XML for audits and capacity meetings. Network share discovery extends the same analysis across servers, storage devices, and domains, so a single console covers more than one machine. Teams that also need deeper duplicate-file forensics often pair it with DupScout Ultimate.
The practical payoff of FolderSizes is time and predictability. A full-disk walk replaces hours of manual folder-by-folder checking with one ranked view, so the answer to what is eating this volume arrives in seconds rather than after lunch. Administrators stop guessing about which shares deserve an archive policy, because the evidence is already grouped by size, age, owner, and file type. Scheduled scans convert that one-off cleanup into an ongoing process: you get an emailed report before a volume fills rather than a failed backup afterwards. Exports from FolderSizes slot into existing change-control and capacity-planning workflows without anyone re-keying numbers. For teams running mixed Windows estates, the ability to analyse network shares alongside local disks means one tool covers laptops, servers, and file appliances. Smaller organisations get the same clarity on a single workstation, where recovering tens of gigabytes from stale downloads and duplicate media is often enough to postpone a hardware purchase entirely.
Point FolderSizes at a local disk, a mapped share, or a discovered network resource and it measures every folder in a single pass, including hidden and system content that Explorer leaves out. The result is a complete map of where storage actually went, so nobody has to open Properties dialogs one folder at a time.
Results are sorted by size, size on disk, file count, and folder count, so the heaviest directories rise to the top of the list. You can then step down level by level to find the exact subfolder responsible, turning a vague complaint that the drive is full into a specific, actionable target.
Dedicated views pull out the biggest files, the oldest untouched data, and temporary clutter in only a few clicks. Because these are usually the safest candidates for archiving or deletion, the resulting list works as an immediate shortlist for reclaiming space on a tight volume.
FolderSizes groups duplicate files together and shows how much capacity those copies consume across a drive or network share. Because the grouped view keeps matching sets side by side, it is far easier to decide which versions to retain, which to archive, and which can simply be removed without any impact.
FolderSizes renders storage as treemap, sunburst, bar, and pie charts so patterns become visible before you read a single figure. Treemaps are especially effective for spotting one oversized branch buried deep inside an otherwise healthy folder tree, where a plain text listing would hide the problem.
FolderSizes splits scan data into separate report views covering file type, owner, attributes, age, size, name, and folder depth, so each question gets its own dedicated table rather than one overwhelming list. Every report can be exported to Excel, PDF, HTML, CSV, or XML for audits, support tickets, or capacity meetings.
Recurring scan schedules let an analysis run unattended on a set cadence and deliver the finished report straight to an inbox. Storage pressure then arrives as an early warning rather than as a failed overnight backup or a volume that quietly fills up over a weekend.
File system snapshots capture the state of a volume at a chosen point in time, and trend analysis compares those snapshots so you can see growth rates instead of a single frozen moment. Saved reports can also be reloaded later and compared side by side to confirm whether a cleanup actually worked.
No old versions have been added yet.
It analyses disk space on local drives and network shares, then reports how much room every folder and file consumes. The output is a ranked, filterable view of storage that helps you decide what can be archived, cleaned up, or moved elsewhere.
Yes. Alongside local volumes it can analyse mapped and network shares, and it includes share discovery so servers, storage devices, and domain resources can be located and examined from the same interface.
It includes duplicate file detection, grouping matching files together and showing the space they occupy, so you can review which copies to keep before removing anything.
Yes. Recurring report schedules let analyses run unattended and be delivered by email, which suits routine storage audits far better than remembering to open the application manually.
Report data can be exported to Excel, PDF, HTML, CSV, and XML. That covers presentation needs, such as a PDF for management, as well as machine-readable formats for spreadsheets, tickets, and archival records.
No. The interface is visual and chart-driven, so the ranked folder list and treemap make the biggest space consumers obvious without writing scripts or reading raw file listings.
Size is the logical length of a file's content, while size on disk reflects how much physical space it actually occupies once the file system's allocation units and compression are taken into account. The two numbers often differ, which is why a folder can hold less real data than the reported total suggests.
Explorer reveals folder sizes one Properties dialog at a time and hides certain system content. A disk space analyzer measures every folder in one pass, includes hidden items, and layers filtering, charting, and export on top of the basic numbers.
Comments