Publish AI-Generated HTML

The publish button turns a private artifact into a public one and gives you a link on claude.ai you can send to other people. Anyone with that link can open it and, depending on your settings, remix it in their own Claude account. What it does not do is give you a website: there's no custom domain, no password protection, no analytics, and no control over how long it stays up or how it's presented. Publishing to Tiiny Host instead gives you a normal URL, your own domain if you want one, and the ability to update the page without changing the link.

Open the artifact in Claude and copy its code, or use the download option if the artifact offers one. Save it as index.html on your computer. Then drag that file onto Tiiny Host, pick a link-name, and publish. Your page goes live immediately on a tiiny.site link, and on a paid plan you can point your own custom domain at it in a few clicks. If your artifact is split across several files — separate CSS, JavaScript or images — put them all in one folder with index.html at the top level, zip the folder, and upload the zip instead.

Yes. Claude Code writes files to your machine, so hosting the result is just a matter of uploading them. For a plain static site, zip the folder containing index.html and drop it on Tiiny Host. For a framework project like React, Vue, Astro or Next in static-export mode, run your build command first and upload the output directory — usually dist or build. Tiiny Host serves static files, so anything that compiles down to HTML, CSS and JavaScript works. You don't need to connect a git repository or configure a deploy pipeline, which is what makes it a fast way to check that a Claude Code build actually works in the wild.

It does. Nothing about Tiiny Host is Claude-specific — if your AI tool can hand you HTML, we can host it. That covers ChatGPT canvas exports, Gemini output, Cursor and Copilot projects, and the files you export from builders like Lovable, Bolt or v0. Save the code as index.html, or zip the project folder if there's more than one file, and upload. The publishing steps are identical regardless of which model wrote the code.

No. The whole point is that you don't. You don't need to understand what's inside the file, install anything, use a terminal, or learn git. If you can save a file and drag it into a browser window, you can publish it. The most common stumbling block has nothing to do with code: your main file has to be named index.html, and if you're uploading a zip, index.html needs to sit at the top level of the folder rather than nested inside another one. Get that right and the rest is a single click.

Yes, and this matters more with AI-generated pages than most, because you'll almost certainly ask for another revision. Go back to your Tiiny Host dashboard, upload the new file over the old one, and the same link serves the updated version straight away. Anyone you already sent the link to sees the new page next time they open it. There's no need to publish a second site or send out a corrected URL every time Claude tweaks something.