Sharing a Claude artifact with a client
Claude’s own sharing is instant, already in your plan, and often all you need. It stops short of client work in four places: no password, no expiry date, no record of who opened it, and comments only from people inside your own Claude organisation. QuickHost takes the file Claude made and adds those four.
Checked 17 September 2026 against Claude artifacts’s own pricing and documentation — sources.
At a glance
How does QuickHost compare to Claude artifacts?
Claude’s sharing is one click and often enough. QuickHost adds what a client deliverable needs: a password, an expiry date, who opened it, and comments from outside your organisation.
| What you need | Claude artifacts | QuickHost |
|---|---|---|
| Publish without a repo or a build step | YesOne click from the conversation | YesDrag and drop, the qh CLI, or your agent |
| Multi-file sites — CSS, JS, images, sub-pages | NoOne page; relative links don’t resolve | YesA zip or a folder, served as uploaded |
| PDFs, spreadsheets, markdown and video, each in a viewer | NoHTML, markdown, code and diagrams only | YesPDF, markdown, CSV, JSON, images and video |
| A password on the link | No | YesOn every plan, including the $8 one |
| A separate link per recipient, revocable on its own | No | YesNamed links, each revoked on its own |
| Who opened it, per recipient | No | YesOpens, first and last seen, per person |
| An expiry date on the link | NoOrg-wide retention rules only | YesAny project, every plan |
| Comments from your client, no account needed | NoSigned-in members of your organisation only | YesPinned to a sentence, a PDF page or a video moment |
| Your AI agent can publish it and read the feedback | PartlyClaude reads comments — from your organisation | YesMCP server with 17 tools, CLI and REST API |
| Nothing of the host's on your client's page | NoShown inside Claude’s own page | YesOnly the password and expiry screens name QuickHost |
| Your own domain | No | NoNot yet — links are <name>.quickhost.ing |
| A free plan | YesFree in chat; Claude Code needs Pro | NoA 7-day trial, then from $8 a month |
Fair is fair
When is Claude artifacts the better choice?
If the person opening it is a teammate — or a password and a record of who opened it wouldn’t change anything — Claude’s link is the right answer. It’s already in your plan and it’s one click, and on Team and Enterprise your colleagues can comment while Claude replies to and resolves those comments itself.
Choose Claude artifacts if
- You’re sharing with your own team, inside your Claude organisation
- It’s a single page, and nobody needs a password
- You don’t need to know who opened it, or when
Choose QuickHost if
- It’s going to a client who shouldn’t need a Claude account
- It needs a password, a link per person, or an expiry date
- It’s more than one page — or a PDF, a spreadsheet or a video
- You want to know the moment they open it
The difference
Where does Claude artifacts fall short for client work?
Claude’s sharing was built for showing work, mostly to people who also use Claude. Four things a client deliverable needs aren’t there.
Your client may need a Claude account
Anthropic’s help centre says everyone who opens an artifact shared from Claude’s newer Share dialog needs a Claude account; artifacts published from chat stay open to anyone. Its Claude Code docs say public links need no sign-in, so open yours signed out before a client does.
No password, no expiry date
A shared artifact is open to anyone with the link or limited to your organisation. There’s no password to hand a client, and no date after which the link stops working — only org-wide retention rules on Team and Enterprise.
Nothing about who opened it
Claude doesn’t report views, let alone which person viewed it. You find out a client read the proposal when they reply — or when they don’t.
Comments stay inside your organisation
On Team and Enterprise, colleagues can comment and Claude can reply and resolve. Public links can’t take comments, so a client’s notes arrive by email and someone has to carry them back.
Pricing
How does Claude artifacts’s pricing compare?
You probably pay for Claude already, so its sharing costs nothing extra: chat artifacts publish on the Free plan, Claude Code artifacts need Pro, and sharing with comments inside an organisation comes with Team and Enterprise. QuickHost is a separate subscription on top, from $8 a month.
Claude artifacts
- Free$0
- Publish chat artifacts to a public link
- Pro$20/mo
- $17 a month billed yearly · Claude Code artifacts
- Team & EnterprisePer seat
- Share inside your organisation; colleagues can comment
QuickHost
- Starter$8/mo
- 1 member · 10 active projects
- Studio$39/mo
- 5 members, flat — then $5 each ($50 a year) · 100 active projects
- Agency$79/mo
- 15 members, flat — then $5 each ($50 a year) · 500 active projects
QuickHost prices are per workspace, not per person, and the same on every page of this site. Access is invite-only while billing is being finished; these are the plans it opens with.
Switching
How do I move from Claude artifacts to QuickHost?
There’s nothing to move. You’re adding a step for the work that goes to clients, not replacing Claude — keep making it there, and publish to QuickHost when it leaves the building.
- 1Download the artifact from Claude, or have Claude Code write it to a file.
- 2Drag it onto the QuickHost dashboard, run qh publish, or let Claude publish it directly through the QuickHost MCP server.
- 3Choose a password or a named link for each person, and an expiry date if it should stop working.
- 4When the client comments, ask Claude to read the thread over MCP, make the changes and republish to the same link.
Questions
What else do people ask about Claude artifacts and QuickHost?
The questions that come up when someone is deciding between the two, answered plainly.
Can I password-protect a Claude artifact?
Not in Claude. A shared artifact is open to anyone with the link or limited to your organisation, with no password option. To put a password on one, publish the file somewhere that supports it — QuickHost does, on every plan.
Can someone without a Claude account open my artifact?
It depends how you shared it. Artifacts published from chat open for anyone. For artifacts shared from Claude’s newer Share dialog, Anthropic’s help centre says every viewer needs a Claude account, while its Claude Code docs say public links need no sign-in. Open yours in a signed-out browser before you send it.
Can I see who viewed my Claude artifact?
No. Claude doesn’t report views. On QuickHost each person gets their own link, and you see who opened it, when they first and last did, and how many times.
Can a Claude artifact have more than one page?
Not a Claude Code artifact: it’s a single .html, .htm or .md file, and relative links to other pages or files don’t resolve. QuickHost serves a whole folder or zip exactly as it was built.
What about ChatGPT Sites?
It goes further than Claude: multi-page sites, your own domain, traffic totals, and since September invite-only access for people who sign in to OpenAI. It still has no password, no expiry date and no per-person record of who opened it. The homepage compares all three side by side.
Sources
Where do these facts come from?
Claude artifacts’s own pages, read on 17 September 2026. Prices and plans change — if anything here has gone out of date, email [email protected] and it will be corrected.