Free HTML Hosting In Singapore: What Free Really Gets You

You've got one HTML file and a quote from a sticker printer sitting in your inbox. Maybe Claude wrote the file, maybe a friend did, maybe you typed it yourself.

You want it live at a real address today, on a QR code, without paying anything. That is a reasonable thing to want, and it exists.

Type "free HTML hosting Singapore" into Google, though, and most of the first page is affiliate lists pushing trials that end in a bill.

So here is the version I'd give a friend. Free HTML hosting in Singapore is real, it doesn't expire, and it runs on machines here. But every free tier bills you in something, and the useful question isn't whether it costs money. It's which thing you're paying with.

Sometimes it's a badge on your page. Sometimes it's a public repository holding your source. Sometimes it's a build quota that pauses the site the week it runs out.

This post is the line-by-line version for one file: what $0 covers, what stays paid, what each of the other free hosts restricts, and the four points where free stops being enough. The pillar on HTML hosting in Singapore covers the wider picture.

What Free HTML Hosting In Singapore Actually Covers

Free HTML hosting in Singapore covers one small site completely: the files, the address, the certificate and the traffic, with no card on file and no expiry date.

That last part matters more than it sounds. A plan that is free forever and a plan that is free for 30 days are the same page until the 31st day.

Here's the free plan next to the first paid one, so you can see exactly where the line sits.

Two numbers decide whether the free row works for you: 5 MB and unlimited.

A self-contained page from Claude or ChatGPT is usually under 200 KB, so 5 MB holds it plus a handful of compressed photos. Unlimited traffic means a busy lunch hour of phone scans costs nothing, and that is the number free tiers most often cap quietly.

HTTPS is the step people expect to fight, and there isn't one. The subdomain arrives with the certificate working, so a scanned code opens with no "Not secure" warning. Google's explanation of why HTTPS matters

What Is The Catch On Each Free Host?

Every honest free tier has one, because none of them are charities, and the catches are not the same shape. Here's what each one takes back.

• GitHub Pages: your source is public. On a free account a Pages site lives in a public repository, so anyone can read your HTML. No expiry, no bandwidth bill worth worrying about, but no built-in form handling, and GitHub's terms say Pages isn't for running an online business.
• Netlify: a monthly credit budget. $0 forever, custom domain and SSL included, which is more than most give away. It runs on 300 credits a month and that's a hard limit. When they're gone the site pauses until the month resets.
• Cloudflare Pages: 500 builds a month, and it wants a repository. Custom domains are free and the per-file ceiling is 25 MiB. Cloudflare's published Pages limits The workflow assumes git or its command line tool, and there's no form handling either.
• A static host's free plan, ours included: one site and a badge. No card, no expiry, but one website, 5 MB, and a small pill reading "Powered by OxyPages" along the bottom of the page until you pay.
• A local shared host's free trial: it ends. You entered a card to start it, and in 14 or 30 days it becomes a monthly bill for a plan sized for WordPress, which one HTML file does not need.

Read those as five prices, not a ranking. A public repository is nothing on a hobby project and unacceptable for a client's unreleased page.

If you want them side by side on upload method, custom domains and whether you need git, the honest comparison of free website hosting in Singapore has that table. This post stays on what free costs you rather than which host to pick.

How Do You Put A Hawker Menu Online For Nothing?

You drop the file, check it on your phone, claim it with a free account, and print the QR code. Under five minutes end to end, no card at any point.

Here's the real shape of it. A stall owner at a Toa Payoh food centre asked Claude for a one-page menu: her dishes and prices, opening hours, the days she's closed, and a big WhatsApp button that opens a chat with her number for advance orders.

Claude handed back one index.html with the styling inside it. She wants it on a sticker on the stall front. She does not want a monthly bill for a menu that changes twice a year.

If you're still at the "how do I get the file out of Claude" stage, putting a Claude HTML file online covers that part. From the file onwards:

1. Open the drop zone. Go to the Singapore free hosting drop zone and drag index.html onto it. No account, no card. The anonymous drop zone takes up to 10 files and 5 MB in total.
2. Get the URL. It's live in seconds. Open it on your phone, tap the WhatsApp button to check it opens a chat, and read the hours at arm's length.
3. Claim it. Create a free account and claim the site within 30 minutes, or the anonymous version is discarded.
4. Pick the subdomain. Something short, ideally the stall name, so the address fits on a sticker and someone could type it if the scan fails.
5. Grab the QR code. One is generated for the site. Send it to the sticker printer.
6. Test before you print fifty. Scan the code on screen with two phones, one Android and one iPhone.

Step 6 is the one people skip, and the only one that costs real money to get wrong. A roll of stickers pointing at a typo is a roll of stickers in the bin.

Why The 30-Minute Claim Window Exists

An anonymous drop is a preview, not a home. Anyone can drop a file without an account, so the site has no owner until somebody claims it, and unclaimed sites are discarded after 30 minutes to keep the drop zone from filling with abandoned tests.

In practice: drop the file, look at it, and claim it right then. If you miss the window, nothing bad happens. Your file is still on your computer, so drop it again.

Where Free Stops Being Enough

Free stops at four points, and all four are visible before you hit them, which is the part I care about. A limit you can see is a plan. A limit you discover is a bad afternoon.

A second site. One website is one website. A separate page for catering, or a menu for a second stall, needs the paid tier.

Your own domain. A subdomain on the host's domain is fine on a sticker and fine in a WhatsApp bio. Nobody judges the address of a menu. If you want yourstall.com.sg on a business card, that's a paid plan plus the domain's yearly cost.

More than 30 form submissions a month. If the page takes orders through a form instead of a WhatsApp link, 30 is one good weekend. For a stall the WhatsApp button is the better call anyway: it counts against nothing, and your customers already have the app open.

Anything the server has to do. This one isn't about money at all. A static host serves files: HTML, CSS, JavaScript, images, fonts and PDFs. It does not run PHP, WordPress or a database, on the free plan or any paid one.

So an ordering system that tracks stock, takes payment on the page and logs customers in is an application, and no static host will run it. If that's what you're building, OxyPages is the wrong tool and I wouldn't try to talk you into it. Use a proper ordering platform and let your free menu page link to it.

Everything short of that runs fine on $0: a menu, hours, a map embed, a photo of the stall, a PDF of the full menu, a WhatsApp button, and a small lead form if you add the form attribute and set the spam-check keys once.

What To Do Next

Drop the file before you decide anything. A live page on your phone tells you in ten seconds whether the menu reads well at arm's length, and finding out costs nothing.

Drop your index.html on OxyPages, claim it inside 30 minutes, and print exactly one sticker before you order the roll.

Then let it sit on the free plan for a month and watch which limit you touch first. Most people never touch one. If you do, you'll know exactly which line you crossed and what it costs to fix, which beats guessing at a pricing page in advance.

And if the badge is the thing you can't live with, that's a fine reason to pay. Just pay for that, knowingly, and not for a hosting plan you were told you needed.