Delivery for Sveltes
Delivery in SvelteKit is the step that turns your app into something you can host. An adapter converts the build output for a target, such as a Node server, static files, or a serverless platform, and the deployment process adds environment variables, a build command and a production check.
Stage: Quality and Release · Part of the Svelte roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Choose between adapter-auto, adapter-node and adapter-static
- Prerender pages that never change to produce static HTML
- Set private and public environment variables correctly
- Run vite build and preview the production output locally
- Deploy a SvelteKit app to a hosting platform from a Git repository
- Check the deployed site for broken routes and missing variables
Delivery interview questions
What does a SvelteKit adapter do?
An adapter takes the compiled app and packages it for a specific deployment target, for example a Node.js server, a set of static files, or a serverless function bundle. Without the right adapter, the build output will not run on that host.
When can you use adapter-static in SvelteKit?
Use it when every page can be prerendered at build time and the app needs no server code at request time. If any route relies on server load functions, form actions or dynamic endpoints, you need a server-capable adapter.
Where Delivery fits in the Svelte roadmap
Delivery belongs to the Quality and Release stage (advanced level). Ship.
Other units in this stage
Back to the full Svelte roadmap