How to Clean Android Studio Gradle Build Cache & Transform Caches

🟢 100% Safe to Delete Typical Space Reclaimed: 4.0 GB – 30.0 GB

Location & Quick Verdict

%UserProfile%\.gradle\caches\transforms-3

Android Studio builds cache transformed AAR libraries, dex files, and jetified JAR archives in .gradle\caches\transforms-3.

Safety confirmation: Safely frees gigabytes of drive space. Gradle will rebuild transforms for current projects upon the next build.

How Windows Manages Android Studio Gradle Build Cache & Transform Caches on NTFS & NVMe Drives

Windows 10 and Windows 11 maintain hidden system directories and root-level allocation files at %UserProfile%\.gradle\caches\transforms-3 to handle shell thumbnail databases, prefetcher launch traces, hibernation power states, and user-profile scratch storage. Because many of these paths are marked with +H (Hidden) or +S (System) attributes or guarded by SYSTEM ACL permissions, standard folder size scans often miss them entirely.

Over time, orphaned temporary files, stale Explorer DataCache_* buckets, and uncompacted virtual storage allocations inside %UserProfile%\.gradle\caches\transforms-3 lock up 4.0 GB – 30.0 GB of primary C: drive space. Cleaning Android Studio Gradle Build Cache & Transform Caches using the proper administrative method restores drive headroom safely.

PowerShell Size Verification (Read-Only Check):
# Inspect current disk footprint of Android Studio Gradle Build Cache & Transform Caches (Read-Only)
$target = "$env:USERPROFILE\.gradle\caches\transforms-3"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
  Measure-Object -Property Length -Sum |
  Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
🛡️ What Stays 100% Protected User documents, desktop files, Windows registry hives, boot configuration, and active system locks remain 100% protected.
⚡ What Gets Safely Removed Unlocked temporary scratch files, stale Explorer thumbnail/icon caches, obsolete prefetch traces, and reclaimable system allocations.

Manual Cleaning Instructions

  1. 1 Close Android Studio completely.
  2. 2 Press Windows Key + R, type %userprofile%\.gradle\caches, and press Enter.
  3. 3 Delete the 'transforms-3' and 'jars-9' cache directories.

Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.

Sub-Folders & Cache Locations Breakdown for Android Studio Gradle Build Cache & Transform Caches

Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside Android Studio Gradle Build Cache & Transform Caches are safe to purge and which files remain protected:

Sub-Folder / Cache Location Storage Role Typical Footprint Deletion Safety
%UserProfile%\.gradle\caches\transforms-3 Primary System Scratch, Thumbnail/Icon DB or Virtual Allocation 4.0 GB – 30.0 GB 🟢 100% Safe (Unlocked Files)
%LocalAppData%\Temp & C:\Windows\Temp Orphaned Installer Extraction & Session Scratch Files 1.5 GB – 18.0 GB 🟢 100% Safe
%LocalAppData%\Microsoft\Windows\Explorer (thumbcache_*.db) Cached File Explorer Image & Video Thumbnail Databases 250 MB – 3.0 GB 🟢 100% Safe (Rebuilds Automatically)
User Documents, Desktop & Registry Hives Personal Files, Boot Configuration & System Certificates Protected 🔒 Protected — Never Touched

Frequently Asked Questions

Is it safe to delete Android Studio Gradle Build Cache & Transform Caches?

Yes, 100% safe. Safely frees gigabytes of drive space. Gradle will rebuild transforms for current projects upon the next build.

How much storage space will cleaning Android Studio Gradle Build Cache & Transform Caches free up?

Users typically reclaim 4.0 GB – 30.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %UserProfile%\.gradle\caches\transforms-3.

Why does Windows say some files in Android Studio Gradle Build Cache & Transform Caches are "In Use" when I try to delete them?

Active background processes (such as explorer.exe, svchost.exe, or running desktop apps) hold open file handles to current session scratch files. Skipping locked files—or letting SWEEPR Cleaner clean unlocked items automatically—is normal and completely safe.

Where is Android Studio Gradle Build Cache & Transform Caches located on Windows 10 and Windows 11?

It is stored at %UserProfile%\.gradle\caches\transforms-3. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.

Manual File Explorer vs. 1-Click SWEEPR Cleanup

Feature Manual Deletion SWEEPR Cleaner
Locked File Handling Fails on locked processes Safe background release
Accidental Deletion Risk Moderate (easy to delete wrong folder) Zero (strict rules & hashes)
Safety Undo Rollback None (Shift+Del is permanent) 7-Day Automatic Rollback
Time Required 10–20 minutes per app < 60 seconds across 40+ areas

Related Windows Cleanup Guides & Hidden Space Hogs

Clean Android Studio Gradle Build Cache & Transform Caches Automatically

SWEEPR Cleaner safely clears Android Studio Gradle Build Cache & Transform Caches along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.

🛡️ Windows 10/11 First-Launch Walkthrough: Because v0.1.0 is a freshly compiled 5 MB native Rust app, if Windows SmartScreen appears: Step 1: Click "More info" → Step 2: Click "Run anyway".