Why Publishing Now Needs an Account — and Why We Didn't Want to Ask

host-html was built on one promise: drop HTML, get a URL, no login. We just broke that promise on purpose — and you deserve the honest reason why.

The whole point was no login

host-html started with one stubborn idea: publishing a web page should take seconds, not a signup flow. Drop an HTML file, get a URL. No account, no config, no deploy pipeline. That friction-free path is the reason a lot of you use it — from Claude Code, from a terminal, from a paste box at 1 a.m.

So this is genuinely uncomfortable to write: you now need a free account to publish.

We'd have rather not. We held out on this longer than we probably should have. But we ran out of good options — and I'd rather tell you exactly why than hide behind a vague "for security reasons" notice.

What went wrong

The same thing that made host-html great made it a target.

Anonymous, instant, free publishing is a gift to whoever is building a phishing page. Spin up a fake login screen, grab a link in two seconds, blast it out, and disappear — no account, no trail, nothing to ban. Because there was no one behind a page, there was no one to hold accountable.

At our scale, that stopped being a rare edge case. The overwhelming majority of pages on host-html were published anonymously, and a steady trickle of them were outright scams.

The part that actually forced our hand

Here is the thing about a shared platform: abuse does not stay contained to the abuser.

Because phishing pages lived on the same domain as everyone else's legitimate work, security vendors did the rational thing and flagged the entire domain as phishing. Corporate firewalls started blocking host-html.com outright — which meant your perfectly innocent portfolio, your client demo, your AI-generated deck could get blocked at the office, through no fault of your own.

The cost of the free-for-all had quietly shifted onto the people using host-html honestly. That is the line we could not let stand.

What we changed (and what we didn't)

Publishing now requires a free account with a verified email. That is the whole ask. Not a paywall, not a long form, not a phone number — a five-second signup, and you are back to dropping HTML and getting URLs.

We worked hard to keep everything else exactly as frictionless as before:

• Your content is never held hostage.: Paste or drop your HTML and preview it just like always. The account only comes up at the moment you hit Publish — and your work is waiting for you when you get back.
• Automation still works.: Publishing from the API, a CLI, or an AI agent like Claude Code? Generate a personal API key once and keep going. The old shared key is retired; the workflow is not.
• Everything you already published is safe.: And if you made anonymous pages before the change, you have a short window to claim them to your account and keep them live.

A verified account is not a silver bullet — nothing is. But it raises the cost of abuse from zero to enough, and it gives every page an owner. That alone flips the economics for the people who were exploiting us.

The honest version

I do not love adding a wall. The no-login promise was a real one, and breaking it stings. But "anyone, anonymously, instantly" only holds up until someone decides to weaponize it — and when they do, the bill lands on your most loyal users, not on the person causing the harm.

So we made the trade we had been avoiding: a few seconds of your time, in exchange for a platform that does not get the whole neighborhood blocklisted because of its worst tenant. I think it is the right call. I just wish we had not had to make it.

Thanks for sticking with us — now go make something and publish it →.