
SvelteKit
Application framework built on Svelte for routing, server-side rendering, and deployment of web apps.
74 open-source projects declare SvelteKit in their code; 2 makers' products we track use it. What makers like most: Developers find it simpler and more productive than Next.js, and rewrites from Next.js go smoothly. Their most common complaint: API changes during active development make projects feel unstable and hard to test. On GitHub, 46 public pull requests moved projects to SvelteKit from tools we list, and 35 moved them away.
Profile checked
Works with AI agents:llms.txtMCPCLIHow makers use SvelteKit
Makers' products we track use SvelteKit for frontend framework (2).
What SvelteKit is used for
SvelteKit vs the alternatives makers chose
For frontend framework, 2 of the 2,289 makers' products we know the choice of picked SvelteKit (0%), behind Next.js (76%).
| Option | Makers' products | 2026 launches | Open source | |
|---|---|---|---|---|
| 1,731 76% | 78% | Yes | ||
| 270 12% | 13% | Yes | ||
| 235 10% | 8% | Yes | ||
| 67 3% | 2% | Yes | ||
| 43 2% | 1% | Yes | ||
| 28 1% | 1% | Yes | ||
| 2 0% | 0% | Yes |
For frontend framework: how many of the 2,289 makers' products we know the frontend framework of chose each option, and the share among the 452 launched in 2026, since a tool that came first has products from every year.
When to use SvelteKit, and when not
Pick SvelteKit if
- You already know Vue, or Svelte, and need server rendering. Frontend Framework →
Something else fits better if
- Your app lives behind a login and doesn't need search traffic: React.
- Public pages need server rendering and you want server code in the same React project: Next.js or React Router or TanStack Start.
- You're building a marketing site, docs or a blog: Astro.
SvelteKit is the application framework for Svelte, the role Next.js plays for React or Nuxt for Vue. Svelte compiles components into small JavaScript and CSS; SvelteKit adds routing, data loading, server code, rendering options and the build, using Vite.
More about SvelteKit
Routes are folders under src/routes. A +page.svelte file renders a page, a +page.server.js load function fetches its data on the server, form actions handle POSTed forms without client JavaScript, and +server.js files are plain API endpoints. Hooks run on every request for things like reading a session cookie. By default the first page is server-rendered and later navigation happens in the browser, and you can set prerendering, SSR or client-only rendering per page or layout.
Adapters turn the build into output for a target. Official ones cover Node servers, Bun, static sites, Vercel, Netlify and Cloudflare, with community adapters for other platforms. It also supports service workers for offline apps, and a SPA build can be wrapped with Tauri or Capacitor for desktop and mobile.
Limits to know: there is no built-in auth or database layer, though the Svelte CLI can set up Better Auth and database integrations. Remote functions, its newer typed client-server calls, are still experimental. The ecosystem of components and examples is smaller than React's.
How SvelteKit itself is built
8 tools, from its own code, website and Product Hunt page.
SvelteKit pros and cons
What makers like most: Developers find it simpler and more productive than Next.js, and rewrites from Next.js go smoothly. Their most common complaint: API changes during active development make projects feel unstable and hard to test.
Pros
- Developers find it simpler and more productive than Next.js, and rewrites from Next.js go smoothly. HNHN 2HN 3
- It stays close to plain HTML, CSS and JavaScript, so it is easy to learn from web basics. HNHN 2HN 3
- It works for small SPAs and scales up when an app unexpectedly grows complex. HNHN 2HN 3
- Coding agents produce working SvelteKit apps quickly. HNHN 2
Cons and watch-outs
- API changes during active development make projects feel unstable and hard to test. HNHN 2
- It is not batteries-included, so ORM, admin and auth rely on third-party packages that feel hacky. HN
- Component CSS stays in the page after unmount by design, causing layout bugs that depend on navigation path. HN
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
What Hacker News says about SvelteKit
On Hacker News, 40% of comments about SvelteKit recommend it and 9% criticize it: net praise +31%, 4th best liked of 14 tools HN discusses for frontend framework.
By year
| Year | Comments choosing it, per month | Net praise |
|---|---|---|
| 2023 | 5.4 | +41% |
| 2024 | 4.0 | +24% |
| 2025 | 2.2 | +13% |
| 2026 (8 mo) | 2.8 | +41% |
In their words
- “I use vp with sveltekit for my personal projects now, and I must say it's a very nice experience.” HN, Jul 2026
- “Eventually I tried SvelteKit, and it completely changed my perspective.” HN, Jul 2026
- “I like SvelteKit, but I was struggling with stability in active development periods” HN, May 2026
Hacker News comments January 2023 to August 2026 that name SvelteKit in a sentence like "I use" or "we moved to", Claude read a sample of 100 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.
Reliability and open issues
The most wanted open issue on GitHub has 333 👍.
Most wanted on GitHub
- Treat layout pages like components when using named slots👍 333 · opened Sep 2019 · active Aug 2026
- Native support for web sockets👍 305 · opened May 2021 · active Aug 2026
- i18n brainstorming👍 234 · opened Feb 2019 · active Aug 2026
- Translations👍 144 · opened Apr 2021 · active Aug 2026
- Add incremental static regeneration👍 140 · opened Mar 2021 · active Aug 2026
Who switches
More projects move to SvelteKit: 46 pull requests in, 35 out; the most come from Next.js and leave for Astro.
Next.js → SvelteKit22 PRs
- feat(web): migrate frontend from Next.js to SvelteKit 2 (Svelte 5)deus-meus/padelhive · 2026-08-29
- feat: Migrate blog from Next.js 16 to SvelteKit 2 (Svelte 5 + Tailwind CSS + Bits UI)jaeyoung0509/jaeyoung0509.github.io · 2026-08-16
- Migrate from Next.js to SvelteKittiennm99/loldle · 2026-07-25
- Converts site from Next.js to SvelteKitmanovotny/manovotny.com · 2026-07-24
- feat: Migrate entire portfolio from Next.js to SvelteKitaquinofroilan/aquinofroilan · 2026-07-17
- Migrate site from Next.js to SvelteKitKentokamoto/kentokamoto.github.io · 2026-07-10
- Migrate frontend from Next.js to SvelteKit + BunJeffreyyvdb/MusicHoarder · 2026-05-19
- feat: migrate from Next.js to SvelteKit + Svelte 5jscastanos/jscastanos-dev · 2026-05-19
- chore: migrate frontend from Next.js to SvelteKitshamwari-ai/shamwari · 2026-05-05
- Convert site from Next.js to SvelteKitifireball/reading-list · 2026-04-27
React → SvelteKit17 PRs
- Migrate from React to SvelteKit with native CSS and Svelte 5 runescocreating/TheCharlatan · 2026-09-29
- Migrate product UI from Next.js/React to SvelteKit and update build/toolingfozagtx/DriftRecon · 2026-09-07
- Migrate from Next.js/React to SvelteKitjooshua-inglis/pdf-editor · 2026-08-27
- feat: migrate frontend from React to SvelteKit SPArmwahid/full-stack-fastapi-template-but-svelte · 2026-08-27
- Migrate application from React to SvelteKitzmjohnso/photo-voice · 2026-06-13
- feature: migrate from React to SvelteKit 5 + Bits UIPromptPasture/neatmark · 2026-05-25
- Full rewrite of Khmer Dictionary from React to SvelteKitsrghma/khmer · 2026-04-19
- feat: migrate from Next.js/React to SvelteKit 2 + Svelte 5 (runes)ocknamo/split-bill-calculator-on-nostr · 2026-03-28
- Convert codebase from React to SvelteKitawei82/sds-svelte · 2026-02-26
- Migrate website from React to SvelteKit1aurentius/k-stacks-website · 2026-02-19
Astro → SvelteKit4 PRs
- Migrate from Astro back to SvelteKitewanc26/website · 2026-09-30
- feat: migrate from Astro to SvelteKit with YAML content architecturepixels-studio/web · 2026-04-02
- feat: migrate from Astro to SvelteKitSaintPepsi/ianhogers.dev · 2026-03-14
- Remove legacy Astro web-app after migration to SvelteKit + FastAPIbrooksmcmillin/taskmanager · 2026-01-19
Nuxt → SvelteKit3 PRs
- Migrate from Nuxt 2 to SvelteKit 2 + add Tidal playlist suggestions via Mistral AIikbenbas/mijnnaamisbas · 2026-03-26
- Migrate docs from Nuxt to SvelteKitamir20/dtop · 2026-03-23
- Update from Nuxt to SvelteKitseh-GAH-toh/EndPoem · 2025-06-17
SvelteKit → Astro13 PRs
- Convert the site from SvelteKit to Astronarthur/narthur.github.io · 2026-09-18
- Migrate site from SvelteKit to Astroivoberger/ivoberger.com · 2026-09-15
- migrate from SvelteKit to Astro v7buckley-ca/buckley.ca · 2026-06-26
- Migrate site from SvelteKit to AstroLukaHarambasic/harambasic.de · 2026-06-10
- migrate SvelteKit to Astro with static outputucielsola/ucihuen · 2026-05-08
- feat(docs): migrate docs site from SvelteKit to AstroALRubinger/aileron · 2026-04-14
- feat: migrate portfolio from SvelteKit to AstroDaveKeehl/portfolio · 2026-04-09
- chore: migrate from sveltekit to astrokaedesato/kaede-HP · 2026-04-06
- feat: convert site from SvelteKit to Astro with Rose Pine themingjordangarrison/jordangarrison.dev · 2026-03-25
- feat: migrate from SvelteKit to AstroFlexicon/czy-to-niedziela-handlowa · 2026-03-22
SvelteKit → Next.js11 PRs
- feat(shop): Migrate core ordering flow from SvelteKit to Next.jsAgustin-Perezz/pedifast · 2026-09-28
- Migrate SvelteKit web app to Next.jsnu31hackerspace/prismo · 2026-08-05
- Migrate from SvelteKit to Next.js with App Routeralexisbohns/melogram · 2026-07-10
- Rewrite from SvelteKit to Next.js (static export)jerzabek/portfolio · 2026-06-29
- Migrate from SvelteKit to Next.js 15 with full e-sports redesignmatt-gree/ProjectRio-frontend · 2026-06-16
- Migrate from SvelteKit to Next.js 15 with full e-sports redesignProjectRio/ProjectRio-frontend · 2026-06-16
- feat: migrate frontend from SvelteKit to Next.js 14 App RouterAfoD3V/poke-hub · 2026-05-21
- D3: Port client portal modules from SvelteKit to Next.jsoliverstreetcreative/osc-website · 2026-04-14
- Port SvelteKit application to Next.jsalexkibler/bikeapelago · 2026-04-06
- Convert SvelteKit application to Next.js frontend-only with expandable sidebarenskiilda/webui2 · 2025-12-07
SvelteKit → React8 PRs
- Rewrite Yahtzee scorekeeper from SvelteKit to React with ViteTheRauch1/yahtzee · 2026-08-13
- refactor: migrate web app from SvelteKit to React with new component structure and page routingDev-Card/DevCard · 2026-06-03
- refactor: migrate web app from SvelteKit to React with new component …Dev-Card/DevCard · 2026-06-03
- Migrate frontend from SvelteKit to React + Vite with Framer MotionAlidrix/The_Trend_Scope · 2026-05-04
- feat: migrate from SvelteKit to React 19 + TanStack Starthfrdmnk/morgenblau · 2026-02-25
- Migrate from Tauri/SvelteKit to rngpui React Native + Rust backendundivisible/vuno · 2026-02-14
- Migrate from SvelteKit to React with React RouterDaniel-BD/personal-tracking · 2026-02-10
- Migrate/sveltekit to reactjaem1n207/synchronize-tab-scrolling · 2025-10-17
SvelteKit → Nuxt3 PRs
- Use Opencode to try switching from sveltekit to nuxtpelletiermaxime/nhlstats · 2026-01-10
- chore: Sveltekit to Nuxt migrationiuru2522/iuru · 2025-01-12
- chore: Migration from SvelteKit to NuxtPerdolique/pepega · 2025-01-10
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.
Who uses it
2 makers' products, each linked to the source that shows it, and 74 open-source projects that declare it in their code.
None of these in makers' own words.
Open source: a project that declares SvelteKit as a dependency in its public code — verifiable, but not necessarily a live product.
What its projects tell coding agents
28 of the 47 open-source products built with SvelteKit that were worked on in the last 180 days keep instruction files for coding agents — 60%, against 53% of all the projects we read. AGENTS.md is in 23, CLAUDE.md in 17.
Alternatives to SvelteKit
All alternatives by situation →Further reading
Questions makers ask about SvelteKit
What is SvelteKit used for?
Application framework built on Svelte for routing, server-side rendering, and deployment of web apps. Makers' products we track use it for frontend framework (2).
What are the pros and cons of SvelteKit?
Pros makers name: Developers find it simpler and more productive than Next.js, and rewrites from Next.js go smoothly. It stays close to plain HTML, CSS and JavaScript, so it is easy to learn from web basics. It works for small SPAs and scales up when an app unexpectedly grows complex. Cons: API changes during active development make projects feel unstable and hard to test. It is not batteries-included, so ORM, admin and auth rely on third-party packages that feel hacky. Component CSS stays in the page after unmount by design, causing layout bugs that depend on navigation path.
What are the alternatives to SvelteKit?
For frontend framework, the other options makers' products we track chose most are Next.js (1,731), Astro (270), React (235), Vue.js (67), Svelte (43), Nuxt (28). Open source or self-hostable among them: Next.js, Astro, React, Vue.js, Svelte, Nuxt. Each alternative, with the situation it fits, is on the SvelteKit alternatives page.
Do developers switch to or away from SvelteKit?
On GitHub, 46 public pull requests moved projects to SvelteKit from tools we list, most from Next.js (22), React (17), Astro (4); 35 moved them away, most to Astro (13), Next.js (11), React (8).
When should you use SvelteKit?
You already know Vue, or Svelte, and need server rendering (frontend framework). Something else fits better if: your app lives behind a login and doesn't need search traffic, pick React; Public pages need server rendering and you want server code in the same React project, pick Next.js or React Router or TanStack Start.
Where can I deploy a SvelteKit app?
You pick an adapter for the target. Official adapters exist for Node servers, Bun, static hosting, Vercel, Netlify and Cloudflare, and community adapters cover other platforms. source ↗
Can it generate a fully static site?
Yes. adapter-static prerenders the whole site to files. To prerender only some pages and server-render the rest, use another adapter with the prerender page option. source ↗
Can I build a client-only single-page app?
Yes, by turning off SSR and serving a fallback page. The docs warn this costs load performance and SEO, and suggest prerendering as many pages as you can. source ↗
Can I use it with a backend written in another language?
Yes. The recommended setup deploys the SvelteKit frontend separately with the Node or a serverless adapter; you can also serve it as a SPA from your existing backend, with worse SEO and performance. source ↗
How do I add authentication?
SvelteKit has no built-in auth. You check the session cookie in the handle hook and put the user on locals; the Svelte CLI can set up Better Auth, and the Lucia guide covers building session auth yourself. source ↗
How do I connect a database?
Query the database only in server code, typically through a shared client module, never in .svelte components. The Svelte CLI can set up database integrations for you. source ↗
Can I ship it as a mobile or desktop app?
Yes. A SvelteKit SPA can be packaged as a mobile app with Tauri or Capacitor, or as a desktop app with Tauri, Wails or Electron. source ↗
Is SvelteKit free?
Yes — it is free, open-source software.
Is SvelteKit open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with SvelteKit?
It serves an llms.txt docs index; it has an official MCP server (dev.svelte/mcp); it has an official CLI (@sveltejs/kit).
Who uses SvelteKit?
2 makers' products we track, each with a source, and 74 open-source projects declare it in their code. source ↗