wipzy

The Wipzy film

47 seconds. Music and sound, no narration.

What happens in it

  1. A full disk

    Every project leaves something behind: DerivedData/, an old Xcode_15.4.xip, an Android emulator image. On the sample Mac it adds up to 167 GB.

  2. The scan

    Wipzy reads the whole home folder in 8.7 s on an M4 Pro. The gauge settles on 81.2 GB that is Safe: it comes back with one command.

  3. 305 stacks

    Each project is listed with what it is built on, from Laravel 11 and Next.js 15 to Axum 0.7 and Flutter 3.5. 49 languages, 159 project rules.

  4. Search a project, open What Wipzy sees

    The stack with versions, the evidence for each, and what can go next to the command that brings it back: vendor/ with composer install, node_modules/ with npm install.

  5. Four risk levels

    Safe Your call Careful Protected

    Only Safe is ticked for you.

  6. Review plan, then Clean

    67 items, 81.2 GB, move to the quarantine, each one checked again right before it moves. Nothing is deleted, and Undo puts everything back.

  7. What is Protected

    app/, routes/, .git, .env: your code is never on the list. Anything no rule recognises is Protected.

  8. The tagline

    Deletes only what your toolchain can rebuild.

Get Wipzy

Free cleans Projects and Dev caches. See what Pro adds and what it costs, how the four risk levels work, and what Wipzy sends over the network.