How to share a Claude artifact (so the link actually works)

You asked Claude to build a deck, a report, or a little interactive page. It nailed it. You hit Share, copied the link, sent it to a client.

They replied: “this asks me to log in.”

That is the artifact problem. The thing Claude made is great. The link around it is not built to leave the conversation. This post explains why the link breaks, and the three ways to get a Claude artifact in front of someone who is not you, with the tradeoffs of each.

Why the artifact link breaks

A Claude artifact is rendered inside your conversation. It is part of the chat, not a standalone page on the open web. That has three consequences the moment you try to share it:

• The link is tied to the conversation. If the chat is private, deleted, or the recipient does not have access, the artifact does not load for them. Sometimes it works, sometimes it asks for a login, sometimes it just fails. It is not designed to be a durable public URL.
• It can expose more than the deck. A shared conversation shows the conversation. The viewer can end up seeing how you got there, not just the finished artifact.
• There is no version history and no tracking. You cannot see who opened it. You cannot update it in place and keep the same link. And if you “unpublish,” that is a permanent wipe, not a pause.

None of this means artifacts are bad. For previewing your own work inside your own chat, they are perfect. The trouble starts the moment the artifact has to reach a real person.

The three ways to share a Claude artifact

1. Use Claude’s native publish

Claude can publish an artifact to a public link. It is the fastest option and it costs nothing.

Use it when: the artifact is a throwaway, the audience is casual, and you do not care who opens it or whether the link survives next week.

The limits: the link is still anchored to the artifact system, there is no per-recipient tracking, no version history, and unpublishing erases it. For anything you would send to a client, an investor, or a teammate who will reference it later, this is thin.

2. Copy the HTML out and host it yourself

If the artifact is HTML, you can copy the code and put it on a static host. This gets you a real, independent URL.

The catch is the workflow. A general host like Vercel wants a git repository and a deploy config, not a single file. A drag-and-drop host takes the file but gives you nothing else: no tracking, no versioning, no way for the agent to push an update for you. You are now maintaining a hosting setup for a deck.

Use it when: you already live in that hosting workflow and you only need a plain link.

3. Push the artifact to Slideless

Slideless takes the exact HTML Claude wrote and turns it into a permanent, public, tracked link in one command. No rebuild, no git repo, no design tool. The viewer never sees your conversation. You can re-push to update the same URL, and you get a view count per recipient.

The rest of this post walks through that flow end to end.

Step by step: Claude artifact to permanent link

Get the HTML out of Claude

If you are in claude.ai, open the artifact and copy its HTML into a file called deck.html.

If you are in Claude Code or Cursor, it is already a file. Ask the agent to write the artifact to deck.html and you are done. Better still, the Slideless skill lets the agent do the whole push for you.

Install the CLI and sign in

npm install -g slideless
slideless auth signup-request --email you@example.com

That emails you a 6-digit code. This is the part people remember: you sign up from the terminal, the agent reads the code from your inbox, and you are in. No password to invent.

slideless auth signup-complete --email you@example.com --code 123456 --first-name "Alex"

If npm install -g is blocked on your machine, every command also works as npx slideless ....

Push the deck

slideless push ./deck.html --title "My deck"

✓ Presentation pushed

  Share ID:        0192f1c3-...
  Version:         1

Mint the link

The push uploaded the deck but did not publish it yet. Mint a public viewer URL:

slideless share 0192f1c3-...

✓ Share URL minted

  Share URL:  https://app.slideless.ai/share/0192f1c3-...?token=...

Paste that into any browser. The HTML Claude wrote renders exactly as it built it, on a permanent URL, no login, no conversation attached. Send it to anyone. It works on their phone too.

Here’s that exact flow, as a live Slideless deck — embedded right here in this article. An agent wrote the HTML; one command put it on the URL inside this frame. Scroll it, or open it in its own tab.

What you get that the artifact link never had

• A permanent public URL. It does not break when the chat changes, and the viewer never touches your conversation.

• A tracked link per recipient. Mint a named token per person and see each one’s view count and last-opened time.

• Version history. Re-push to update the deck and the link stays the same:

  slideless push ./deck.html

  The URL does not change, the view count is preserved, and only the files that actually changed re-upload.

• Folder decks, not just one file. If the artifact grew into something with images, video, or 3D, push the whole folder and Slideless serves it as a full micro-site.

• It works from any agent. Claude Code, Cursor, a plain CLI, or the HTTP API. You are not tied to claude.ai.

If you want the full side-by-side, see Slideless vs Claude Artifacts.

When to just leave it as an artifact

Honest off-ramp: if the artifact is a quick preview inside your own chat and it never has to reach anyone else, leave it where it is. Native artifacts are great for that. Reach for Slideless the moment the deck has to leave the conversation and land with a real person, on a link that holds.

FAQ

Why does my Claude artifact link not work for other people? The link is bound to the conversation. It can require access to the chat or break if the chat is deleted. Slideless serves the HTML from its own permanent URL, so anyone with the link opens it, with no Claude account and no access to your conversation.

Can people see my conversation when I share through Slideless? No. Slideless hosts only the deck. The viewer never touches your chat.

Can I update the artifact after I have sent the link? Yes. Edit the HTML and run slideless push again. The URL stays the same and the view count is preserved.

Do I need to be technical to do this? You need to run a few commands. If you are working in Claude Code or Cursor, the agent runs them for you with the Slideless skill.

Get your link

Your agent already made the thing. Give it a link that does not break.

npm install -g slideless
slideless push ./deck.html
slideless share <id>

Read the quickstart · See pricing