Apps

Slack

Slack’s desktop app stores Chromium disk cache entries, Electron V8 compiled code in the Code Cache, GPU shader and render artifacts in GPUCache, and rotating diagnostic logs to speed up workspace loading, channel navigation, and message rendering. Those files help Slack reuse downloaded assets, JavaScript bytecode, and graphics data between launches, but they can become stale after app updates, sign-in changes, or graphics driver changes. Kudu removes Slack’s temporary web cache, compiled code cache, GPU cache, and old logs without touching your workspaces, messages, account details, or preferences.

Why clean Slack?

  • Outdated Chromium cache entries can leave Slack showing blank sidebars, missing profile images, or channels that never fully load until the cached web assets are replaced
  • Invalidated Electron V8 bytecode after a Slack update can cause a very slow first launch, repeated white screens, or several seconds of lag before the UI becomes responsive
  • Stale GPUCache data from a graphics driver update can trigger black windows, flickering panels, or broken emoji and image rendering until Slack rebuilds its shader cache
  • Corrupted cached API responses and frontend bundles can cause sign-in loops, workspace switching failures, or a banner that says Slack needs to reload
  • Large accumulated Cache_Data files waste disk space on systems with many workspaces and heavy file previews, especially when old downloaded assets are never reused
  • Verbose logs can grow after repeated crashes, connection retries, or debugging sessions, leaving behind disk usage even after the original problem is gone
What gets cleaned

Cache paths Kudu targets

Windows

%AppData%/Slack/Cache/Cache_Data
%AppData%/Slack/Code Cache
%AppData%/Slack/GPUCache
%AppData%/Slack/logs

macOS

~/Library/Application Support/Slack/Cache/Cache_Data

Linux

~/.config/Slack/Cache/Cache_Data
Frequently asked

Common questions about Slack

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.