Claude's Live Artifacts vs. ShareMyPage: What Each One Is Actually For
Claude's Live Artifacts vs. ShareMyPage: a Live Artifact keeps a page fresh with your data inside Claude, ShareMyPage sends a page to anyone, anywhere. Who each one is for, and the real downside of each.
Claude's Live Artifacts vs. ShareMyPage looks like a choice between two ways to share an HTML page. It mostly isn't. A Live Artifact in Cowork keeps a page fresh for you inside Claude. ShareMyPage puts a page in front of someone else. Treat them as the same job and you'll pick the wrong one.
I built ShareMyPage, so I'm not neutral. I tried Live Artifacts before writing this, and they're good. They solve a different problem from mine, so this is not a "which one wins" post. It's what each is for, and when I'd reach for which.
Pin a Live Artifact for a view you keep coming back to
A Live Artifact is a persistent HTML page Claude builds for you inside Cowork. What makes it "live" is that it re-queries your connected apps when you open it. Ask for a dashboard of open tasks across Linear and Asana, or a morning brief with your Slack mentions and today's calendar, and it shows today's state, not the day it was built. Every iteration is saved as a version you can compare and restore.
This is for you if:
- you want a private dashboard that refreshes itself
- the data lives in apps you've connected to Claude
- everyone who needs it is in your Claude organization and uses Claude Desktop
That's a real capability, and it's the part ShareMyPage does not do. For a private dashboard you keep returning to, a Live Artifact is the better tool.
Live Artifacts don't leave Claude, your org or your machine
That's the downside, and it comes in three parts.
- They don't leave Claude. A Live Artifact opens in the Claude Desktop app. The person on the other end needs Claude Desktop installed and needs to be in your Claude organization. There are no public or external links and no picking specific recipients. Anyone in your org with the link can open it, and nobody outside it can.
- They don't leave your org. Sharing is Team and Enterprise only, and it stays inside the organization. A client, a contractor or someone at another company is out of scope by design.
- They don't leave your machine. Live Artifacts live on your computer, and if you switch devices they don't come with you. They're desktop-only too, so there's nothing to open on the web or on a phone.
The reason underneath all three is where the work runs. When you open a Live Artifact, the fetch happens on your machine, through your connectors. That's what makes it desktop-only, and it has a consequence that's easy to miss: two people opening the same artifact don't see the same page. Each one runs on their own access, so a colleague who hasn't connected a source sees an error where you see a number. And it's only ever current while someone is looking at it.
One more thing before you lean on them. A Live Artifact uses your approved connectors without asking each time. That's what makes the refresh feel effortless, but it means a page that can change your data will do so when it opens. Think twice before you pin one that writes, not just reads.
None of this is a flaw. It's the shape of a tool built to keep a private view fresh for you and your team, inside Claude.
Use ShareMyPage when the page has to reach someone else
ShareMyPage starts where Live Artifacts stop. You take an HTML or Markdown page, from Claude, from any other tool or written by hand, and it becomes a real URL that opens in any browser, on any device, with no account and no app to install.
This is for you if:
- you're sending it to a client, a candidate, an investor or the whole internet
- the person on the other end shouldn't need Claude, or anything else
- you want to decide per page who gets in: fully public, behind a password, or limited to your workspace
None of those viewers will ever touch a connector of yours, because the page is served in isolation. (If you want the details on how I run that untrusted HTML safely, I wrote up the sandbox model here.) You still get version history.
The downside is the mirror of the Live Artifact's strength. A ShareMyPage page doesn't re-query your apps when someone opens it. Everyone you allow sees what you published, and if the underlying data changes, you republish, or have Claude re-push it over MCP. For a dashboard you want to stay current by itself, that's a chore a Live Artifact doesn't have.
| Live Artifacts (Cowork) | ShareMyPage | |
|---|---|---|
| Content | Live, re-queries your apps on open | Published snapshot, same for every viewer |
| Opens in | Claude Desktop app | Any browser, any device |
| Viewer needs | Claude Desktop, in your org | Just the link |
| Who can view | Your Claude org only | Public, password, or workspace |
| External sharing | No | Yes, anyone you grant |
| Where it lives | Your computer, doesn't sync | Cloud, on a real URL |
| Access model | Viewer's own connectors | Author controls entry |
Use them together
These two fit together. Claude can generate a page and, over our MCP integration, push it straight to ShareMyPage as a link. So the same Claude that keeps a Live Artifact fresh for you can hand you a public, access-controlled version to send outward. One for the view you live in, one for the view you ship.
The short version
- Use a Live Artifact if you want a dashboard that refreshes itself while you work inside Claude.
- Use ShareMyPage if the page has to reach someone outside your Claude org, on whatever device they're holding, with you deciding who gets in.
The tip I'd give a friend: before you build the page, ask who will open it. If the answer is only you and your team in Claude, pin it. If it's anyone else, send a link.
If you have a page to send to someone, create it on ShareMyPage and paste your HTML in.