Get a permanent URL for your Claude artifact
One command. Or one sentence in Claude Desktop. Your Claude artifact becomes a permanent URL you control – public, shared with specific people, or gated to your company. Inline comments work too. Your agent reads them back, fetches the current version, republishes with `short_id` and `base_version`, and resolves the thread.
From Claude to a real URL
dsp publish ./artifact.htmlOr skip the CLI entirely and paste the artifact in app.display.dev. Either way you get the same thing: a permanent URL that renders the full interactive page, not a download.
Anthropic's share link isn't a URL for your team
Claude's built-in publish gives you a claude.ai/public/artifacts/... URL. It works for a public demo. Claude Code Artifacts add a private page on claude.ai – available on Pro, Max, Team and Enterprise – but on Pro and Max it stays private to you alone, sharing is Team/Enterprise-only and only ever reaches authenticated seats inside your Claude org, the source has to be Claude, and there's no external sharing and no comments. Neither one works when:
- The artifact contains your company's data and shouldn't be on the open web
- A teammate needs to leave inline feedback the agent can act on
- The artifact will be referenced six months from now, after the chat context is gone
- The artifact is one of fifty in a project and needs a memorable URL on your own domain
- Your security team won't approve another consumer-grade share surface
display.dev opens viewing to anyone with their work login, no Claude seat, adds comments and updates from any agent, and outlives the chat window.
How it works
Via Claude Code or the CLI
dsp publish ./artifact.htmlThe CLI uploads, returns the URL, and copies it to your clipboard. To update later, fetch the artifact's current version and republish with --id <shortId> --base-version <currentVersion>.
Via Claude Desktop (MCP)
Add display.dev as an MCP server. Then ask Claude to "publish this artifact to display.dev as company-gated." One sentence, no copy-paste.
Via the dashboard
Drag the artifact into app.display.dev. Pick visibility. Get the URL.
Compared to the alternatives
| Method | Permanent URL | Company auth | Allow-list | Inline comments | Custom domain |
|---|---|---|---|---|---|
| Anthropic publish | ✅ (on claude.ai) | ❌ | ❌ | ❌ | ❌ |
| ShareMyArtifact | ✅ | ❌ | ❌ | ❌ | ❌ |
| ShareDuo | ✅ | ❌ | ❌ | ❌ | ❌ |
| OneClickLive | ✅ | ❌ | ❌ | ❌ | ❌ |
| Tiiny Host | ✅ | ❌ | ❌ | ❌ | Pro |
| display.dev | ✅ | ✅ | ✅ | ✅ (read via MCP) | ✅ |
The other tools all stop at "the link works." display.dev is the only one designed for the loop where humans leave feedback and the agent reads it back.
Comments are the part nobody else has
Every published artifact has inline comments. A PM highlights a paragraph, drops a note, hits send.
Your agent reads the thread via MCP, fetches the current version, republishes with short_id and base_version, then marks the comment resolved. The URL doesn't change. Version history is preserved.
This is the whole point. The artifact is a living document the agent maintains, not a one-shot screenshot.
Visibility levels
Public – anyone with the URL. Same shape as Anthropic's publish, but on your domain.
Allow-listed – specific email addresses. Useful for sharing with a client or a vendor without giving them company SSO.
Company-gated – anyone authenticating with a verified domain email (e.g. @acme.com) gets in. Google Workspace, Microsoft Entra ID, or email OTP.
You change the level any time. The URL stays the same.
What gets published
| Artifact | Why display.dev |
|---|---|
| Revenue dashboard from a Claude analysis | Company-gated, comments back to the agent |
| Architecture diagram for a design review | Allow-list the reviewers, collect inline feedback |
| Competitive teardown for the exec team | Off the open web, on your domain |
| Interactive prototype for a customer | Allow-list their email, no account needed |
| Daily report from a scheduled agent | Permanent URL, agent republishes with short_id and base_version |
| Internal RFC for engineering | Linked from Notion, gated to company |
If it's an artifact, it publishes. No format restrictions beyond HTML or Markdown.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
What teams say
"It's helped us delay a switch to Anthropic enterprise plans, which we probably would've been forced into so we could collaborate on Claude Design output."
– Max Wood, CEO, Indigo Engineering. Read the story →
Common questions.
Does this work with Claude Code, Claude Desktop, and the web app?
Yes. Claude Code calls dsp publish from the terminal. Claude Desktop publishes via the MCP server. The web app's artifacts work too – download the HTML, drop it in app.display.dev, get the URL.
What about Cursor, Codex, v0, and other AI tools?
Same workflow. display.dev doesn't care which tool generated the HTML. See /cursor, /codex, and /v0 for tool-specific guides.
Can my agent read comments back and update the artifact?
Yes. That's the core loop. The MCP server exposes comments, export/get, publish, and resolve tools. Your agent reads the thread, fetches the current artifact version, edits the artifact, republishes with short_id and base_version, and resolves – no human intervention needed for the maintenance pass.
Is the URL permanent across versions?
Yes. Every republish with the artifact's short_id and current base_version creates a new version on the same URL. Viewers always see the latest. Earlier versions stay accessible via the version pill on the artifact.
Can I use a custom domain instead of `*.dsp.so`?
Yes, on Pro. Bring your own domain (e.g. share.acme.com), point a CNAME, done.
What's the difference between this and `/share-html-file`?
/share-html-file is the same product framed for the "I just want to send an HTML file to my team" use case. This page is for the "my AI agent generates artifacts and they need URLs" use case. Same engine, different entry point.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).