SvelteKit: Application framework

Learn how SvelteKit turns Svelte components into complete websites and apps, with context on routing, rendering choices and deployment adapters.

Updated 8 September 2026

What SvelteKit adds to Svelte

SvelteKit is an application framework built around Svelte. It provides the structure needed for a complete website, beyond the components that make up its interface. Its documentation covers several project types, including static websites and applications with server-side behaviour.

For a booking interface, components handle the calendar and form, while the application also needs URLs, data loading and a reliable path for submitting changes. Those responsibilities belong in the wider architecture.

Static output and server features

SvelteKit supports choosing how pages are rendered and deploying the resulting application through an appropriate adapter. A static export and a server-backed application have different capabilities even when their interfaces look similar.

A public help page may be generated ahead of time, while an availability search needs current data. Decide which parts require runtime execution before selecting the hosting model.

Planning forms and navigation

Test a direct URL visit as well as navigation within the app. Both should show the correct content and handle errors clearly.

For a form that creates a booking, test repeated submissions and unavailable inventory. A responsive interface does not replace server-side validation or a reliable way to record the result. Keep those responsibilities explicit when moving between static and dynamic routes.

How DNSTrace.dev detects SvelteKit

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

x-sveltekit-page — Emitted by the framework on server-rendered page responses.
/_app/immutable/ in markup — The content-hashed build output directory SvelteKit emits.

What a detection proves

The page was produced by SvelteKit.

What it does not prove

Which adapter or host is in use, or the framework version. A statically exported build will show the asset path without the response header.

Common questions about SvelteKit

Can SvelteKit generate a static website?

Yes. SvelteKit supports static project configurations as well as server-backed applications. A static deployment cannot provide request-time server features unless another service handles them.

Why is only the asset path present on some SvelteKit sites?

The x-sveltekit-page header comes from the server runtime. A prerendered or statically exported build has no runtime to emit it, leaving the immutable asset path as the signal.

Application framework