Publish the Website Claude Built You — No GitHub, No Vercel

First figure out what you're actually holding, because it decides everything else. Three cases:

1. A single .html file. The usual output for a landing page — styling, scripts, often the images, all baked into one file. This is the simplest case: upload one file to a host.

2. A folder of files — index.html plus style.css, maybe script.js, and an images/ or assets/ folder. Bigger builds do this. The number-one beginner mistake lives here: uploading only index.html and getting a live page that's an unstyled, image-less mess. Upload the whole folder together, and the homepage file must be named exactly index.html — lowercase.

3. A Claude Artifact still in the chat — you haven't downloaded anything. There's a shortcut here, covered at the end of the options.

To tell which you have, open the file in any text editor. If the <style> and <script> are right there in the file and you see no <link href="style.css"> or <img src="images/hero.jpg"> pointing at separate files, it's the easy single-file case. If you see references to other files, it's a folder and all of it travels together.

Real public hosts first, because that's the job most people here have.

Method 1 — Drag-and-drop hosts (start here)

No git, no terminal, and you can start without even an account.

• Cloudflare Pages direct upload — in the dashboard, go to Workers & Pages and drag your files in. You get a project.pages.dev address, free HTTPS, free custom domains, and unlimited bandwidth on the free plan — its standout feature. Real limits: direct upload caps at 1,000 files and 25 MiB per file (irrelevant for one page, matters for a heavy asset folder). One gotcha worth knowing upfront: a project created by direct upload can't later be switched to auto-deploy from Git — you'd make a new project. For most people here that never comes up.

• Netlify Drop — drag your file or folder onto the page, get an instant random-name.netlify.app URL with free HTTPS and free custom domains. The free plan has usage limits — check the current numbers on Netlify's pricing page before you lean on it for anything heavy. The trap: a fresh drop is anonymous. Close the tab without signing up and "claiming" the site and you can't manage or update it — it's out of your hands. Claim it right away.

• Tiiny.host — arguably the most non-technical of all: drag a single HTML file (or a zip), get a *.tiiny.site link. Free tier exists, but password protection and custom domains are paid. The "simplest possible thing, and I'll pay a few dollars for a password or domain" option.

• Neocities — free static hosting, drag-and-drop, friendly community. Great for a personal or hobby page on a subdomain.

Method 2 — GitHub Pages in the browser (no terminal, but not jargon-free)

You can do this without touching git: make a GitHub account, create a new public repo, use the web "Add file → Upload files" button, then Settings → Pages and set the source branch. Your site lands at username.github.io/repo, free, with free custom domains and HTTPS.

Honest take: this is the most conceptually heavy of the beginner paths — repos, branches, a Settings toggle — and it has a famous trap. GitHub Pages URLs are case-sensitive. If your file is Logo.PNG but the HTML says logo.png, it works on your laptop and 404s once live. That's the classic "why are my images broken online but fine locally?" A deploy also takes a minute to appear, which feels broken when it isn't. Wait before you panic.

Method 3 — Vercel and the CLI/git world (the path you were escaping)

Vercel's current getting-started is command-line first (npm i vercel, vercel login, vercel) or connect a GitHub repo in the dashboard — it assumes Node 18+ and either a terminal or a repo. The free Hobby tier and free custom domains are real and good. But plainly: Vercel and Netlify's git integrations shine when you'll keep editing in a developer workflow. For one HTML file, this is exactly the machinery that's been sending you in circles. Skip it unless you know you want it. (Vercel's old drag-and-drop deploy is effectively gone — don't go hunting for it.)

Quick preview only — share the Claude Artifact

If the page is still a Claude Artifact and you just want to show someone fast, Claude's own share/publish button gives you a claude.ai URL in seconds, zero tools. But know what it is before you send it: the link is public — anyone who has it can open the page — and it may carry some Claude branding. Artifacts are for prototypes, not production sites: third-party API calls and persistent storage are unavailable, and the page stays on Claude's infrastructure. Fine for "let me show a friend this thing I made," wrong for "this is my business's homepage." (Claude's buttons move around over time, so look for the share/publish control, not a specific spot.)

Which one fits you?

For most people who want a normal public website that search engines are allowed to index, on their own domain, for free: Cloudflare Pages or Netlify Drop. That's the honest first pick. Publishing alone does not guarantee a Google listing, though — submit the domain through Google Search Console if discovery matters.

One situation the free public hosts don't cover, worth naming because it's a different job: you're not publishing a public marketing site — you're sending a page to specific people. A proposal, a client one-pager, a portfolio for a recruiter, a pitch. You'd like it private or password-protected, and you'd genuinely like to know whether and when it got opened, for how long, and from which country. The static hosts give you none of that. That's the slot Pagelive fills: pages are private and non-indexed by default, you can password-protect them, and views are tracked — whether and when the link opened, how long the viewer stayed, and top countries. The free tier publishes up to 5 pages with no credit card; a custom domain is a paid upgrade.

And where it's the wrong pick: if you want a public site that ranks in Google on your own domain for free with unlimited bandwidth, that's Cloudflare Pages — Pagelive is built around tracked private links, not being your SEO homepage. For a quick "show a friend" link where Claude branding is fine, just share the Artifact. Match the tool to the job you actually have.

A custom domain is optional. If you want one, the shape is the same everywhere — learn it once:

1. Buy a domain — registration usually costs about $10–15/year for a .com. Cloudflare Registrar sells at cost with no markup; Namecheap and Porkbun are fine too. The hosts above offer free plans (with usage limits), so the domain is typically the only cost.
2. Add the domain in your host's dashboard first — before you touch any DNS. Order matters.
3. Point DNS. For www, the host will usually give you a CNAME target (e.g. your-project.pages.dev) to add at your registrar. For the bare/apex domain (example.com), follow that host's exact dashboard instructions — Cloudflare Pages, for instance, requires the domain to be an active Cloudflare zone. Cloudflare's docs warn specifically: register the domain in the dashboard first — a manually added CNAME without that step fails with error 522.
4. Wait for SSL. The HTTPS certificate provisions automatically but can take minutes to an hour. A "not secure" warning right after setup is almost always the cert still catching up, not a mistake. Also pick www vs non-www and set a redirect so both resolve.

You're not missing a secret dev step — the last 10% just got wrapped in jargon written for someone else's problem. Want a normal public site on your own domain for free? Drag your file onto Cloudflare Pages or Netlify Drop and you're done in minutes. Sending it to specific people and want to know whether and when it got opened? That's a different tool. Still in Claude and just showing a friend? The fastest link is the one Claude hands you directly. Pick the one that matches what you're actually trying to do, and stop reading tutorials aimed at developers.