What is SvelteKit adapter-static?
A SvelteKit build target that emits a fully static site with no server runtime. Fully static output fits documentation and marketing pages, but any route needing server logic must switch back to a server adapter.
Related terms
adapter-cloudflare
The SvelteKit build target that deploys this site to Cloudflare Workers. The adapter maps dynamic routes to workers and static files to assets, with route include and exclude rules controlling what runs at the edge.
Prerendering (Static)
Build-time HTML generation: pages render once during the build and ship as static files. This BYOB site defaults to prerendered routes with explicit opt-outs, so content loads fast and crawlers see complete markup.
SvelteKit
The full-stack framework BYOB generates: Svelte 5 components with server rendering, file-based routing, and edge deployment. Standard code any developer can extend outside the builder.
SSR Per Request
Fresh HTML rendered on the server for every request, used for personalized or frequently changing pages. Server rendering guarantees complete markup on first paint but costs compute per visit, so reserve it for dynamic routes.
CSR Shell
A minimal HTML shell that renders content in the browser after JavaScript loads. Client rendering suits authenticated dashboards behind login, where SEO matters less and interactivity starts only after scripts execute.
Hydration Cost
The JavaScript work that turns server-rendered HTML into an interactive app. Hydration replays component logic in the browser, so oversized bundles delay input readiness even when paint looks instant.