How to host a Claude artifact as a live, shareable link
In short
Claude builds working HTML artifacts inside a conversation, but they stay trapped there. 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 real: a dashboard, a calculator, a landing page, a small game, all rendered live in the conversation. The problem starts when you want someone else to see it.
The artifact lives inside Claude, behind your account. There is no public URL to send. Screenshotting it loses the interactivity. Inviting someone into your Claude account is not practical. An artifact is almost always self-contained HTML, which is why it hosts so cleanly as a static site. You just need somewhere to put it.
How to publish a Claude artifact (step by step)
Open the artifact and switch to code view
In Claude, click the artifact to expand it, then toggle to "Code" or "Source" view. You see the raw HTML, CSS, and JavaScript that powers the artifact.
Copy the full HTML
Select all and copy. Claude's code view has a copy button in the top corner that grabs everything cleanly. The output is almost always a single self-contained file.
Paste into NudgeHost
Go to the Claude artifact uploader and paste the HTML directly. No need to save a file first. NudgeHost accepts raw HTML paste.
Share your public link
A short nudgehost.com link comes back in seconds. The page renders full screen, and the link preview unfurls with a sensible title and image when shared in Slack or iMessage.
Updating an artifact without changing the URL
Artifacts evolve. You ask Claude for a second version, it rebuilds the thing, and you want the same link to show the new output. Swap the source in your dashboard and the URL does not change. Everyone who already has the link sees the update on their next visit.
This is the part screenshots and one-off uploads get wrong. Every change means a new file and a new link to redistribute. With NudgeHost, one link serves every version. Unlike hosts that expire free links after 30 days, NudgeHost keeps your artifact live as long as you want.
When to use a ZIP file instead
Most artifacts are a single HTML file. Occasionally Claude splits things across several files, or you have built something larger around it. In that case, zip the files together and upload the archive. NudgeHost unpacks it and serves the whole project as a real site at the site's own subdomain, with index.html as the entry point. Stylesheets, scripts, and images load from the root exactly as you wrote them, and if the project uses a client-side router, direct visits to its routes work too.
If Claude loaded a library like React or Tailwind from a content delivery network, those requests fire as normal from the hosted page. The artifact behaves online exactly as it did in the conversation. The same approach that lets you publish any HTML page handles multi-file projects.
Why NudgeHost over other options
| Feature | GitHub Gist | CodePen | NudgeHost |
|---|---|---|---|
| Live HTML rendering | ✗ (raw code only) | ✓ | ✓ |
| No account to view | ✓ | ✗ (cluttered UI) | ✓ |
| Clean, full-screen view | ✗ | ✗ (split panes) | ✓ |
| Update without new URL | ✗ | ✓ | ✓ |
| Branded link preview | ✗ | ✗ | ✓ |
The short version: GitHub Gist shows raw code with no rendering. CodePen renders HTML but wraps it in a cluttered editor UI and requires an account. NudgeHost gives the recipient a clean, full-screen page with no login wall, no branding chrome, and a branded preview when the link is shared in chat.
Free vs Pro: what you need
The free plan handles artifacts easily. The 25MB limit sits far above the size of anything Claude produces, which is almost always under a few hundred kilobytes. You get 10 active links with no expiry and no visitor cap.
The NudgeHost Pro plan adds password protection and the option to brand your link with a custom domain, both of which matter once the link is going to a client rather than a teammate. If you built a prototype or a pitch tool with Claude, sharing it from yourname.com/pitch lands differently than a generic subdomain.
📖 Also useful
- How to share a Lovable site
Export from Lovable, host on NudgeHost, get a public URL.
- How to host a v0 export
Publish v0.dev projects as live sites in 30 seconds.
- Send a large PDF without email
Skip the attachment limit. Drop a PDF and share the link.
Frequently asked questions
How do I get the HTML out of a Claude artifact?
In the artifact view, switch to the code or source toggle. You see the raw HTML. Copy the whole block. You can also ask Claude directly: "Give me the full HTML source of this artifact."
Does the recipient need a Claude account?
No. The hosted link is a normal public URL. Your conversation never leaves Claude. Only the HTML you paste reaches NudgeHost.
Will external libraries (React, Tailwind) still work?
Yes. If the artifact loads libraries from an external library host, those requests fire normally from the hosted page. The artifact behaves online exactly as it did inside Claude.
What if Claude gives me multiple files?
Ask Claude to inline everything into a single HTML file (it does this reliably). Or zip the files and upload the archive. NudgeHost unpacks it and serves the whole project as a live site at its own link, with index.html as the entry point.
Can I password-protect an artifact link?
Yes. You can lock the link with a password on the Pro plan. The recipient enters a password before seeing the artifact.
Can I use a custom domain for my artifact?
Yes. You can use your own domain to serve the artifact from yourname.com instead of nudgehost.com. Available on Pro and Team plans.
What other file types does NudgeHost support?
PDF, DOCX, ZIP, images, and 20+ other formats. See all NudgeHost hosting options.
Ready to publish your artifact?
Copy the HTML from Claude, paste it into NudgeHost, and get a link. Free, no credit card, no account needed to start.
Get started free