Sharing Claude artifacts with clients: a practical guide
You can share work made in Claude through its native artifact sharing or publish the finished content through a service such as Foliyo. Choose based on what the client needs to receive: an artifact with Claude’s supported behavior, or a branded report or presentation with a separate publishing workflow.
Start with what Claude already provides
For a quick demonstration or collaboration inside Claude, native sharing can be the simplest route. Claude’s sharing options vary by artifact type, plan and organization settings. Its current documentation distinguishes newer artifacts from legacy chat artifacts, so check the instructions for the actual item you created.
Do not assume every recipient needs a paid Claude account. Anthropic documents public access without a Claude account for published legacy chat artifacts, with different rules for other sharing modes. Review the access setting in your own account and test the link as a recipient before deciding that another tool is necessary.
When does a separate branded deliverable help?
If you are a consultant or agency, the client handoff may need more than the artifact itself. You might want a strategy report in the client’s visual identity, your consultancy named as sender, a consistent address for revisions and readership information available alongside your other deliverables.
That is Foliyo’s role. Your AI tool prepares the content, and Foliyo hosts the reviewed result as a browser page or presentation. You choose the design reference, sender and access settings separately. A client’s website can inform the visual design without changing who is responsible for the work.
The useful comparison is the job each option performs. Keeping an interactive experience inside Claude may be exactly right. Publishing a finished proposal for a client who just needs to read, decide and return later is a different task. Avoid moving the work solely to remove evidence that AI helped you create it.
| Recipient’s task | Practical starting point |
|---|---|
| Try the original artifact’s interactive behavior | Keep the native artifact and test its supported sharing mode. |
| Review a finished, client-branded recommendation | Publish a separate report with clear evidence and next steps. |
| Present a concise sequence during a call | Use a 16:9 browser presentation, with detailed evidence linked. |
| Revisit revised scope at the same address | Use a publishing workflow that updates the existing deliverable. |
Separate the finished argument from the conversation
A long chat is a working record. It may include rejected ideas, unfinished numbers, private notes and instructions that make sense only to you. Before sharing, identify the final recommendation and the evidence the client needs to assess it. Remove unrelated conversation content and keep uncertainties visible.
For example, imagine a fictional Northwind website strategy. The finished page should explain the audience problem, the recommended changes, the evidence behind them and the decision required. It should not make the client scroll through every prompt you tried before settling on that recommendation.
Ask the agent to list missing sources and conflicting figures before it designs the page. A polished report with an unsupported claim is still an unsupported report. Retain approved source material so later revisions can be checked against the original facts.
Choose a format that survives the handoff
A scrolling page works well for independent reading. Fixed 16:9 slides suit a presentation you lead. Flexible slides let sections take different amounts of space while preserving a visual sequence. Tell the agent whether the recipient will read on a phone, present to colleagues or inspect detailed tables.
Foliyo publishes static HTML deliverables with supported content and controls. It does not run arbitrary JavaScript applications. If the original artifact depends on custom scripts, databases or live model calls, do not assume those features will carry across. Preserve the essential content in a supported layout and test every control that matters.
Use a brief that makes the choices explicit
Connect Foliyo through a supported MCP client or use the CLI first. Connection availability depends on your AI product and account. A working custom connection is different from a public marketplace listing; use the setup instructions rather than assuming Foliyo will appear in every directory search.
The prompt below keeps review, publication and email delivery separate. Replace the fictional client and source details. If the agent asks for missing choices, numbered answers are enough; you should not need to rewrite the whole brief.
Create a Foliyo from the approved Northwind strategy in this conversation. Keep the recommendations, sources, assumptions and next decision. Make it a scrolling page for a client reading on a phone. Use Northwind’s approved design guide and my consultancy as sender. Ask any missing questions using numbered choices. Show me the complete draft and access settings before publishing. Return the link without emailing anyone.Check the result outside your own signed-in session
Open the recipient link and complete the chosen access gate. Check the body of the report, not just the hero. Follow the source links, inspect the mobile layout and try navigation. If a chart contains the central evidence, make sure its labels are readable and its meaning is explained in text.
On Free, Foliyo pages carry Foliyo branding and include a basic read receipt. Pro removes Foliyo branding and adds detailed engagement reports and email gates. A personal link attributes activity to that link; a forwarded link does not prove who read it. Choose email verification when the access requirement calls for stronger inbox-based identification.
Common questions before sharing
Can I update the deliverable later? Yes. In Foliyo, ask the agent to find and update the existing page. Recheck the access settings and tell the client when a change affects scope, price or a decision. A stable address does not update copies someone saved separately.
Does a separate page make AI work more valuable? Presentation can make your reasoning easier to evaluate, but value still comes from the relevance, evidence and judgment in the work. Use branding to make ownership and context clear, not to conceal weak thinking.
Should I move every artifact to Foliyo? No. Keep the native artifact when its behavior or collaboration model fits the task. Use a separate deliverable when the branded handoff, controlled access and ongoing publishing workflow are useful to the client relationship.
Product guidance from Foliyo. See current plans and limits, connection instructions and our privacy policy. Send corrections or questions to hello@foliyo.io.