In short
Claude builds working HTML artifacts inside a conversation, and NudgeHost can host one as a page of its own. Copy the source and paste it into NudgeHost, and you get a public link in seconds. No Anthropic account needed for the recipient. Update the source later and the link stays the same.
Why Claude artifacts are hard to share
Claude's artifacts feature turns a prompt into something that runs, such as a dashboard, a calculator, a landing page or a small game. The result appears in a panel beside the conversation.
Claude has its own Publish and sharing controls, and what they allow depends on your Claude plan. If you would rather own the page, you can host the code yourself and manage it from a NudgeHost dashboard, where you can replace it, set it to expire or delete it. An artifact that is a single HTML file needs no changes for static site hosting, so the only job left is finding a place to put it.
How to publish a Claude artifact (step by step)
Open the artifact and view its code
In Claude, open the artifact and use the controls on the artifact panel to view its code. For an HTML artifact you see the markup, the styles and the script.
Copy the full HTML
Copy everything in the code view. If you cannot find a copy control, ask Claude to print the complete HTML in a single code block and copy that instead.
Paste into NudgeHost
Open the Paste HTML tab of the uploader, paste the source and press Publish. Nothing has to be saved to disk first, since you can paste HTML straight into the uploader.
Share your public link
Your link comes back in seconds, in the form nudgehost.com/your-name. It is a public link that needs no account to open. The page opens in the hosted viewer, under a slim NudgeHost header that shows the file name and a Download button. In a chat app that shows link previews, the link unfurls with the page's title.
Updating an artifact without changing the URL
Artifacts change. You ask Claude for a second version, it rebuilds the page, and you want the same address to show the new one. Save the new HTML as a file, open the link's settings in your dashboard and choose Replace file. The URL stays the same, and anyone who already has it sees the update the next time they open it.
A screenshot or a fresh upload would mean a new file and a new link to hand out again. With Replace file, one link serves each version in turn, and the page stays up until you delete it or set it to expire. If you are weighing hosts, a side-by-side of NudgeHost and Tiiny.host sets out the limits of each.
When to use a ZIP file instead
Most artifacts are one HTML file. If Claude split the work across several files, or you built something larger around it, put everything in a ZIP with an index.html and upload the archive. NudgeHost unpacks it and serves the project as a site on its own nudgehost.site address, with index.html as the entry point. Stylesheets, scripts and images load from the root as you wrote them, and a path with no file behind it returns the entry page, so a client-side router can take over on a direct visit.
Why NudgeHost over other options
| Feature | GitHub Gist | CodePen | NudgeHost |
|---|---|---|---|
| No account to view | Yes | Yes | Yes |
GitHub's documentation says anyone you send a gist's URL to can see it, and CodePen's says public Pens can be seen by anyone. A NudgeHost link works the same way for the viewer. What you get around it is a dashboard for replacing the file, setting an expiry date and reading open counts, plus a password on Pro and Studio.
Free vs Pro: what you need
The free plan handles artifacts comfortably. Its 25MB file limit fits a single HTML page with room to spare, and it keeps 10 links live at once with no cap on visitors. Without an account a link lasts 7 days, and you can hold 3 at a time until you sign up.
A paid plan raises those ceilings. The Pro plan costs $12 a month, lifts the file limit to 250MB and removes the cap on live links. Studio costs $29 a month and takes files up to 1GB.