Hosting HTML files is a placement decision

You have .html files (plus CSS, JS, images). The question is where those bytes live publicly. Ignore forty-vendor bingo cards. Filter on: who builds, who terminates TLS, whether unknown URLs rewrite, whether mail is bundled, and whether forever-free is a hard requirement.

StaticHost hosts the files you supply via zip or GitHub. Build locally—the platform does not run npm or Hugo. HTTPS appears on preview before you touch DNS; custom certificates follow DNS verification. nginx: try_files $uri $uri/ =404 (no SPA index.html fallback). No email. No CDN product. Plans $9 / $30 / $65 / $130. Short trial, not free forever.

Related decision pieces: best host for an html website, static website hosting for small projects, static website hosting service.

HTML files are the oldest web deployment unit. Modern platforms sometimes obscure that. If your deliverable is already HTML, you do not owe anyone a framework narrative to earn HTTPS.

What StaticHost is for HTML files

A narrow pipe from your folder to HTTPS. Deploy history. Explicit site and storage caps. Staging on Pro and above. Suitable for brochure sites, exported portfolios, and small multi-page HTML kits without server-side code. You can replace the tree in minutes when copy changes.

The operational story stays readable: edit → package → deploy → preview → optional DNS. That readability is why file hosts still win for HTML kits.

What it is not

Not a browser-based Dreamweaver replacement as the primary workflow. Not PHP. Not a mailbox factory. Not a guarantee that file:// habits will survive. Not an edge rules playground. Not unlimited. Not a place to expect history-mode SPA rewrites.

If your HTML is a thin shell over an API that needs secret server routes, you need more than HTML file hosting for the API—even if the shell itself can still be static.

Criteria that sort hosts quickly

  1. Artifact purity. Pure HTML files → file host or object storage. Needs runtime → elsewhere.
  2. Rewrite policy. Need SPA fallback → platform that documents it. Accept =404 → StaticHost.
  3. Ops. Want zero nginx on-call → managed static. Want full control → VPS.
  4. Money. $0 forever → Pages-class. Paid predictable → StaticHost tiers.
  5. Identity. Preview URL first vs DNS-first workflows—prefer preview-first for HTML file checks.
  6. Hand-off. Can a non-developer upload a zip you prepared? If yes, prefer simple file ingest.

Run the list before demos. Sales calls for unrelated platforms eat afternoons.

Worked example: local plumber brochure site

A plumber has index.html, services.html, service-area.html, and photos/ of van wraps. No CMS. Phone numbers are tel: links. They ask where to host the HTML files their nephew exported from a template.

StaticHost fits: upload the folder, preview on HTTPS, then point plumber.example after the nephew confirms spellings. Starter ($9) covers one site and 2 GB. They should not buy a VPS. They should not install WordPress “for future blogs” if nobody will write posts. They should not expect info@ mailboxes on the web plan—use Google Workspace or similar separately.

If next year they add three technician microsites, Pro ($30) or Scale ($65) matches site count better than overloading one project. Keep each technician’s HTML in its own site slot so takedowns stay clean.

Failure: file:// CSS paths that 404 in production

HTML authored by double-clicking files often picks up absolute file:// references or machine-specific paths when editors “help.” Locally, Chrome still loads file:///Users/nephew/site/styles.css. On StaticHost, that URL is meaningless; the stylesheet 404s or never applies. Sometimes the HTML uses href="C:\Users\...".

Catch this on preview before DNS. View source. Every stylesheet and script should be a relative path (styles.css, css/site.css) or a root-relative path on your host (/css/site.css), not a file:// URI. Fix the HTML, re-zip, redeploy. The host cannot rewrite your nephew’s laptop paths into web paths automatically.

This failure is why “where to host” must include “where to verify”: choose a host with instant HTTPS preview so path bugs show up without involving the domain registrar. Plumbers do not care about nginx theory; they care that the blue buttons look blue on the phone their customers use.

A short decision sketch

  • HTML files only, paid, preview-first, honest 404s → StaticHost.
  • Need mail + website one invoice → shared host class (different tradeoffs).
  • Need $0 forever → free static hosts.
  • Need server includes or PHP forms → PHP host.
  • Need global cache rules as code → object storage + CDN.

Pick the lane; then package the files correctly. Hosting choice does not forgive a bad zip, and a perfect zip does not need a dramatic platform.

Packaging habits that survive hand-offs

When a nephew, freelancer, or agency delivers HTML files, require a one-page README in the zip that states: site root folder name, how to open preview expectations, and which phone numbers must be checked. You will not host the README publicly if you strip it before upload—but the discipline prevents silent file:// regressions.

Name releases with dates (plumber-2026-03-01.zip). StaticHost deploy history helps, yet local archives help when someone asks what changed last spring. Keep photos resized before they enter the tree; 2 GB on Starter disappears when phone camera originals land in photos/.

If the business later wants online scheduling, link out. Do not force a PHP scheduler onto a static file host. Placement decisions stay clean when each vendor does one job: files here, booking there, mail elsewhere.

Questions people actually ask

Can I drag individual HTML files without a zip?

Workflows center on zip or GitHub of a tree. Treat the site as a folder release, not ad-hoc single-file FTP nostalgia—though the mental model (files on a server) is the same.

Why does my CSS work on my PC but not on the host?

Often file:// or wrong relative paths. Preview with DevTools Network open and repair links so they resolve from the HTTPS origin.

Does StaticHost run server-side includes?

No. Pre-render includes locally into plain HTML before upload.

Which plan for a single brochure?

Starter at $9/mo. Upgrade when you need more sites, staging, or storage beyond 2 GB (Pro $30, Scale $65, Business $130).