Netlify supports any framework that produces static output. For frameworks with server-side capabilities (SSR, API routes, middleware), an adapter or plugin translates the framework's server-side code into Netlify Functions and Edge Functions automatically.

During build, the framework adapter writes files to — functions, edge functions, redirects, and configuration. Netlify reads these to deploy the site. You do not need to write Netlify Functions manually when using a framework adapter for server-side features.

Check these files to determine the framework:

astro.config.*

next.config.*

nuxt.config.*

vite.config.*

react-router

app.config.*

@tanstack/react-start

svelte.config.*

Each framework has specific adapter/plugin requirements and local dev patterns:

For single-page apps with client-side routing, add a catch-all redirect:

undefined

[[redirects]] from = "/*" to = "/index.html" status = 200

undefined

Each framework exposes environment variables to client-side code differently:

VITE_

import.meta.env.VITE_VAR

PUBLIC_

import.meta.env.PUBLIC_VAR

NEXT_PUBLIC_

process.env.NEXT_PUBLIC_VAR

NUXT_PUBLIC_

useRuntimeConfig().public.var

Server-side code in all frameworks can access variables via or .