Heads up — the easy free way to put an AI-built page online usually makes it public and searchable on Google. Pagelive keeps yours private →
+ +

Claude artifacts

Claude artifacts: what they are, and everything you can do with them.

Claude artifacts are the interactive files Claude builds right in the chat — apps, documents, dashboards, and decks rendered as live HTML. This hub covers the full lifecycle: using artifacts, live artifacts, public vs. private, and publishing one as a branded, password-protected, tracked link.

Publish your artifact Add to Claude Free to start · no credit card.
+ +

In one paragraph

Claude artifacts are interactive files that Claude, Anthropic’s AI assistant, creates in a dedicated window beside your chat — web pages, small apps, documents, dashboards, and decks rendered as live HTML rather than plain text. You can iterate on an artifact in conversation, download its code, and publish it as a standalone web page anyone can open.

+ +

The guides

Every Claude artifacts guide, in one place

Start where your question is — each guide stands on its own.

What are Claude artifacts?

The plain-language definition, examples, and how artifacts differ from normal Claude responses.

Read the guide →

How to use Claude artifacts

Turn them on, create one with a prompt, iterate, download the code, and publish — step by step.

Read the guide →

Claude live artifacts

Anthropic’s persistent, data-refreshing artifacts in Cowork — what they do, and how to share one.

Read the guide →

Are Claude artifacts public?

Who can see an artifact, what the Publish button really does, and how to keep client work private.

Read the guide →

How to publish an artifact

Three routes to a live link: native Publish, the Pagelive connector, or uploading the HTML.

Read the guide →

Share without a Claude login

Send an artifact to clients and colleagues who don’t use Claude — as a clean link in any browser.

Read the guide →

Claude artifact examples

Real artifacts people build for work — proposals, calculators, dashboards — with the prompts behind them.

See the examples →

Artifacts not working?

The common reasons an artifact renders blank or broken — and the fixes, in order of likelihood.

Fix it →

Build a website with Claude

From a plain-language prompt to a live site on its own link — the full walkthrough.

Read the guide →

Claude Code

Building pages with Claude Code in the terminal — and publishing what it makes as a real link.

Read the guide →
+ +

What you can build

What you can build with artifacts

Artifacts are real, interactive HTML — not a screenshot of one. That makes them ideal for client-facing work.

Client proposals

Interactive proposals with live pricing and scope — not a flattened PDF.

Calculators & tools

ROI calculators, quote builders, and small apps that actually run in the browser.

Dashboards & reports

Charts, tables, and status views Claude assembles from your data.

Pitch decks

Web-native decks with animation and responsive layout that survive intact.

Preview an artifact in the HTML viewer →
+ +

Native sharing

How native Claude sharing works (and its limits)

Claude can publish an artifact and give you a share link, so other people can open the page without seeing your conversation. That’s great for a quick look — but it stops short of what client work needs.

  • No viewer analytics — you can’t see who opened it or for how long.
  • No branding, custom domain, or password gate.
  • A shared artifact link can be public — anyone with the URL can open it.
Claude publish vs Pagelive, side by side →
+ +

Publish with Pagelive

How to publish artifacts with Pagelive

Three ways in — pick whichever fits your workflow. The outcome is the same: a clean, branded link.

Just say “publish this” in Claude

Add Pagelive as a connector (MCP) and Claude can publish the artifact it just built — straight from the chat, no copy-paste.

Claude connector (MCP)Publish from chat

Drag-drop or paste the HTML

Already exported the artifact? Drop the HTML file into the dashboard or paste the markup. Layout and interactivity survive intact.

Drag-drop filePaste HTML

POST it from your own code

Automate it: send the artifact to Pagelive from your own scripts or pipeline with a simple REST call.

REST APIAutomate publishing
Set up the Claude connector →
+ +

Share without a login

Send clients a link that doesn’t need a Claude account

Your client opens a Pagelive link in any browser — no Claude account, no app, no sign-up. And because pages are noindex and served from an isolated content plane, your artifact won’t quietly leak onto Google.

+ +

Track & protect

Track, protect, and update published artifacts

A published artifact is a living link — watch it, lock it, and refresh it without ever resending.

Analytics

Opens, unique viewers, dwell time, country, and a by-day breakdown — so you follow up while you’re top of mind.

Password

Lock confidential artifacts behind a PBKDF2-hashed password, enforced at the edge.

Same-link updates

Edit the artifact and republish — the link never changes, and version history keeps your previous edits.

+ +

FAQ

Claude artifacts FAQ

What are Claude artifacts? +

Artifacts are the interactive files Claude builds inside a chat — web apps, documents, dashboards, and decks rendered as live HTML rather than plain text.

Can I share an artifact with someone who doesn’t use Claude? +

Yes. Publish it as a Pagelive link and it opens in any browser — your client never needs a Claude account, an app, or a login (unless you add a password).

Will my published artifact show up on Google? +

No — pages are noindex by default. We send the robots meta and X-Robots-Tag headers that tell search engines not to list it. You can opt a page into indexing if you ever want that.

Can I password-protect it? +

Yes. Passwords are PBKDF2-hashed — we can’t see them — and the gate is enforced at the edge, so only people with the link and the password can open the artifact.

+ +

Publish your artifact.

Branded, private, noindex by default. Publish your first artifact free.