Needs a static export
How to publish a Next.js site as a static export
Next.js renders on a server by default, so it needs one config change before it can be published as a finished site.
Choosing a host rather than a command? Next.js Hosting and React Hosting cover what they cost and what does not work here.
- Build command
- npm run build
- Folder to upload
- out
Free plan, free SSL, no credit card.
-
Build the project
Run npm run build in the project folder. This is the step Droply does not do for you: we publish finished pages, we never run your build.
-
Find the output folder
The build writes a finished site to out. That folder, not the project folder, is what gets uploaded.
-
Drag it in
Drop the folder (or a ZIP of it) into Droply. It is live on an HTTPS droply.id subdomain in seconds, and re-uploading publishes a new version at the same URL.
Worth knowing about Next.js
Add
output: "export"to next.config.js, then build. The static site appears inout, not.next.Anything that runs on the server does not survive the export: API routes, server actions, middleware, on-demand revalidation and dynamic image optimisation.
If your app depends on those, it needs a host that runs Node. That is a real answer, not a limitation we can configure around.
Did an AI tool build this project?
- v0 hosting: Next.js with shadcn/ui. Needs a static export before it can be served as files, and this is the page that says which setting.
Hosting an AI-generated website covers the question that comes before the build command: whether what you are holding is a single file or a project, and which of the two every tool actually hands back.