Personal HTML deserves a boring host

A personal HTML website is identity in files: about page, projects, maybe a resume PDF. Where to host it should optimize for ownership of the domain, HTTPS without drama, and zero desire to patch servers at midnight.

StaticHost offers that boring path: zip or GitHub of your files, local builds only (no remote npm/Hugo), HTTPS preview then DNS then certificate, nginx try_files $uri $uri/ =404 without SPA fallback, no email, no CDN product, plans $9/$30/$65/$130, no forever-free tier after a short trial.

Related: hosting for a simple html website, host a personal html website, static website hosting for personal projects.

What this host is

A paid file host for personal sites that outgrew “free subdomain forever” or never wanted it. Clear quotas. Rollback. Custom domain support with verified certificates.

What this host is not

Not a social network. Not a mailbox. Not a PHP diary app. Not a free student commons (use Pages-class hosts if $0 is required). Not an SPA rewrite service.

Decision criteria for personal sites

  • Domain ownership. Prefer hosts that play well with registrar DNS you control.
  • Learning goal. If the goal is learning Linux, use a VPS. If the goal is a public page, do not.
  • Budget. $9/mo is fine for a long-lived personal brand; forever-free is fine for class throwaways.
  • Stack honesty. Hand HTML and static exports fit; WordPress does not.
  • Privacy of packaging. Do not upload .env or private notes beside index.html.

Worked example: student class project

You need a personal HTML site for a web design course: index.html, process.html, and a css/ folder. The syllabus says “must be publicly reachable via HTTPS.”

Where to host: If the course requires $0, use a forever-free static host. If you already use StaticHost or want the same workflow you will use for clients, Starter ($9) works—build nothing remotely, zip the folder, preview, optional domain. StaticHost will not grade you; it will serve files. Do not invent a React SPA with history routes unless you prerender—deep links 404 here.

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

Students often develop by double-clicking index.html. Some tutorials accidentally encourage absolute local paths. On a real host, file:// stylesheets never load. The personal site looks unstyled and “broken hosting” gets the blame.

Criterion when choosing a host: can you verify on HTTPS preview quickly? StaticHost yes. Open preview, fix href="css/site.css", redeploy, then add DNS. Teaching yourself relative paths is part of hosting HTML personally; the host will not rewrite laptop paths.

Personal-site selection sketch

  • Want paid, simple, file-based → StaticHost.
  • Want $0 class project → free static hosts.
  • Want blog with server CMS → PHP/WordPress host.
  • Want full DevOps practice → VPS.
  • Want framework remote builds → JAMstack build platforms.

Questions people actually ask

Is $9/mo worth it for a personal site?

If the domain matters commercially or you want staging later, yes. If it is a weekend experiment, free hosts may suffice.

Can I connect GitHub Pages and StaticHost at once?

You can move between them because your artifact is files. Point DNS at one origin at a time.

Does StaticHost give me email like old shared hosting?

No. Use a mail provider separately.

Why do my React routes 404 on refresh?

No SPA fallback (try_files … =404). Use hash routing or generate HTML per route before upload.