NEXT.JS HOSTING

Yes, in two ways. For SSR, run the Next.js server on any Node.js host (VPS, Render, Railway). For static export, host the pre-built HTML files anywhere. Static.app is one of the simplest options for static exports: add output: 'export' to your config, run the build, ZIP the out/ folder, and upload. No Docker, no Node.js runtime, no process management.

Vercel offers a free tier for Next.js that includes SSR and serverless functions, with limits on bandwidth and commercial use. For static exports hosted elsewhere, Cloudflare Pages and GitHub Pages are free with limitations. Static.app costs $5/monthnth and includes unlimited traffic, built-in forms, analytics, and password protection. The right choice depends on whether you need server-side features or just want to serve pre-built HTML files.

No. Static.app hosts pre-built files only, with no server-side runtime. For Next.js, this means you need to use static export mode by adding output: 'export' to your next.config.js. This pre-renders all pages as HTML files during the build step. If your app relies on SSR features (Server Components with server-side data fetching, ISR, or middleware), you need Vercel or another Node.js host.

No. API routes in Next.js (the /api directory) require a running Node.js server to process requests. On static hosting, there's no server to execute that code. The workaround is to move your API logic to a separate backend service (Render, Railway, Supabase) and have your Next.js frontend call it via fetch. For simple form handling, the static-form attribute on Static.app replaces the need for a custom API route.

API routes, Server Components with server-side data fetching, ISR (Incremental Static Regeneration), and middleware. These all require a running server. Static export generates HTML at build time.

Yes, in static export mode. Set output: 'export' in your config and the App Router's static features work: layouts, nested routes, loading states, error boundaries, and parallel routes. The parts that don't work in static export are Server Actions, dynamic server-side data fetching, and middleware. If your app uses only client components and static data, the App Router works perfectly.

Yes, using generateStaticParams() in your route files. This tells Next.js to pre-render every combination of the dynamic parameter at build time. For example, a blog with /posts/[slug] generates a separate HTML file for each post. The resulting pages are static files that Static.app serves like any other HTML page. You need to know all possible parameter values at build time.

Yes, with one configuration change. Add images: { unoptimized: true } to your next.config.js. This tells Next.js to use standard <img> tags instead of its server-side image optimization (which requires a running server). Your images still display correctly, they just won't have the automatic WebP conversion and responsive sizing that Vercel provides. For most sites, the difference in loading speed is minimal.

Yes. Tailwind CSS is a build-time tool that generates a single optimized CSS file during next build. The output contains only the CSS classes your project actually uses, typically 10-30KB. Static.app serves this CSS file like any other static asset. There's nothing server-side about Tailwind.

Add trailingSlash: true to your next.config.js. Without this, Next.js generates files like /about.html. With it, the output becomes /about/index.html. The second format works more reliably on static hosts because the server can resolve /about/ to /about/index.html automatically. This also prevents redirect issues that can hurt page load speed and SEO.

Static export supports i18n through sub-path routing. Each locale gets its own set of pre-rendered HTML files (e.g., /en/about/index.html, /fr/about/index.html). Upload all of them in your ZIP and Static.app serves the correct page for each URL. Note that automatic locale detection based on the Accept-Language header requires middleware, which doesn't work in static export. You'll need a client-side redirect or language selector instead.

Vercel is excellent for full Next.js features (SSR, ISR, Edge Functions). If you only need static export, Static.app is simpler and cheaper with no per-seat pricing.

Vercel's free tier includes SSR, Edge Functions, and automatic Git deployment, but has bandwidth limits (100GB), build minute caps, and one commercial project restriction. Static.app's $5/monthnth plan has unlimited traffic, no build minute limits (you build locally), and supports multiple commercial sites. If you need SSR or serverless functions, Vercel is the better choice. If you're exporting static HTML and want simpler, unlimited hosting, Static.app costs less with fewer restrictions.