Apps
Granola
Granola stores a Chromium HTTP disk cache in Cache_Data to speed up loading web content, embedded app resources, images, scripts, and API responses between launches. Over time those cached response bodies, index files, and metadata entries can become stale or oversized, especially after site changes or app updates. Kudu removes only Granola's HTTP cache older than one day, leaving settings, sessions, databases, and user content untouched.
Why clean Granola?
- Stale cached HTML, JavaScript, or CSS can make Granola load an older version of a page, which shows up as missing buttons, broken layouts, or features that do not match what the service currently serves
- Expired API responses left in Chromium's disk cache can cause panels to show outdated information or fail to refresh until the old entries are removed
- A bloated Cache_Data folder increases disk usage and can slow startup while Granola scans cache index entries before rebuilding fresher ones
- Corrupted cached images or media files can produce blank thumbnails, partial page rendering, or assets that never finish loading even though the network is working
- Cached redirects and response metadata from a previous deployment can trap Granola in reload loops, repeated sign-in prompts, or pages that only start working after a hard refresh
- Old compressed response bodies and cache fragments can make one specific workspace or view misbehave repeatedly, while clearing the HTTP cache forces Granola to fetch clean copies without affecting saved sessions or content
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/Granola/Cache/Cache_Data |
Frequently asked
Common questions about Granola
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.