Adapters
Before you can deploy your SvelteKit app, you need toadapt it for your deployment target. Adapters are small plugins that take the built app as input and generate output for deployment.
Official adapters exist for a variety of platforms — these are documented on the following pages:
@sveltejs/adapter-cloudflarefor Cloudflare Pages@sveltejs/adapter-cloudflare-workersfor Cloudflare Workers@sveltejs/adapter-netlifyfor Netlify@sveltejs/adapter-nodefor Node servers@sveltejs/adapter-staticfor static site generation (SSG)@sveltejs/adapter-vercelfor Vercel
Additionalcommunity-provided adapters exist for other platforms.
Using adapters
Your adapter is specified insvelte.config.js:
importconstadapter:(opts:any)=>import("@sveltejs/kit").Adapteradapterfrom'svelte-adapter-foo';/**@type{import('@sveltejs/kit').Config}*/constconstconfig:Config@type{import('@sveltejs/kit').Config}config={Config.kit?:KitConfig|undefinedSvelteKit options
kit:{KitConfig.adapter?:Adapter|undefinedYouradapter is run when executingvite build. It determines how the output is converted for different platforms.
@defaultundefinedadapter:functionadapter(opts:any):import("@sveltejs/kit").Adapteradapter({// adapter options go here})}};exportdefaultconstconfig:Config@type{import('@sveltejs/kit').Config}config;Platform-specific context
Some adapters may have access to additional information about the request. For example, Cloudflare Workers can access anenv object containing KV namespaces etc. This can be passed to theRequestEvent used inhooks andserver routes as theplatform property — consult each adapter’s documentation to learn more.