Share Claude HTML artifacts as live URLs
Share a Claude HTML artifact with a browser link. Choose native Claude sharing or export HTML for PreviewShip, then check assets, access, and link expiry.
Answer First
To share a Claude HTML artifact, use Claude’s Share controls if its access rules suit your reviewers. For an exported HTML page or static build, upload the files to PreviewShip and share the returned HTTPS project link. PreviewShip viewers do not need a Claude account; features that depend on Claude, its connectors, or its storage do not transfer with an HTML export.
From HTML to a link you can share
- Paste the complete HTML, or switch to upload a saved .html file.
- Publish, then open the HTTPS link and check the page.
- Share the link; create an account to save and update the project.
No-signup previews last 24 hours, with uploads up to 15 MiB. Claimed projects follow your plan: 3-day previews on Free, or continuous hosting with an active Pro subscription. Claiming an expired project does not republish it.
Deploy build artifacts, not source-code zips.
If you upload a zip, build the project first and zip the static output folder such as dist, build, out, or public with index.html and assets. Do not zip raw React/Vue/Next source folders with package.json and node_modules. Single .html, .md/.markdown, and .pdf files are supported directly by console upload, CLI, MCP, and the VS Code/Cursor extension.
Key takeaways
Recommended workflow
Open the artifact and decide whether to share it in Claude or export a browser-ready copy.
For PreviewShip, export standalone HTML, download an HTML artifact, or ask Claude for a complete HTML file with its required assets.
Upload the file, paste the complete HTML, or deploy the built folder with CLI or MCP. Wait for the deployment to be ready.
Open the project link in a separate browser, verify the page and interactions, then send that link to reviewers.
Comparison snapshot
Native Claude Artifact or an exported website?
Claude’s current Share flow requires viewers to sign in to Claude. A legacy artifact published from chat is an exception: people can view it without an account. The available controls depend on the artifact type, plan, and organization policy, so check the Share or Publish dialog for the artifact you have.
Choose PreviewShip when you have an export that should work as a separate static page. The hosted page does not bring along Claude conversations, connector permissions, Claude-powered features, or artifact storage.
Share a report, landing page, or design review
For example, ask Claude to produce a finished report.html with the report content and styling included. Upload that file, wait for Ready, and copy the project link. If the HTML refers to a local chart.png or styles.css, include those files in a static ZIP with index.html instead.
Check the published link at both desktop and mobile widths. Test buttons and charts, inspect missing images, and confirm that external services accept calls from the preview origin before sending it to a client.
Keep the review link useful after the first handoff
Guest publishing accepts up to 15 MiB and keeps the public preview for 24 hours. Claim it before expiry when account limits allow. Free projects have 3-day preview retention; an active Pro subscription provides continuous hosting.
Deploy later revisions to the same claimed project to keep its project URL. Public access is the default. For confidential reviews, start with an account project and configure Pro password access before publishing sensitive content.
Publish from Claude Code with CLI or MCP
If the file is already in your workspace, authenticate the PreviewShip CLI and deploy it with npx previewship deploy ./report.html --json. For a built frontend, deploy the complete output folder instead. With PreviewShip MCP configured, the agent can perform the same deployment and return its status and URL.
Claude Code also offers native Artifacts. Its current documentation specifies a self-contained page with a rendered size of at most 16 MiB and a Content Security Policy that restricts network access. Separate asset folders and ordinary backend services are not part of that native page model.
Fix a blank export or broken interaction
Confirm that the export is HTML rather than a screenshot, PDF, React source component, or a link to the Claude artifact. A framework source project needs a build; uploading package.json and src does not build it on PreviewShip.
If the exported page relies on Claude connectors, artifact storage, or Claude-powered actions, ask for a standalone version using suitable static data or your own service. Never put private API keys into the HTML. A static host cannot recreate those Claude services.
Official sources
Product and workflow facts were verified against these official pages on 2026-10-26.
FAQ
How do I share a Claude artifact with someone without a Claude account?
If it is a legacy chat artifact with Publish available, Claude supports public viewing. For other artifacts, export a browser-ready HTML copy and publish it on PreviewShip. The exported page must work without Claude-only services.
How do I download a Claude design artifact?
Open the design and use Export, then choose standalone HTML when available. Legacy artifacts have controls to view, copy, or download their content. Check the exported format before uploading: a PDF or source ZIP needs a different workflow from a complete HTML page.
Can I host Claude HTML without GitHub?
Yes. Upload the complete .html file or paste its source. If it uses local assets, upload a static ZIP containing index.html and those assets. No GitHub repository, FTP, or DNS setup is needed.
Can I turn /home/claude/repo/index.html into a URL?
That path refers to a file in an agent workspace. Deploy the file if it is self-contained, or deploy its full static output folder if it references local assets. Sending the local path alone does not let another person open it.
Will Claude-powered features keep working after export?
Do not assume so. Claude connectors, artifact storage, and Claude-powered actions are not provided by PreviewShip. Verify that the export works as an independent static page before sharing it.
Can Claude Code deploy to PreviewShip directly?
Yes. Configure PreviewShip MCP or authenticate the CLI, then have Claude Code deploy the finished HTML or built static folder. PreviewShip hosts the output; it does not build a source project or run a backend.