← SkillSafe
Space Hog

For the drive that says it is full

Space HogSee what fills your drive and what to do about it.

Paste a storage listing from du, ls, find or a Drive export. The page shows where the space goes on a treemap, the biggest files and the likely duplicates. One run plans what to archive, which copies to remove and what to ask about - and the page adds up what that frees. Nothing in the plan deletes a file's only copy.

Try a sample:

1 The listing free

Get a listing - copy one line, run it in a terminal, paste what it prints:

Also read: ls -lR, Windows dir /s, and a Drive list with a name and a size column (a CSV or copied table). Sizes like 48G or 3.2 GB count in powers of 1024. Or drop a .txt or .csv here.

2 Where the space goes free

Biggest files and likely duplicates

3 The plan

One run decides each candidate: archive it off the drive (when its name says it is finished or past), remove the extra copies of a likely duplicate, keep it, or ask you first when it may be the only copy of something that matters. The page adds up what the plan frees.

Pricing as soon as the session is ready...

NOT PLANNED YET

What to do

    Questions for you

      The page's check

        Archive means move the file somewhere cheaper - an external disk, cold storage - and check the copy opens before removing it from the drive. Nothing is moved or deleted from this page.

        4 Saved drives

        How it works

        The page reads each line of du (size then path; folder totals are set aside when their files are listed), ls -l or ls -lR (the size column, under each folder heading), find -printf (bytes then path), or a table with a name and a size column. Sizes with units count in powers of 1024, as du -h and Drive do; du rounds, so its totals are close rather than exact.

        Likely duplicates are files of exactly the same size whose names match once copy marks - Copy of, (1), copy - are set aside. The candidates for the plan are those duplicate groups, then the biggest single files.

        The run never suggests deleting a file outright: single files can only be archived, kept or asked about, and only the extra copies of a likely duplicate can be removed. The page adds up what that frees from its own byte counts.