Apps
Ruby Gem Cache
RubyGems keeps a local cache of downloaded .gem package archives under ~/.gem so installs, reinstalls, and dependency resolution can reuse already fetched files instead of downloading them again. Over time this cache accumulates old gem versions, partially downloaded archives, and package files that are no longer needed after upgrades or bundle changes. Kudu removes these cached .gem archives while leaving installed gems, user projects, gemsets, credentials, and configuration untouched.
Why clean Ruby Gem Cache?
- Corrupted or partially downloaded .gem archives can cause gem install or bundle install to fail with checksum, unpacking, or unexpected EOF errors until the bad cached file is removed
- Old cached gem versions pile up after repeated updates, so ~/.gem grows large and users notice low disk space even though those package archives are no longer actively used
- A stale local archive may be reused instead of fetching a fresh copy, leading to repeated install failures for one specific gem until the cache is cleared
- Switching between Ruby versions, gemsets, or dependency sets leaves behind many unused .gem files, making cache directories much larger than the currently installed environment suggests
- Offline or flaky-network installs can leave incomplete package downloads in the cache, and the next install attempt may keep failing on the same gem until that archive is deleted
- Large gem caches slow down manual inspection, backup, and profile sync operations because thousands of old package archives under ~/.gem are copied even though they can be downloaded again as needed
What gets cleaned
Cache paths Kudu targets
Windows
~/.gem |
macOS
~/.gem |
Linux
~/.gem |
Frequently asked
Common questions about Ruby Gem Cache
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.