Astro Framework Build Output & Asset Cache (.astro)

Bottom Line: It is 100% safe to delete .astro and dist directories. Astro automatically regenerates clean build assets on the next astro dev or astro build command.

Why Does Astro Build Cache Exist?

When building modern web applications with Astro, Vite caches transformed TypeScript components, CSS modules, and optimized image assets inside .astro/ and node_modules/.vite/.

• Primary Purpose: Fast local HMR (Hot Module Replacement) and static site generation caching.
• Storage Impact: Multi-page sites or large asset libraries expand cache storage to 500 MB to 5 GB.
• Cache Integrity: Stale .astro cache files can occasionally cause stale prop errors or broken CSS styles.

What Happens If You Delete Astro Build Cache?

• System & App Safety: ✅ 100% Safe to Delete. Your original .astro, .tsx, and .md source files remain completely untouched.
• Automatic Regeneration: Running npx astro build generates a fresh, clean dist/ directory.
• Reclaimed Storage: Deleting build caches frees 500 MB to 5 GB of disk space.

How to Delete Astro Build Cache Safely

# Delete Astro cache & dist directories
rm -rf .astro dist node_modules/.vite

Or via npm script:

"scripts": {
  "clean": "rimraf .astro dist"
}

Frequently Asked Questions (FAQ)

Will deleting .astro delete my content collections?

No. Content collection files located inside src/content/ are source files. The .astro directory only contains pre-compiled schema TypeScript definitions and build artifacts.

Why is my Astro site displaying outdated styles in dev mode?

Stale Vite cache inside node_modules/.vite can lock old CSS bundles. Deleting .astro and node_modules/.vite fixes CSS caching issues instantly.