How to host a Claude artifact

Claude's artifacts feature turns a prompt into something working in front of you: a dashboard, a calculator, a landing page, a small game, rendered live in the conversation. The problem starts the moment you want someone else to see it. The artifact lives inside Claude, behind your account, and there is no public URL to send. Screenshotting loses the interactivity, and inviting someone into your Claude account is not an option.

The fix takes about thirty seconds. Open the artifact in Claude and switch to its code or source view, which shows the underlying HTML. Copy the whole block. Then you publish a Claude artifact by pasting that HTML straight into NudgeHost, with no file to save first. A public link comes back, and anyone who clicks it sees the working artifact in their browser. They need no Anthropic account, and they never see your conversation.

An artifact is almost always self-contained HTML, which is why it hosts so cleanly. See what a static site is for the longer explanation of why files served as they are load fast and need no server. If Claude loaded a library like React or Tailwind from a CDN, those requests fire as normal from the hosted page, so the artifact behaves online exactly as it did in the conversation.

Most artifacts are a single HTML file, but occasionally Claude splits things across several files, or you have built something larger around it. In that case the same approach that lets you publish an HTML page handles the rest. Zip the files together and upload the archive, and NudgeHost unpacks it and serves the index as the entry point. Either way the result is a single clean URL.

The link you get is short and on nudgehost.com, the kind of URL you can paste into a Slack message or a tweet without it looking suspicious. The page renders full screen, and when you share it the preview unfurls with a sensible title and image, so the link reads as intentional rather than broken.

Artifacts evolve. You ask Claude for a second version, it rebuilds the thing, and you want the same link to show the new one. Swap the source in your NudgeHost dashboard and the URL does not change, so everyone who already has the link sees the update on their next visit. This is the part screenshots and one-off uploads get wrong, where every change means a new file and a new link to redistribute.

The most common next step is showing the artifact to someone whose opinion matters. If Claude built you a pitch tool or an interactive prototype, you can send a presentation as a link and send the live link as the working demo rather than a slide about it. A client clicking a real, working thing lands differently than a screenshot in a deck.

Hosting an artifact is free, and the 25MB limit on upgrade to Pro sits far above the size of anything Claude produces, which is almost always under a few hundred kilobytes. The paid tiers add custom domains and password protection, both of which matter once the link is going to a client rather than a friend. If you just want to try it, you can drop a file to get started with the artifact HTML right now.