Apps
OneDrive Logs
Background sync and installer activity in OneDrive writes rotating diagnostic logs under the per-user logs and setup\logs folders, including sync engine traces, updater and installer transcripts, crash reports, and network/authentication diagnostics. These files accumulate during normal file indexing, change detection, sign-in, update, and repair operations, but they are not the synced content itself. Kudu removes OneDrive sync client and setup log files older than seven days while leaving your cloud files, local files, account settings, and credentials untouched.
Why clean OneDrive Logs?
- Repeated sync retries and authentication loops can generate large trace logs, and the most obvious symptom is OneDrive using hundreds of MB or more in AppData even though your actual synced files have not grown
- Failed updates and repair attempts leave installer transcripts in setup\logs, so disk usage keeps increasing after each update while the app otherwise appears to work normally
- Verbose diagnostics from file rename conflicts, long path handling, or blocked uploads can pile up during a sync problem, leaving users with low-space warnings on small SSDs
- Crash and restart cycles create fresh log sets on every launch, and the visible symptom is rapidly growing log folders after OneDrive repeatedly closes, reopens, or shows sync errors
- Old diagnostic logs are only historical records, so clearing older ones reduces clutter when troubleshooting without deleting synced documents, offline files, or account preferences
- On shared or tightly managed Windows profiles, accumulated OneDrive traces can consume profile quota space, which users notice as roaming profile warnings or failed sign-ins to other corporate apps
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/Microsoft/OneDrive/logs |
%LocalAppData%/Microsoft/OneDrive/setup/logs |
Frequently asked
Common questions about OneDrive Logs
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.