On web or Desktop, open the artifact, select Share, choose its audience and copy the link. Options depend on your plan and organization policy. Older artifacts may show Publish or Share & copy link instead. Mobile apps cannot change sharing settings.
Most artifacts using Anyone with the link open without sign-in. Docs and some dashboard content require it; invited viewers sign in with their invited email. Connected apps, Claude-powered features and stored data can behave differently for recipients. On managed accounts, ask your owner about unavailable sharing options.
Test the link as your recipient, not only as its signed-in creator. For legacy Team/Enterprise chat artifacts, Claude warns that sharing also exposes chat attachments and files. Review those before sharing. See Claude’s sharing and access documentation for the rules that apply to your artifact.
For template artifacts, open Export. Claude documents these formats; legacy artifacts have separate code, copy and download controls.
Claude artifact export formats| Creation | Export choices |
|---|
| Slides | PowerPoint, PDF or editable Google Slides |
|---|
| Docs | Word, PDF, Markdown or Google Docs |
|---|
| Designs | ZIP, PDF, PowerPoint or standalone HTML |
|---|
| Motion | MP4 video |
|---|
Source: Claude’s artifact and export documentation. Check your actual export menu rather than assuming every artifact offers HTML.
If you want to deliver the original file, use your usual file-sharing tool or htmlhost File Transfer. Check the download link’s expiry. This delivers the file; it does not convert a PowerPoint into an interactive HTML deck.
Give your HTML an independent link
- Get the actual files. Download the HTML, copy the complete code, or export the project. Leave out Markdown fences. For a folder or ZIP, keep
index.html at the root with its CSS, JavaScript and images. - Open the preview. Paste HTML above or upload the file, folder or ZIP. Confirm that you have the latest complete version, not just a patch from a follow-up message.
- Check the experience. Read it on a phone, test filters or slide controls, and check every image. An AI preview can supply dependencies that your export does not include.
- Publish deliberately. Select Publish, complete sign-in if prompted and copy the resulting HTTPS address. Open that address in a private window before sending it.
A public link can be forwarded. Review the content and access settings before publishing; password protection is a Pro feature. Follow your organization’s sharing policies when exporting work.
A signed-in Free account includes 3 site creations in total, 500 MB of site storage, and its sites never expire. Deleting a site does not restore a creation slot. Pro includes unlimited sites. Custom domains are included with Pro or available as a paid add-on on Free. Check current plans and limits before publishing a permanent site.
Example: a workshop feedback report. Switch between all sessions, morning and afternoon. The response total and rows change together. The report includes its data, font, styles and filtering script in one HTML file.
Open the working report ↗ · Download the HTML source
This is an htmlhost teaching example with fictional data, not a captured Claude export. Download it, open it locally, then try importing the same file. It has no live data connection, AI calls or external rendering dependencies. With JavaScript disabled, the full table remains readable.
Check the part a screenshot cannot prove
Choose Morning: you should see two workshop rows and 24 responses. Choose Afternoon: two rows and 18 responses. Return to All sessions: four rows and 42 responses. These checks distinguish a functioning report from a picture of one.
If your own exported report shows its charts but the filter does nothing, confirm that its script and data came with the markup. Ask for the complete project and retest. If it queries a connected private service, a static export needs a separate authorized integration or an explicitly chosen data snapshot.
Ask Claude for a portable version
Use this when your output is incomplete or depends on the original preview. Review any conversion before sharing, especially slide layouts and interactive controls.
Prepare this creation for sharing as a standalone HTML project. Keep its purpose, content and interactions: a report should stay a report, a presentation should keep its slides, and a prototype should keep its controls. Include the complete HTML, CSS, JavaScript and the assets it needs. Use relative paths for included files. Tell me which features need Claude, connected apps, private data or a backend and cannot work in a static export. Do not include credentials or private API keys. If a single HTML file can preserve everything, provide that file; otherwise provide the complete folder or ZIP with index.html at the root.
Do not replace live behavior with fabricated data to make an export appear complete. If a feature cannot travel, label the limitation or choose native sharing instead. Never put private API credentials in browser code.
Continue editing with Claude, then update the same link
For a saved htmlhost project, follow the Claude connection guide to connect through the approved directory listing. Save Draft before handing work over so Claude can read the saved version. Ask it to edit the existing project, inspect the draft, then publish the change when ready.
Connecting does not guarantee that every attachment in a Claude conversation can be transferred automatically. Confirm the files reached the project. A connector connection is also not confirmation of a successful publish.
For manual revisions, open the same project, replace or edit the relevant files, preview and select Update. Your shared address stays the same. Save Draft alone leaves the published version unchanged.
If the export looks right but does not work
- Blank page: check for incomplete HTML, JSX that needs a build, or missing scripts. Renaming source code does not compile it.
- Missing pictures or styles: include the files at the paths referenced by the HTML. A local computer path is not a public asset URL.
- Dead buttons or slide arrows: include and test the interaction code, not only the visible content.
- Missing live data or AI features: identify the service they require. HTML hosting alone does not reproduce Claude’s runtime or permissions.
- Recipients see something different: check both the actual published version and their access. Your signed-in preview is not a recipient test.
Questions about sharing Claude creations
Do I have to turn my Claude artifact into a website?
No. A report, presentation or prototype can stay exactly that. Choose a native link for viewing, an appropriate document download for editing, or HTML when you want a browser-viewable project you can host independently.
Can I upload a Claude share link to htmlhost?
Use the actual HTML or project files for this workflow. A Claude conversation or artifact URL is not the exported project. Importing a preview address is not a reliable way to recover its code, private data or dependencies.
Will renaming a React or PowerPoint file to HTML work?
No. React source needs an appropriate build or conversion to standalone HTML. A PowerPoint file needs its own viewer, or a separately created HTML version. Changing a filename does not convert its contents.
Can I update my shared HTML report at the same link?
Yes. Edit the existing htmlhost project, preview it and select Update. Your recipients keep the same address. Save Draft alone does not change the published version.
Working with another tool? See opening and sharing Gemini HTML. For a complete multi-file import walkthrough, read how to host an HTML project.