Gaming

Riot Games

Riot Client writes rotating diagnostic logs under LocalAppData for sign-in, patching, launch handoff, embedded Chromium web views, update services, and game bootstrap events for League of Legends, VALORANT, and other Riot titles. These plain-text session logs, crash traces, installer records, and service logs accumulate across every launch and failed update, often growing into hundreds of megabytes without helping day-to-day play. Kudu removes only the Riot Client Logs folder contents, freeing space and clearing stale troubleshooting output without touching installed games, account data, settings, replays, or Vanguard components.

Why clean Riot Games?

  • Repeated patch retries and failed repairs generate large updater and bootstrap logs, and the usual symptom is LocalAppData filling up even though no new game content was installed
  • Login loops and launch handoff errors can leave behind many duplicate session traces, so users often notice the Riot Client folder growing after every failed start
  • Embedded Chromium web views for news, store, and authentication write verbose console and network logs, which can make disk usage spike after browsing tabs in the client
  • After crash storms or anti-cheat related launch failures, Riot Client can produce fresh stack traces on every attempt, and users typically see rapid log growth between each click of Play
  • Old diagnostic logs make manual troubleshooting harder because current errors are buried under weeks of outdated patcher and service output, so finding the real cause takes longer
  • On systems with limited SSD space, accumulated Riot logs contribute to low-disk warnings and can interfere with updates by leaving less free space for patch staging files
What gets cleaned

Cache paths Kudu targets

Windows

%LocalAppData%/Riot Games/Riot Client/Logs
Frequently asked

Common questions about Riot Games

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.