What does this tool do?
Select a folder or file set to analyze it in your browser. The tool groups available modified dates into age buckets, identifies inactive candidates using your threshold, and reports relative-path, basename, and simulated full-path lengths. It is read-only: it does not delete, archive, rename, move, or change timestamps, and it does not inspect file contents.
Age buckets and inactive candidates
Files with a readable last-modified date are placed in 0-7 days, 8-30 days, 31-90 days, 91-365 days, 1-3 years, or 3+ years. Files without a readable date appear as Unknown. The report shows the oldest and newest items by modified date. A file is flagged as an inactive candidate when its age is at or beyond the threshold in days since modified.
Path-length and filename checks
The table reports three values: relative path length, basename length for the final path segment, and simulated full path length. Relative-path length is displayed but is not checked against a limit. The selected profile is applied to the simulated full-path and basename lengths. Values over 90% of a limit and up to the limit are flagged near limit; values over the limit are flagged exceeds limit. Windows-invalid basename characters (< > : " | ? * and control characters), trailing dots, and trailing spaces are flagged separately.
Limit profiles and simulated paths
Select Windows (legacy MAX_PATH, 260), Windows (long paths enabled, 32767), or POSIX / Linux / macOS (4096). Each profile uses a 255-character filename limit. Browsers expose the selected file's relative path, not its true absolute path. If needed, enter a Simulated destination prefix (optional); the tool prepends it to the relative path to calculate the simulated full-path length.
What browsers can and can't tell you
Browser directory-selection APIs (<input webkitdirectory> and drag-and-drop) reliably expose a file's name, relative path, size, and last-modified timestamp. They do not reliably expose creation date, last-access time, symbolic-link targets, hidden-file attributes, or paths your OS blocks the browser from reading - support varies by browser and OS, and some of this information is never exposed at all. This tool groups and flags files using only what the browser actually reports, and treats anything unavailable as "Unknown" rather than guessing.
Search, filters, sorting, and exports
Search by relative path. Use Inactive only, Path issues only, Over limit only, or Unknown date only to narrow the table. Select a column header to sort the results. CSV and JSON export the full report, while Clear all removes the current analysis from the workspace.
How to use it
- Drop a folder or files onto the drop zone, or select browse folders for a folder and browse files for individual files.
- Set the inactive threshold (days since modified); the report updates automatically.
- Select a Path-length limit profile or enter an optional simulated destination prefix; the report updates automatically.
- Review the age and simulated full-path distributions and the results table.
- Search, filter, sort, or select CSV or JSON to use the report outside the page.
Frequently asked questions
Does this tool delete or rename old files?
No. This tool only reports ages, inactivity candidates, and path-length flags for your review. It never deletes, archives, renames, moves, or changes timestamps on any file, and it never claims a file is safe to remove - that decision is always yours.
Can it read creation dates or hidden/symlinked files?
Not reliably. Browser directory APIs expose a last-modified timestamp consistently, but creation date, access time, symbolic-link targets, hidden-file attributes, and inaccessible paths are not exposed consistently (or at all) across browsers. Buckets and flags here are based on whatever the browser actually reports.
How is the full path length calculated if the browser can't see absolute paths?
Browsers only expose a file's name and its path relative to the folder you selected, never its real absolute path on disk. This tool lets you optionally enter a destination path prefix to simulate what the full path would look like if these files were placed there, and checks that simulated length against the selected limit profile.
How is this different from the Folder Size Analyzer?
The Folder Size Analyzer looks at storage use - how big files and folders are. This tool ignores storage entirely and instead looks at lifecycle risk (how old or inactive files are) and filename/path portability risk (whether paths are close to or over documented length limits).
Does it upload my files anywhere?
No. Folder and file selection use the browser's local File and directory APIs. File contents are never read and nothing is sent to a server.