A static site is one where the pages are already built, so there is nothing to run when a visitor arrives. It is the fastest and most reliable kind of site there is, and it is fully supported here.
Two ways to do it
Upload the files. Add a site in your panel, choose Static, and put your HTML, CSS, images and JavaScript into the site's web directory. Done.
Build from git. On Pro and above, connect a repository, set a build command such as npm run build, and tell us the output directory, for example dist, build, _site or public. Every push rebuilds and republishes the site.
What you get
- HTTPS, with a free certificate that renews itself
- The global CDN, across 119 edge locations, so your pages come from near your visitor
- Page caching
- Unmetered traffic, so a post that does well costs you nothing extra
- Automatic backups
Common build tools
Astro, Hugo, Eleventy, Jekyll, Gatsby, Vite and plain Vite plus React all produce a folder of files. Point us at that folder and you are done. Check your framework's own documentation for the exact output directory name.
Forms and other dynamic bits
A static site cannot process a form by itself. Either use a form service, or put a small app on a subdomain to receive the submissions. See Deploying a Node.js app or Deploying a Python app.
Redirects
If you are replacing an older site, set up redirects from the old addresses to the new ones so you do not lose your search traffic. Ask us at [email protected] if you have a long list and want a hand.
Clearing the cache
Because static pages are cached aggressively, clear the page cache from the panel after a big change if you do not see it straight away.
The assistant in your control panel can see your actual account and answer about your sites, your plan and your usage. For anything else, email [email protected] and a person will answer.