Got A Claude HTML File? Put It Online In A Minute
Claude built the page and left you with code. Here is how to put your Claude HTML file online in about a minute, with no git, no build step and no terminal.
The OxyPages Team · · 9 min read
You asked Claude for a landing page. It built one, the preview looks right, and now you are staring at a few hundred lines of code with no idea what turns that into a link you can send someone.
That is where most people stall. Every guide starts with "install Node" or "create a repository", and you did not set out to become a developer.
You need none of it. Search "Claude HTML file" and you mostly get framework arguments. The truth is much smaller: what Claude handed you is already a finished website, and it just needs an address.
I have published a lot of these, for clients and for myself, and it has never once needed a terminal. Copy, paste, publish. The page is live at a real URL and you can send it to anyone.
The parts worth thinking about come after that: what address it lives at, how you change one sentence later without regenerating the page, and the few things a page like this cannot do.
That last one is what people find out too late.
TL;DR: What Claude gives you is one self-contained document, with the styling and scripts already inside it, so there is nothing to build. Copy the code out of the artifact panel, paste it into any static host, and you have a live URL in under a minute. Stay on a free subdomain while it is a draft, and buy a domain when the page represents you commercially. Two things actually go wrong: a copy that stops short of the closing </html> tag, and images that break once the page moves.
What A Claude HTML File Actually Is
It is one document holding the entire page: the structure, the styling and any behaviour. When Claude builds you a landing page or a portfolio inside an artifact, it deliberately writes the CSS and the JavaScript inline instead of splitting them into separate files.
That matters more than it sounds.
A normal web project is dozens of files that reference each other, and getting it online means preserving that structure exactly. One self-contained page has no such problem. There is nothing to wire up, so nothing can come unwired on the way.
So treat it like a document, not a project. Copy it, paste it, and it works.
The same is true of what comes out of ChatGPT, v0 or a Lovable export, which is why hosting an AI-generated site is the same three steps whichever model wrote the page.
Getting The Whole Thing Out Of Claude
There are two ways, and the one you pick barely matters.
Open the artifact, find the copy button in its top corner, and click it. The whole page is now on your clipboard. Some artifacts also offer a download that saves an .html file to your computer, which is worth doing before you change anything.
If the code arrived as a block inside a normal reply rather than an artifact, select the block and copy that. Check you have everything from the opening <!DOCTYPE html> line to the closing </html> tag.
A copy that stops short renders as half a page, the top fine and the bottom missing. It is the most common reason a first attempt looks wrong, and people blame the host for it.
How Do You Put It Online?
You paste the code into a static host and press publish. That is the whole mechanism, and it works the same way on every host worth using.
- Pick a static host that accepts pasted code or a dropped file. At this size most are free.
- Paste the code in, or drag the
.htmlfile onto the page if you downloaded it. - Give the page a short name. It usually becomes part of the address.
- Publish, and copy the URL it hands back.
- Open that URL on your phone before you send it to anybody.
That is genuinely the whole process. The page is live at a real address and it works on any device.
What I would not do at this stage is wire up a deploy pipeline. Netlify, Vercel and GitHub Pages are built for projects with a build step and a repository, and I use them happily for work that has a repo. Setting one up around a single page means an account, a git provider and a pipeline to learn, for something that needed none of it.
The first two do have a shortcut: Netlify Drop and Vercel Drop take a dragged folder, no git, no terminal.
Why Not Just Email The File?
Because it usually does not open as a web page on the other end. Depending on their setup it downloads silently, opens in a text editor as a wall of code, or gets stripped by a mail filter for looking like a script.
A URL works on any device, with nothing to explain. That is the entire reason to bother publishing.
The One That Came Out Broken
Here is the failure I run into most, assembled from the pages that have gone wrong on me.
A client wanted a one-page site for a workshop. Claude produced the whole thing in one artifact: a hero, a schedule table, a signup button and a photo of the venue. It looked perfect in the preview, so I copied it, pasted it into a host, published and sent the link.
Two minutes later he replied asking why there was a broken image icon where the photo should be.
Nothing was wrong with the host or with my copy. The page was pointing at the photo using an address that only existed inside the chat session, and once the page lived somewhere else that address meant nothing.
The fix took a minute. I saved the photo, put it in a folder beside the .html file, changed the reference to images/venue.jpg, then uploaded the folder instead of pasting the code. Most hosts that take a paste will also take a dropped folder, and a folder keeps a page and its pictures together.
So do this every time: open the published page and actually read it. A broken image icon means the page is reaching for something it can no longer see. Fonts fail the same way, only more quietly, which is why a heading sometimes looks different once it is live.
Subdomain Or Custom Domain?
Use a free subdomain while the page is a draft, and buy a domain the moment it represents you commercially. That is the whole decision.
| Free subdomain | Custom domain | |
|---|---|---|
| Address | your-page.somehost.com | yourbusiness.com |
| Cost | Free | Roughly $15 a year for a .com |
| Ready in | Seconds | Minutes, plus DNS propagation |
| Best for | Drafts, client previews, personal projects | Anything a customer or an employer sees |
| Reads as | A work in progress | A real business |
For sharing a draft or showing a client an idea, the subdomain is the correct answer and paying for a domain is a waste. Nobody judges the address of a work in progress.
For anything commercial, buy the domain. The address is the first thing people judge, usually before they have read a word of the page. The custom domain answers in the FAQ cover the DNS side if you go that way.
How Do You Edit It Later Without Starting Over?
Edit the published page directly, and go back to Claude only when you want something genuinely new.
The loop most people fall into looks like this. You publish, you spot a typo, you go back to the chat, ask for a fix, wait while the whole file regenerates, then copy and re-paste all of it. It works. It is also slow, and every regeneration is a chance for the model to quietly change something you liked.
Three better habits:
- Edit the code in the host, if it has an editor. Fixing a word of copy takes seconds and nothing else on the page can move.
- Describe the change instead. Some hosts include an AI editor that rewrites the page in place, so "make the heading bigger and the button green" alters those two things and nothing else.
- Keep a local copy of every version you publish. A bad edit is then one paste away from being undone, which matters more than it sounds at 11pm.
The thing to avoid is any workflow where changing one sentence means regenerating the whole page.
What A Static Page Cannot Do
A static page shows the same content to every visitor and runs no code on a server. So it cannot log people in, query a database, take a payment by itself, or run a WordPress plugin. Better to know that now than after you have built half a product on it.
What it can do covers more than most people expect: any layout, animation or interactivity that happens in the browser, a contact form if your host handles the submissions, analytics, and embedded tools like a booking widget or a payment link. Most landing pages, portfolios, brochure sites and event pages need nothing beyond that list.
There is an upside to the limitation. Nothing is assembled on demand, so the reply starts almost immediately, and the front of the page load is where Google's Core Web Vitals thresholds are usually won or lost.
If you genuinely need accounts and a database, you need an application, and no static host substitutes for one. OxyPages is the wrong tool in that case and I would not talk you into it. A managed WordPress host, or an app platform your developer picks, is the honest answer.
What To Do Next
Get it online first, on a free subdomain, before you change anything else. A live URL you can open on your phone tells you more in ten seconds than another round of edits in a preview pane.
Then, in this order:
- Publish to a free subdomain and copy the link.
- Open it on a phone and read the page top to bottom. Watch for broken images and fonts that changed.
- Fix what is wrong by editing the published page, not by regenerating it.
- Decide whether it has earned a custom domain. If it represents you commercially, it has.
Paste the code into OxyPages if you want the version that takes a minute, or see what the plans actually include first if you would rather look at the numbers before you start.
The hard part was building the page, and Claude already did that. Putting it online should cost you a minute, not an afternoon.
FAQ
Can I Host It For Free?
Yes. A single page uses almost no storage and almost no bandwidth, so most static hosts have a free tier that covers it comfortably. You normally start paying only when you want a custom domain, want the host's branding gone, or need form handling and analytics.
Will It Look The Same Online As It Did In Claude?
Almost always, because the page carries its own styling inside it. The exception is anything it loads from elsewhere, such as a web font or a temporarily stored image. If a heading looks different after publishing, that is nearly always the reason.
Do I Need To Know How To Code?
No. Publishing is copy, paste, click. Reading the code helps if you want to fix a word by hand, but none of it is required to get the page online.
Can I Add A Contact Form To It?
Not with HTML on its own, because a form needs somewhere to send what people type. Some static hosts handle submissions for you, so a plain form in the page collects entries with no backend code. Check whether yours does before paying for a third party form service.
Is A Claude HTML File Different From A Normal Web Page?
No. It is an ordinary web page that happens to have been written by a model instead of a person. Browsers cannot tell, hosts cannot tell, and nothing about it needs special handling, which is why it can be live a minute after you copy it.