Islands for Astros
Astro islands are interactive components embedded in otherwise static HTML. The page renders to HTML on the server, and only components marked with a client directive, such as client:load, client:idle or client:visible, are hydrated in the browser. This islands architecture keeps JavaScript small and loads it only when needed.
Stage: Interactivity · Part of the Astro roadmap · Last reviewed 19 November 2026
What to learn in Islands
- Add a React, Vue or Svelte component to an Astro page
- Choose between client:load, client:idle and client:visible
- Explain why un-hydrated framework components ship no JavaScript
- Share state between islands using nanostores or similar
- Decide which parts of a page really need hydration
Islands interview questions
What does client:visible do?
The client:visible directive delays loading and hydrating a component until it scrolls into the viewport. Below-the-fold widgets such as comment boxes or carousels then cost nothing on first load. Compare client:load, which hydrates immediately, and client:idle, which waits for the browser to be idle.
What is the islands architecture?
It is a pattern in which a page is mostly static HTML with small independent interactive regions, or islands, that are hydrated separately. This contrasts with a single-page app, which hydrates the whole page. Less JavaScript runs, so pages load and become usable faster.
Where Islands fits in the Astro roadmap
Islands belongs to the Interactivity stage (beginner level). Islands.
Other units in this stage
Back to the full Astro roadmap