Server for Astros
Astro server features let pages render on demand instead of at build time. Server-side rendering uses an adapter for a runtime such as Node or a serverless host, endpoints return data, and server islands render dynamic parts of an otherwise cached page, such as a user menu, with server:defer.
Stage: Interactivity · Part of the Astro roadmap · Last reviewed 19 November 2026
What to learn in Server
- Enable SSR with an adapter and set output options
- Mark a single page for on-demand rendering
- Read request headers and cookies in a page or endpoint
- Create an API endpoint that returns JSON
- Use server:defer to load a personalised component after the page
Server interview questions
When should you use SSR in Astro instead of static output?
Use SSR when pages depend on the request, such as logged-in content, cookies, query parameters or frequently changing data that cannot wait for a rebuild. Static output is faster and cheaper to host for content that is the same for everyone, so mix both where possible.
What is a server island?
A server island is a component marked server:defer that Astro renders separately on the server after the main page has been delivered. The rest of the page can be static and cached while the island, such as a cart count or user avatar, is filled in with dynamic content.
Where Server fits in the Astro roadmap
Server belongs to the Interactivity stage (beginner level). Islands.
Other units in this stage
Back to the full Astro roadmap