Static Hosting
Definition
Static hosting is the serving half of publishing a website: somewhere to put a folder, and a machine that returns its files when a browser asks. The host does a small, fixed set of things — match an incoming path to a file, choose a Content-Type, add caching and compression headers, terminate TLS, and reply. It does not execute your code, so there is no runtime version to keep current and no process that can leak memory overnight. A static site is what you give it; static hosting is what turns that folder into an address people can open. Plans differ mainly in what surrounds the files: how many requests are included, whether a custom domain is allowed, whether old versions are kept, and what analytics you get.
Why It Matters
Running your own server for a folder of HTML means you now own an operating system, a TLS certificate that expires every ninety days, a firewall and a backup plan — for files that never change. A static host absorbs all of it, usually for nothing at the sizes most sites actually are. Reliability improves for the same reason: with no application to crash, the realistic failure modes shrink to DNS and the network. The part people underestimate is the certificate; a lapsed one shows every visitor a full-page browser warning, and hosts that renew automatically simply remove that whole category of outage.
How It Works
You upload a folder and the host copies it to storage, then usually pushes it out to a CDN so the files sit near visitors rather than in one datacentre. A request arrives for /pricing/; the host looks for pricing/index.html, and falls back to a 404 page when there is nothing there. Directory paths resolve through the index.html convention, so folders behave like pages without you writing any routing. On the way out, the response carries Content-Type, Content-Length, an ETag for revalidation and a Cache-Control header, and the body is normally compressed with gzip or Brotli. HTTPS is handled by a certificate the host issues and renews for the hostname, which is why the address works over TLS the moment the upload finishes.
Real-World Example
A charity has a one-page campaign site — index.html, one stylesheet, a logo and two photographs, 1.8 MB all in. They drop the folder on 99helpers, name it give-boldly, and it is live at give-boldly.99helpers.site with HTTPS already working, no server to configure and no invoice. Two weeks later they add a password to the page while the copy is being reviewed, then take it off again for launch day. Edge analytics show 4,100 visitors and the referrer that sent most of them, without setting a single cookie.
Common Mistakes
- ✕Uploading the folder that contains the site folder — the host then serves a directory one level too high, and the home page sits at /my-site/ instead of /
- ✕Expecting server-side features to work — form handlers, PHP includes and .htaccess rules do nothing here, because nothing on the host executes them
- ✕Leaving cache lifetimes long on the HTML — visitors keep seeing yesterday's page while the new files sit unread at the edge
Related Terms
Static Site
A static site is a website made of finished files — HTML, CSS, JavaScript, images — that are sent to the browser exactly as they are stored. Nothing is assembled on the server when a visitor arrives.
index.html
index.html is the file a web server returns when a visitor asks for a folder rather than a named file. It is the default document for the site root and for every directory inside it.
Static File Hosting
Static file hosting serves files exactly as they were uploaded, byte for byte, with no code running on the server to assemble the response. Every visitor to a given address gets the identical bytes back.
CDN
A content delivery network: a set of servers spread across the world that keep copies of your files and answer each visitor from somewhere close to them. It is the service; the machines it runs on are its edge network.
Custom Domain
A custom domain is a name you own, pointed at content somebody else hosts, so visitors see files.acme.com instead of the provider's address. You keep the registration; the provider keeps the servers.
Put a file online in seconds
Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.
Host a file free →