The short answer
Yes. Rebuilt or re-downloaded automatically when needed.
What is it?
Gradle creates a .gradle folder at the root of each project (next to build.gradle, settings.gradle or their .kts versions) with per-project caches: file hashes, configuration cache and task history. Not to be confused with the global ~/.gradle folder. Only folders in projects untouched for 30 days are considered.
What happens if you delete it?
Gradle recreates it on the next build; that build can be slower because up-to-date checks start from scratch.
How to remove it properly
Stop the Gradle daemon with ./gradlew --stop, then move the project’s .gradle folder to the Trash in Finder.
Quit the app that uses it, then move it to the Trash. Empty the Trash when you’re sure.
- MoreRoom only suggests items unused for 30 days or more.
How MoreRoom helps
MoreRoom recognises this item, shows its real size and when it was last used, and labels it “Safe to remove”. In the free version you can move it to the Trash in one click, with Undo; Pro collects every safe item at once.
Frequently asked questions
Is it safe to delete the .gradle folder in an Android project?
Yes. Rebuilt or re-downloaded automatically when needed. Gradle recreates it on the next build; that build can be slower because up-to-date checks start from scratch.
Will Gradle project caches (.gradle) come back after I delete it?
Yes. Gradle recreates it on the next build; that build can be slower because up-to-date checks start from scratch.
How do I remove Gradle project caches (.gradle) properly?
Stop the Gradle daemon with ./gradlew --stop, then move the project’s .gradle folder to the Trash in Finder.