How it works
Astro renders pages to HTML at build time or on the server, and ships no JavaScript unless a component asks for it. Interactive parts become islands: a React, Vue, Svelte or Solid component marked with a directive such as client:visible loads on its own, while the rest of the page stays static. Content collections give Markdown and MDX files typed, validated front matter.
It suits sites where reading matters more than app-like interaction, and sending less JavaScript helps Core Web Vitals. Server islands and on-demand rendering cover personalised parts. The team behind Astro joined Cloudflare in 2026; the framework stays MIT-licensed and deploys to most hosts.
Astro pros and cons
Pros
- Very little JavaScript by default, so pages load quickly
- Mix components from React, Vue, Svelte and others in one site
- Content collections keep Markdown and MDX sites tidy
- Deploys as static files or with server rendering
Cons
- Not built for highly interactive, app-like products
- Sharing state between islands takes extra work
When to use Astro
Pick it when
- Blogs, documentation, portfolios and marketing sites
- Sites where speed and SEO matter more than interactivity
- Moving a content site off a heavier framework
Skip it when
- Dashboards, editors or apps with lots of shared state
Astro pricing
Astro vs the alternatives
Related terms
More in Frontend
Meta-frameworks