Developers · Angular build caches (.angular)

Is it safe to delete the .angular cache folder?

Safe to removeComes back on its ownTypical size: 100 MB–3 GB per project
…/.angular

Anywhere in your projects: a “.angular” folder next to “angular.json”.

Updated October 17, 2026By the MoreRoom team, Yando Pte. Ltd.This page as Markdown

The short answer

Yes. Rebuilt or re-downloaded automatically when needed.

What is it?

The Angular CLI keeps a persistent build cache in .angular/cache, inside the .angular folder next to angular.json. It speeds up ng build and ng serve. Only folders in projects untouched for 14 days are considered. Typically hundreds of MB.

What happens if you delete it?

The cache is rebuilt on the next build or serve, which is slower the first time.

How to remove it properly

Run ng cache clean in the project, which deletes the cache permanently, or move the .angular 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 14 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 .angular cache folder?

Yes. Rebuilt or re-downloaded automatically when needed. The cache is rebuilt on the next build or serve, which is slower the first time.

Will Angular build caches (.angular) come back after I delete it?

Yes. The cache is rebuilt on the next build or serve, which is slower the first time.

How do I remove Angular build caches (.angular) properly?

Run ng cache clean in the project, which deletes the cache permanently, or move the .angular folder to the Trash in Finder.

Guides that mention it

Related folders