# Static Sites

> Publish pre-built HTML, CSS, JavaScript, and assets without a long-running application server.

Source: https://nexthomelabs.com/docs/services/static-sites
Slug: services/static-sites
Section: Create
Last updated: 2026-08-30

---

# Static Sites

A Static Site serves a generated directory of files. Choose it for plain HTML and for frameworks configured to produce a static export. Because no server process runs after the build, a Static Site does not use a start command or runtime health check.

## Common output directories

| Project | Typical build command | Publish directory |
| --- | --- | --- |
| Vite or React | `npm run build` | `dist` |
| Astro | `npm run build` | `dist` |
| Next.js static export | `npm run build` | `out` |
| SvelteKit with a static adapter | `npm run build` | `build` |
| Plain HTML | none | `.` |

The directory must contain the final `index.html` and referenced assets. Review the detected framework and publish directory in the service configuration before deployment.

## Next.js static export

Set `output: "export"` in the project’s Next configuration, build the project, and publish `out`. Do not upload a normal `.next` directory to a Static Site; it needs a running server and should be deployed as a [Frontend App](/docs/services/frontend-app).

## Deploy

Select **Static Site**, choose a repository or archive source, set the build command and publish directory, then deploy. Use the deployment detail page to check whether the configured output directory was found.