Claude is great at building the page. Sharing it is where it stops.
An artifact is a real, working web page. It just lives somewhere your visitors can’t get to without an account — and, in the new Claude experience, can’t get to at all without one.
Every viewer needs a Claude account
Artifacts shared from the Share dialog — everything made in the new Claude, in Claude Design, Slides, Docs or Code — can only be opened by someone signed in to Claude. Your client, your customer, your mum: sign-in wall.
It’s on claude.ai, and Google is told to ignore it
Even the older public artifact links live on an Anthropic address with a noindex, nofollow tag. Nobody will ever search their way to it, and you can’t put your own domain on it.
It lives and dies with the chat
The artifact is tied to the conversation that made it. Unpublish it and that’s permanent — it can’t be re-published and its stored data is deleted. A link that depends on your Claude subscription is not a link you put on a business card.
Sharing behaviour as described in Anthropic’s Help Center article Publish and share artifacts (September 2026). Publishing to a public link is available only for chat artifacts on the previous experience.
What you get when the same HTML lives on Fylo
Two ways Claude can hand out an artifact, next to what the identical file does once it’s hosted. Nothing about the code changes — only where it lives.
| What you need | Fylo.Host | Claude Share linkNew experience, Design, Slides, Docs, Code | Claude Publish linkChat artifacts, previous experience |
|---|---|---|---|
| Opens without a Claude account | ✓ | ✗ | ✓ |
| Your own URLSubdomain free, custom domain on paid plans | ✓ | claude.ai/… | claude.ai/… |
| Indexable by Google | ✓ | ✗ | noindex |
| Working contact formSubmissions to your inbox | ✓ | ✗ | ✗ |
| Visitor analytics, bots excluded | ✓ | ✗ | ✗ |
| Multi-page site with images | ✓ | ✗ | ✗ |
| Edit after publishing | Dashboard editor | In Claude | Unpublish is permanent |
| Minified and served from the edge | ✓ | ✗ | ✗ |
| Ask Claude questions inside the pageAI-powered artifacts | ✗ | ✓ | ✓ |
Claude artifact to live website in three steps
About two minutes, most of it reading this.
Get the code out of Claude
New Claude: open the artifact and use its code view or download option, or ask Claude to give you the page as one HTML file. Published chat artifact: open the public link and press Copy — it copies the whole file.
<!DOCTYPE html>
<html> … </html>
// select all · copy
Paste it in, pick a link
Drop the code into the editor above, or upload the .html file. The preview renders it exactly as Claude did. Type a subdomain or let us pick one.
Publish & share
Live in seconds. Send the link to anyone — no Claude account on their end. Sign up free to keep it online, then add your domain, forms and analytics from the dashboard.
Got a React artifact? One extra sentence.
Claude’s React artifacts run inside its own sandbox and won’t work as a bare file. Before you copy anything, send Claude this prompt and host the file it gives you back. It’s the number one reason a hosted artifact shows a blank page.
Built for pages that started as a prompt
Everything below is on by default or one toggle away in the dashboard. Nothing needs a config file, a repo or a build.
Free plan: 1 project and 10 MB, which is a lot of artifacts. Custom domains and more projects are on the paid plans — see pricing.
The artifacts that end up on a real URL
Fylo next to the usual suspects
Static.app and Tiiny Host both host Claude artifacts too. Here is where they differ for a single HTML file, taken from their own pages.
| What you need | Fylo.Host | Static.app | Tiiny Host |
|---|---|---|---|
| Free plan that stays freeNot a trial | ✓ | 7-day trial, then paid | Free with limits |
| Accepts a loose .html fileNo zipping first | ✓ | ZIP required | ✓ |
| Paste code and publish, no account | ✓ | ✗ | ✗ |
| Live preview before publishing | ✓ | ✗ | ✗ |
| Host-side minify, WebP, font subsetting | ✓ | ✗ | ✗ |
| Contact forms | ✓ | ✓ | Paid |
| Custom domain with SSL | Paid plans | Paid plans | Paid plans |
| Import straight from a Claude link | ✗ | Public links only | ✗ |
Static.app and Tiiny Host details as published on their sites in September 2026. Check their pricing pages for current terms. Static.app’s link import works with the older claude.ai/public/artifacts links, not with artifacts shared from the new Claude.
Keep it in Claude when the viewer is in Claude. Host it when they aren’t.
The Claude link is fine when
- You’re sharing with teammates who already use Claude, inside the same organization.
- The artifact talks to Claude — an AI-powered chatbot, coach or generator that needs Claude’s API behind it.
- It uses connected apps or shared storage that only make sense for Claude users.
- You’re still iterating and want people to see each new version automatically.
Host it on Fylo when
- The viewer is a customer, a client, a recruiter or the public — anyone you can’t ask to sign in.
- You want it on your domain, in Google, on a business card or in an ad.
- The page needs a working form, real visitor numbers, or more than one page.
- It should keep working after the chat is gone, the subscription lapses or the artifact is unpublished.
Claude artifact hosting questions
noindex, nofollow directive, and shared artifacts are behind a login. The same HTML hosted on Fylo.Host is indexable, has a canonical URL and can sit on your own domain.index.html, put them in one folder with any images, zip the folder and upload the ZIP on the homepage. Each file becomes a page.Claude wrote it.
Give it an address anyone can visit.
Paste once. We handle the milliseconds.
Host your artifact free No signup to try. No Claude account for your visitors. Live in seconds.