Deploy Claude Artifacts sites with VibeDeploy
Claude artifacts are self-contained HTML, React, or SVG pieces built inside a conversation. VibeDeploy turns any artifact into a real URL with a custom domain, in under a minute.
Why VibeDeploy for Claude Artifacts
Claude artifacts live inside the chat. They're great for prototyping and demos, but you can't share a URL with a non-Claude user. To deploy an artifact, you need to extract the code and host it.
Single-file deploys
Most artifacts are one HTML file or a small React component. VibeDeploy accepts them as-is. No build step, no framework setup. Drag the file, get a URL.
Magic file for Claude Code
Claude Code can read .vibedeploy.txt and ship an artifact directly from a conversation. No copy-paste back to a browser.
Sub-minute time-to-URL
Save artifact, drag to VibeDeploy, get a vibedeploy.be URL. Add a custom domain in 30 more seconds. End-to-end under a minute.
How to deploy a Claude Artifacts site
- 1
Save the artifact
In Claude, click the artifact's download icon, or copy the HTML/code into a local file (e.g. index.html).
- 2
Sign up for VibeDeploy
Free plan covers 1 artifact site at no cost. No credit card required.
- 3
Drag and drop
From the dashboard, choose New Site and drag your artifact file (or folder) into the upload area. VibeDeploy serves it as a static site.
- 4
Add a custom domain (optional)
If you want artifact.example.com instead of artifact.vibedeploy.be, point a CNAME at VibeDeploy and add the domain in site settings.
- 5
Or, deploy from Claude Code in one shot
If you're using Claude Code, drop a .vibedeploy.txt in your working directory. Tell Claude to deploy. It does the rest.
# .vibedeploy.txt project: my-claude-artifact token: vbd_xxx framework: static
Claude Artifacts hosting at a glance
How Claude Artifacts's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Claude Artifacts default / generic alt | VibeDeploy |
|---|---|---|
| Hosting location | US/Cloudflare global | EU (Belgium) |
| Custom domain free | Yes (GitHub/Netlify) | Yes |
| Claude Code integration | No | Yes (magic file) |
| Drag-and-drop deploy | Yes (Netlify Drop) | Yes |
| GDPR DPA available | Enterprise | All paid plans |
Common questions about deploying Claude Artifacts
Do React artifacts deploy without a build step?expand_more
Single-file React artifacts (the kind that use the in-browser Babel + React UMD pattern) deploy as plain HTML. If your artifact has a build step (TSX with imports), run npm run build locally first, then deploy the dist folder.
Can I deploy multiple artifacts under one domain?expand_more
Yes. Each artifact can be its own site (artifact1.vibedeploy.be, artifact2.vibedeploy.be) or you can put them in subfolders of one site (example.com/artifact1, example.com/artifact2).
What about artifact features that need Claude's runtime, like the Mermaid renderer?expand_more
Artifacts that depend on Claude's chat-side rendering (some Mermaid integrations) need an equivalent client-side library. For Mermaid specifically, include Mermaid.js via CDN in the deployed HTML. Most other artifacts work standalone.
How does this differ from GitHub Pages or Netlify Drop?expand_more
VibeDeploy hosts in the EU (Belgium), supports custom domains free on every plan, and integrates with Claude Code via the magic file. GitHub Pages and Netlify Drop are US-based and have separate workflows.
Ship your Claude Artifacts project today
Free plan, no credit card. Custom domain in 60 seconds. Hosted in Belgium.