Skip to content

What is 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.

Example

The site builds with adapter-cloudflare: dashboard and API routes run as workers while blog, glossary, tools, and marketing pages serve as static files, exactly matching the include and exclude lists in svelte.config.js.

What people get wrong

Reaching for adapter-static on an app with server endpoints silently drops dynamic behavior. Match the adapter to the app: static output for static sites, the Cloudflare adapter when workers serve live routes.

Frequently asked questions

Do excluded routes still deploy?

Yes. Excluded paths still publish as static assets alongside the worker; the exclude list only controls what the worker handles at request time, keeping edge compute focused on dynamic routes.

Sources

Browse all Build & Render Performance terms →