Repair shops & IT teams
A cleaner handoff.
A better service visit.
Bring Kudu to your next support job. Inspect the machine, review the cleanup, and leave the customer with a clear record of what you did.
Free & open source · Commercial use allowed under MIT · No desktop account required
Understand the problem
Record the symptom and confirm the scope.
Find the right cleanup
Scan, inspect paths, and agree on selections.
Verify the outcome
Check free space and test the original symptom.
Leave a useful record
Explain results, skips, and next steps.
READY FOR THE WORKBENCH
Three resources. One repeatable workflow.
Use these locally and adapt them to your shop. No signup, no customer information sent to this page.
Service checklist
A printable, one-page workflow from intake and consent to verification and handoff.
Open printable checklist ↗CLI quick reference
Scan-only commands, JSON report examples, and exit codes for your service notes.
Download CLI reference ↗Customer handoff
An editable text template for work completed, space recovered, and follow-up advice.
Download handoff template ↗A LITTLE STRUCTURE GOES A LONG WAY
Make the next visit consistent.
Work through the checklist on screen or print a copy for your job sheet. Ticks stay in this page session and reset when you reload.
The service checklist
0 / 6 completeStart with a scan, not a script that deletes.
These commands inspect a machine without requesting cleanup. Use the executable path if Kudu is not on PATH. The Windows portable download can be run from its extracted folder.
JSON reports can contain file paths and device details. Keep them in the customer’s job record and redact them before sharing. Scan results are estimates; verify the result after cleaning.
Read the CLI reference →Scan-only examples
kudu --cli --help
kudu --cli perf info --json
kudu --cli disk drives --json
kudu --cli scan --system --browser --app --json
kudu --cli history list --jsonNo --clean flag. No bulk repair, uninstall, or privacy changes.
Bring the right tools to the job.
Windows portable
Use the ZIP or portable EXE from the download page. Portable means no installer, not no local traces: settings, history and logs can remain on the serviced machine. Follow your shop’s data-retention policy.
Choose a current download →Cleanup you can explain
Review selected items, exclusions, and the Recycle Bin before cleaning. Leave privacy traces, performance-cache resets, and optional maintenance for a separately agreed task.
Read the cleanup workflow →Ongoing support
Kudu Cloud is optional and paid. Link a customer machine only with explicit permission and a clear agreement about who manages it after the visit. Local desktop maintenance works without Cloud.
Explore ongoing monitoring →