Apps
Google Antigravity
Built on a Chromium and Electron-style runtime, Google Antigravity stores several layers of disposable data to speed up the IDE: HTTP disk cache in Cache_Data for web UI assets and remote content, V8 code cache and compiled CachedData for faster startup, GPUCache entries for rendered UI and shader-related artifacts, cached extension VSIX packages, and rolling log files. When these files go stale or grow excessively, Kudu removes the web, compiled code, GPU, extension installer, and log caches while leaving projects, command history, sessions, settings, accounts, and passwords untouched.
Why clean Google Antigravity?
- Stale HTTP cache entries in Cache_Data can keep serving outdated IDE assets after an Antigravity update, showing broken panels, missing icons, or a UI that only fixes itself after a hard reload.
- Invalidated V8 code cache and compiled CachedData after a version change can make the first launch drag, with slow window creation, delayed command palette opening, or extensions taking longer to activate until caches rebuild.
- Old GPUCache data from a previous graphics driver version can conflict with Chromium's accelerated rendering path, causing black editor panes, flickering menus, or laggy scrolling until the GPU cache is recreated.
- Accumulated cached extension VSIX installers waste disk space and can leave Antigravity repeatedly referencing old package downloads, which users notice as large profile folders and occasional extension update oddities.
- Oversized or corrupted log files can grow quietly in the background during extension crashes or sync errors, leading to unnecessary disk usage and slower support zip creation or profile backup operations.
- A bloated mix of web cache, compiled script cache, and GPU artifacts can make Antigravity feel inconsistent between launches, with one start normal and the next showing delayed workbench rendering while each layer revalidates stale entries.
- Cached browser assets for embedded views and sign-in flows can become mismatched with newer backend responses, producing blank webviews, stuck loading spinners, or sign-in pages that do not render correctly until the cache is cleared.
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/Antigravity/Cache/Cache_Data |
%AppData%/Antigravity/Code Cache |
%AppData%/Antigravity/GPUCache |
%AppData%/Antigravity/CachedData |
%AppData%/Antigravity/CachedExtensionVSIXs |
%AppData%/Antigravity/logs |
macOS
~/Library/Application Support/Antigravity/Cache/Cache_Data |
~/Library/Application Support/Antigravity/Code Cache |
~/Library/Application Support/Antigravity/GPUCache |
~/Library/Application Support/Antigravity/logs |
~/Library/Application Support/Antigravity/CachedData |
Linux
~/.config/Antigravity/Cache/Cache_Data |
~/.config/Antigravity/Code Cache |
~/.config/Antigravity/GPUCache |
~/.config/Antigravity/logs |
~/.config/Antigravity/CachedData |
Frequently asked
Common questions about Google Antigravity
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.