You asked Claude for a prototype, a report or a deck, and it delivered. Now you need someone else to see it. There are four realistic ways to share a Claude artifact, and each suits a different situation.
1. Claude’s built-in sharing
Claude’s apps include ways to share conversations and artifacts with other people, depending on your plan and workspace settings. This is the quickest option when the recipient is happy to view the result inside Claude’s own interface.
Good for: quick, informal sharing. Trade-offs: the link and presentation are Claude’s, not yours; availability depends on your plan and organisation settings; and it isn’t designed for embedding in docs or serving data files like CSV or JSON.
2. Download the file and send it
Copy the artifact into a file (for example report.html) and send it by email or chat.
Good for: one-off handoffs to technical people. Trade-offs: recipients have to download and open files; many email and chat tools block or mangle HTML attachments; you end up with “report-final-v3.html” copies everywhere.
3. Host it yourself on a static host
Put the file in a repository or upload folder on a host like GitHub Pages, Netlify, Vercel or Cloudflare Pages.
Good for: long-lived projects that deserve version control and a custom domain. Trade-offs: every artifact means copying code, creating a project, configuring and deploying — typically 10–30 minutes. Non-HTML types (slides, Markdown, CSV, JSON) need extra work to display nicely.
4. Deploy from the conversation with ArtifactDeploy
Connect ArtifactDeploy to Claude once as a custom connector, then say “deploy this”. Claude publishes the artifact and replies with a permanent URL in about three seconds.
Good for: sharing lots of artifacts quickly with people outside Claude. Trade-offs: a one-time connector setup (about two minutes), and very large or multi-file projects are better on a traditional host.
Side-by-side comparison
| Built-in sharing | Send the file | Static host | ArtifactDeploy | |
|---|---|---|---|---|
| Time per artifact | Seconds | 1–2 min | 10–30 min | ~3 seconds |
| Recipient needs | A browser | To download & open | A browser | A browser |
| Your own URL/prefix | No | No | Yes | Yes (Pro) |
| Viewers for CSV/JSON/Markdown | Limited | No | DIY | Built in |
| Manage from Claude | Partly | No | No | List & delete tools |
Which should you use?
- Showing a colleague who also uses Claude? Built-in sharing is fine.
- Building a real product with a codebase? Use a static host with Git.
- Sharing prototypes, reports and decks with clients, managers or the public — often? Deploy from the conversation. It removes the gap between “Claude made it” and “here’s the link”.
Ready to try the last option? Follow the step-by-step deploy guide.