Explainer
Claude live artifacts, explained
Anthropic’s live artifacts turn one-off outputs into persistent tools that refresh with your real data. Here’s what they are, what they’re genuinely good at — and what to do when one needs to go in front of a client.
In one paragraph
Claude live artifacts are persistent artifacts in Claude Cowork, Anthropic’s desktop workspace. Unlike a regular artifact — a static snapshot inside one chat — a live artifact is saved in its own sidebar tab and refreshes with current data from your connected apps each time you open it (as of June 2026).
The difference
Regular artifacts vs. live artifacts
| Regular artifact | Live artifact | |
|---|---|---|
| Where it lives | Inside one conversation | Its own tab in the Cowork sidebar |
| The data | Snapshot from when it was built | Refreshes from connected apps on open |
| Where it runs | Claude web, desktop & mobile | Claude Cowork (desktop app) |
| Built for | Deliverables — pages, docs, decks | Living tools — dashboards, trackers |
Feature specifics as of June 2026, per Anthropic’s published help-center documentation — check Claude’s docs for the current state.
Where they shine
What live artifacts are genuinely good at
Anything you’d otherwise rebuild every time the data moves. The artifact stays put; the numbers come to it.
Living dashboards
A metrics view that pulls fresh numbers from your connected apps each time you open it — no re-uploading, no re-prompting.
Trackers
Pipelines, projects, competitors — anything you check repeatedly and want current, not as of last Tuesday.
Recurring briefs
A standing report that reassembles itself from today’s data instead of being rebuilt by hand every week.
The gap
A live artifact is a tool for you — not a link for your client
Live artifacts live inside your Cowork workspace, attached to your connectors and your machine. As of June 2026 there’s no way to put one on your own domain, behind a password, with analytics on who viewed it. The moment the work needs to reach a client, it needs to become a page you control.
Step 1
Get the rendered HTML
Ask Claude for the page as plain HTML — the rendered state you want the client to see, with the numbers baked in.
Step 2
Publish it as a private link
Say “publish this” with the Pagelive connector, or upload the HTML. The page is noindex by default and can sit behind a password.
Step 3
Send it, then watch it
Your client opens it in any browser — no Claude account. You see opens, unique viewers, time on page, and country. When the numbers change, republish: the link stays the same.
Worth knowing
Why a stable snapshot beats a live view for client work
It feels backwards at first: the artifact refreshes itself, and the published page doesn’t. But a deliverable should show what you signed off on. A published Pagelive page is exactly that — the approved version, on a link that never changes, with version history behind it. When the data moves and you’re ready for the client to see it, republish to the same link. Pages are noindex by default and your first 10 are free — see pricing for custom domains and passwords on Pro.
Live artifacts FAQ
What are Claude live artifacts? +
Live artifacts are persistent artifacts in Claude Cowork, Anthropic’s desktop workspace. Unlike a regular artifact — a static snapshot inside one chat — a live artifact is saved in its own sidebar tab and refreshes with current data from your connected apps and files when you open it (as of June 2026, per Anthropic’s help center).
Do live artifacts work in the Claude web app? +
As of June 2026, per Anthropic’s documentation, live artifacts are a Claude Cowork feature — part of the Claude desktop app on macOS and Windows. Regular artifacts work everywhere: web, desktop, and mobile. Check Claude’s help center for the current state, as availability changes.
Can I share a live artifact with a client? +
A live artifact lives inside your Cowork workspace — it’s a tool for you, not a link for them. To put the result in front of a client, get the rendered HTML and publish it as a hosted page. A Pagelive link adds what client work needs: your own domain, an optional password, noindex by default, and viewer analytics.
Will a published copy keep refreshing like the live artifact does? +
No — a published page is a stable snapshot of the artifact at publish time. For client work that’s usually the point: they see the version you approved, not whatever the data does overnight. When you want them to see new numbers, republish — the Pagelive link never changes, and version history keeps prior versions.
Put the result in front of someone.
Private, noindex, tracked — on your own domain if you want. Free to start.