How to Share a Claude Artifact With a Client Who Doesn't Use Claude
Published
You finished a report or interactive design in Claude. Your client just needs to open it, but they don’t have a Claude account.
For a new Claude Artifact, an “Anyone with the link” Share link still requires the person opening it to sign in to Claude. If the client doesn’t use Claude, a finished HTML export hosted as a normal web page can be the better handoff. If they only need to read the work, a PDF is simpler.
There is one important exception: older chat artifacts published with Publish on eligible Claude plans can open without a Claude account. The right choice depends on which sharing option you actually have, and whether the work still needs Claude to run.
First check which Claude link you have
Claude has changed its artifact-sharing flow. The buttons may look similar, but the recipient’s experience is not the same.
| What you have | What the client needs | When it fits |
|---|---|---|
| A newer artifact with Share → Anyone with the link (Pro, Max, Team and Enterprise plans) | A Claude account to open it | The client uses Claude or needs to work with you inside the artifact |
| A legacy chat artifact with Publish (Free, Pro and Max plans) | No Claude account just to open and use ordinary features; Claude-powered features can still require sign-in | The published link already does everything your client needs |
| A public link to a shared chat | No Claude account to view the chat snapshot | You want to share a conversation, not deliver a standalone finished report |
| A self-contained HTML export hosted as a webpage | No Claude account; access depends on the host’s settings | The client needs the finished page, not the creation workspace |
These distinctions come from Anthropic’s artifact-sharing instructions and shared-chat link documentation. On Team and Enterprise plans, artifacts stay inside the organization unless an owner turns on external sharing, and even then the recipient needs a Claude account.
Test the actual link before changing tools: copy it, open a private browser window where you are not signed into Claude, and check whether you reach the work or a sign-in screen. Do not assume “Anyone with the link” means “no account required.”
Decide what the client needs to do
If they need to comment, edit, or continue work with you inside Claude, keep the artifact in Claude and use its access controls. An HTML export is a copy, not a live collaboration session.
If they need to read or print a proposal, export a PDF. A fixed report is easier to store and forward as a document. There is no reason to host an interactive page when the interactivity adds nothing.
If they need to click filters, switch tabs, or inspect an interactive chart in a finished report, consider a standalone HTML export. That gives the client a browser page without asking them to adopt Claude. But this works only when the interaction runs in an ordinary browser, without depending on Claude, a private connection, a database, or a server you haven’t deployed.
Turn a finished Claude design into an HTML link
1. Export a copy that can run outside Claude
If you built the work in Claude Design, open the finished design and use Export → Standalone HTML. Anthropic also lists PDF and ZIP among its Claude Design export options.
Do not assume every artifact is a standalone webpage. A React component, a Claude-powered tool, or a design that uses connected services may need more than an HTML download. If the standalone option isn’t available, choose an export that is supported or arrange the appropriate hosting/runtime rather than treating the preview in Claude as a portable file.
Open the exported HTML on your computer. Click the tabs, filters, and buttons that the client is supposed to use.
2. Check for files or services the export still needs
An HTML page can look fine on your computer and fail after you upload it.
Check whether images or styles reference files from your laptop, such as /Users/... or C:\Users\.... If they do, embed them in the page or put the HTML and its assets together in a ZIP. Check any charts or fonts that depend on external websites.
Our guide to sharing an HTML file walks through those checks in more detail.
3. Publish the finished file, not your Claude workspace
If you already have an HTML hosting workflow, such as GitHub Pages or Netlify, use it.
For one finished page, you can also upload the HTML to Litehost. Drop in a standalone .html file (or an eligible ZIP), then copy the page link. The no-account quick try accepts files up to 2 MB and lasts about 15 minutes; sign in and save the link before sending it as a lasting client deliverable.
For a public Litehost project, the recipient opens the rendered webpage without creating a Litehost account. A password-protected or private project follows its own access settings.
4. Open it as your client would
Before sending:
- Open the hosted link in a private window, signed out of Claude and the hosting service.
- Try the link on your phone. Check the table widths, charts, filters, and the bottom of the page.
- Confirm that every image loads and every interaction you promised still works.
- Check whether the recipient is expected to download anything, and test that path if so.
A page displaying correctly for its creator is not proof it works for its recipient.
What we tested with a Claude-made report
On October 21, 2026, we ran a manual end-to-end handoff test: create and share a Claude Artifact, export an HTML version, publish that version with Litehost, open the delivered page without a logged-in recipient session, check its mobile interactions, and replace the HTML while retaining the original recipient link.
The test was performed and confirmed manually by the Litehost founder. We did not preserve a screenshot set or instrument a comparison of loading times or conversion rates, so this is evidence for one tested workflow, not a promise about every kind of Claude Artifact.
The published example from that test was this Litehost page. Because individual links can change or become unavailable, use it as an example rather than assuming it is a permanent public demo.
A client handoff example
Consider an illustrative freelance marketer delivering acme-campaign-report.html to a small business owner. The page has a spend summary, campaign chart and filter for comparing channels. The owner reads the report on a phone and does not use Claude.
A PDF would preserve the summary, but the campaign filter would no longer work. A newer Claude Share link may ask the owner to sign in. The marketer instead exports a standalone HTML copy, checks it on a phone without a session, and sends the page URL.
Two days later, the marketer finds a mistake in one number. They correct the HTML and replace the file in the same saved Litehost project. The link in the original email continues to show the revised page. The marketer must repeat the export and replacement; the hosted copy does not synchronize itself with Claude.
That last point is the tradeoff: you gain a separate handoff page, not a second live Claude workspace.
What an HTML export will not do
A plain HTML hosting service does not automatically reproduce Claude’s own AI features, private connectors, shared storage, live collaboration, or server-side code. If your artifact depends on those, keep the native workflow or deploy a real application that provides the missing services.
Likewise, a public URL is not private access control. If the report contains client-sensitive information, check its confidentiality requirements first. Use a suitable restricted-access method rather than sending a public page and assuming the link itself is protection.
If your client already has Claude and wants to edit or comment there, Claude’s native sharing is usually the shorter route. If a PDF is all they need, send the PDF.
Before you send the final link
The useful test is not whether your Claude preview looks good. It is whether the recipient opens the right version, under the right access conditions, and can do what the report was built for.
For a finished, self-contained HTML report, create an HTML link with Litehost. For file paths, ZIP structure, and a fuller PDF-versus-HTML decision, see How to Share an HTML File So It Opens as a Page.