Getting a static HTML site online, then giving it a backend
Upload the files to a static host first: ship.page publishes with no account (10 MB HTML, 25 MB ZIP, link lasts 7 days), while Cloudflare Pages (20,000 files) and GitHub Pages (1 GB) host for $0 with an account. Then add forms, storage, data and realtime from hosted APIs.
Updated
# No account: one HTML file, live in about 2 seconds
curl -X POST https://ship.page/deploy \
-H "Content-Type: text/html" \
--data-binary @index.html
# Free Cloudflare account: a whole folder, no expiry
npx wrangler pages deploy ./site --project-name my-site
The ship.page call returns JSON with the live url on a *.ship.place address, expires_at and a one-time claim_token. Claiming the page with a free account keeps it for 30 days from upload, and Pro at $4 a month removes the expiry while you stay subscribed (ship.page quickstart). Wrangler opens a browser to log in to Cloudflare on the first run, then uploads the folder to a Pages project that stays up until you delete it (Pages direct upload).
In our November 2026 upload test from Frankfurt, a 4 MB HTML file was live on ship.page 2.2 seconds after the command started, while a new Cloudflare Pages project served it at its production URL after about 10 seconds, plus 3 seconds to create the project. The methodology page has the full setup.
Choosing a static host by how long the link has to live
| Host | Account | Free link lifetime | Free size limit | Custom domain on free |
|---|---|---|---|---|
| ship.page | None | 7 days, or 30 days after a free claim | 10 MB HTML, 25 MB ZIP, 100 files | No; Team at $19 a month, and Pro at $4 a month adds 5 ship.place names |
| Cloudflare Pages | Free Cloudflare account | No expiry | 20,000 files, 25 MiB each | Yes, 100 per project |
| GitHub Pages | GitHub account and a public repo | No expiry | 1 GB site, 100 GB a month soft bandwidth | Yes |
| Netlify Drop | None to deploy, free account to keep it | Claim within 1 hour | No published total cap | Yes, with SSL |
Use ship.page when the link is for a review, a client preview or an AI-generated page you want to send right now. Use Cloudflare Pages when the site should stay up on your own domain and creating an account is fine. Use GitHub Pages when the HTML already lives in a public GitHub repo, keeping in mind that GitHub does not allow Pages to run an online business, an e-commerce site or SaaS (GitHub Pages limits). Netlify Drop also skips the account, but its docs say an anonymous deploy has to be claimed within one hour (Netlify deploys).
The scored comparisons are the free HTML hosting test, where ship.page leads at 84/100 for publishing with no signup, and the Netlify Drop alternatives test, which scores the hosts people move to when a Drop link expires.
What a static site cannot do on its own
A static host serves files and nothing else: no code runs when a visitor submits a form, uploads a photo or sends a chat message. Each of those jobs has a hosted service with a free tier that the page can call directly:
- Forms: post straight to Web3Forms (250 free submissions a month) or Forminit (100 a month with 100 MB of files). See the forms guide.
- File uploads: a small Worker signs a short-lived PUT URL into Cloudflare R2, which includes 10 GB-month of storage and charges no egress. See the storage guide.
- Data: Supabase from the browser with row level security, 500 MB of Postgres for $0. See the database guide.
- Live updates: WebSockets on Cloudflare Durable Objects, 100,000 requests a day on the free plan. See the WebSockets guide.
The one security rule for static sites with a backend
Every byte of a static site is public. Anyone can open view-source or the network tab and read every key, URL and comment you shipped. Only put keys in the page that are built to be public: a Web3Forms access key, a Supabase publishable key with row level security enabled on every table, a Pusher app key. Anything that can write without rules belongs in a Worker or function and never in HTML. That includes a Supabase service role key, R2 access keys, a Turso auth token and SMTP passwords.
The second rule follows from the first: whatever the page can call, a script can call too, thousands of times. Free tiers are small (50 form submissions a month on Formspree, 50,000 Firestore reads a day), so rate limit anything that writes or signs, and cap the size of what it accepts.
Deploying from a terminal or CI
The command line guide covers the curl call to ship.page, Wrangler for Cloudflare Pages, Surge, and Netlify's anonymous deploy flag, plus GitHub Actions setups for ship.page and Cloudflare.
What happened to the original StaticBackend project
StaticBackend started as an open-source backend for static sites, written in Go and published under the MIT license at github.com/staticbackendhq/core. The repository is now archived, with 744 stars and 71 forks, so it receives no new releases. staticbackend.com now covers the same problem with hosted services: which ones give a static site forms, storage, data and realtime in 2026, what their free tiers allow and what they cost. The original code is still on GitHub if you want to self-host it.
Frequently asked questions about putting HTML online
How do I turn an HTML file from ChatGPT or Claude into a link?
Save the output as index.html and drop it on ship.page, or send it with the curl command above. You get a public https link on ship.place with no account; it stays live for 7 days, or 30 days if you claim it with a free account. For a permanent free link, upload the same file to Cloudflare Pages after signing up.
Can I host an HTML site for free forever?
Yes, with an account. Cloudflare Pages and GitHub Pages keep sites online with no expiry for $0, and both take a custom domain. Surge does the same from the terminal. Hosts that skip the account step, such as ship.page and Netlify Drop, trade that for links that expire after 7 days or 1 hour unless you sign up.
Do I need a server for a contact form?
No. Point the form's action at a form service such as Web3Forms, which handles 250 submissions a month for $0 and emails you each one. The forms guide has a copy-paste example and the limits of the alternatives.
Official pricing and documentation sources
- ship.page quickstart
- ship.page pricing
- Cloudflare Pages direct upload
- Cloudflare Pages limits
- GitHub Pages limits
- Netlify deploys
- Netlify pricing
- StaticBackend core on GitHub
Related static site guides