Can Claude publish artifacts on its own?

Yes. On Free, Pro, and Max plans Claude can publish an artifact to a public link. On Team and Enterprise plans you can also restrict it to your organization. But those published pages have no password, no inline comments, no version history, and you can't republish after unpublishing.

What does Repage add that Claude's built-in publishing doesn't have?

Password protection, inline comments, full version history with revert, and a stable link you can republish. Claude's published links are public-only and permanent — once you unpublish you can't reuse the same artifact link.

Do viewers need a Claude account to see a Repage-hosted artifact?

No. A Repage page is standard HTML served at a URL — anyone with the link (and password, if set) can open it without a Claude subscription.

If I already use Claude's built-in publish, why switch?

You don't have to switch entirely — use Claude's publish for quick public demos, and Repage when you want your documents organized into projects, passwords for sensitive pages, inline review, revision history, or files you can export and keep.

Can I get my files back out of Repage?

Always. Every document downloads as its original Markdown or HTML source in one click, any project exports as a .zip of plain files that works as an Obsidian vault, and one link downloads everything you own. A published Claude artifact lives inside Claude — there's no export of your published library.

Which Claude plans can use Claude's artifact publishing?

Publishing to a public link is available on Free, Pro, and Max. Restricting to your organization is a Team and Enterprise feature. Repage accepts the artifact's HTML regardless of which Claude plan you're on.

Claude Artifact Publishing vs Repage — Comparison

Side by side

Capability	Repage	Claude publish
Download the source file (.md / .html)	Yes — one click	No
Export projects as plain files (Obsidian-ready)	Yes — .zip	No
Organized library (projects & folders)	Yes	No — lives in chats
Password-protect the link	Yes	No
Inline comments from reviewers	Yes	No
Version history & revert	Yes	No
Re-publish after unpublishing	Yes	No — permanent
Viewer needs a Claude account	No	No (public) / Yes (org)
Publish via MCP from Claude	Yes	Built-in
Price	Free	Free

What Claude's built-in publishing is good for

Claude's publish is the fastest way to put an artifact on a public link — one click, no extra accounts, shareable immediately. It's ideal for a quick demo to a wide audience where you don't need feedback, passwords, or history.

When to host on Repage instead

Your files stay yours. A published artifact lives inside Claude; on Repage every document downloads as its original Markdown or HTML, whole projects export as a .zip of plain files you can drop into an Obsidian vault, and one click exports your entire library — self-host it anywhere.
An organized library, not a chat history. Repage files documents under projects with their own pages — you can actually find last month's plan without scrolling a conversation.
Sensitive artifacts. Claude's published links are always public. Repage lets you gate an artifact behind a password so only invited reviewers can open it.
Review cycles. Teammates can leave inline comments on a Repage page — there's no review layer in Claude's publishing.
Iterating on the same artifact. Publish a revised version to Repage and the link stays the same; Repage keeps every revision so you can compare or roll back. Claude has no version history for published artifacts.
Long-lived pages. If you unpublish a Claude artifact you can't republish it — the link is gone permanently. A Repage link is stable; take it down and bring it back whenever you want.
Viewer independence. A Repage page is plain HTML served at a URL — viewers don't need any Claude plan to open it, and it doesn't count against anyone's Claude usage.

How to move a Claude artifact to Repage

Paste the HTML

Copy the artifact's HTML from Claude, paste it into Repage, and get a link instantly — best for one-off shares where you want Repage's features without connecting tools.

Publish via MCP

Connect the Repage MCP server to Claude and ask Claude to publish the artifact. Claude returns the hosted link directly — no copying, and revised versions become new Repage versions automatically.

Host your next Claude artifact on Repage

Publish HTML from any AI assistant, collect comments, keep every version.

Publish a document

Frequently asked questions

Can Claude publish artifacts on its own?: Yes. On Free, Pro, and Max plans Claude can publish an artifact to a public link. On Team and Enterprise plans you can also restrict it to your organization. But those published pages have no password, no inline comments, no version history, and you can't republish after unpublishing.
What does Repage add that Claude's built-in publishing doesn't have?: Password protection, inline comments, full version history with revert, and a stable link you can republish. Claude's published links are public-only and permanent — once you unpublish you can't reuse the same artifact link.
Do viewers need a Claude account to see a Repage-hosted artifact?: No. A Repage page is standard HTML served at a URL — anyone with the link (and password, if set) can open it without a Claude subscription.
If I already use Claude's built-in publish, why switch?: You don't have to switch entirely — use Claude's publish for quick public demos, and Repage when you want your documents organized into projects, passwords for sensitive pages, inline review, revision history, or files you can export and keep.
Can I get my files back out of Repage?: Always. Every document downloads as its original Markdown or HTML source in one click, any project exports as a .zip of plain files that works as an Obsidian vault, and one link downloads everything you own. A published Claude artifact lives inside Claude — there's no export of your published library.
Which Claude plans can use Claude's artifact publishing?: Publishing to a public link is available on Free, Pro, and Max. Restricting to your organization is a Team and Enterprise feature. Repage accepts the artifact's HTML regardless of which Claude plan you're on.

Claude artifact publishing vs Repage