Share Claude HTML artifacts as a live preview URL
Learn how to share Claude HTML, host Claude HTML online, and turn Claude-generated artifacts into public preview URLs without GitHub or server setup.
Answer First
To share Claude HTML, save the generated artifact as a complete .html file or keep it as index.html with any referenced assets, then publish it with PreviewShip by upload, paste, CLI, MCP, VS Code, or Cursor. PreviewShip hosts the Claude HTML as a public HTTPS preview URL so teammates, clients, or stakeholders can open the page in a normal browser.
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 files are supported directly by console upload, pasted HTML, CLI, MCP, and the VS Code/Cursor extension.
Key takeaways
Recommended workflow
Ask Claude or Claude Code for a complete HTML document, not just a fragment.
Save the artifact as report.html, index.html, or another .html file. If it references local assets, keep those assets in the same static folder.
Deploy with PreviewShip upload, paste HTML, `npx previewship deploy ./report.html --json`, MCP, VS Code, or Cursor.
Share the returned preview URL and ask Claude to include it in the final handoff or review note.
How to share Claude HTML
The highest-intent workflow is simple: Claude generates a complete HTML page, you publish that artifact, and reviewers open a live URL. This avoids sending raw code or asking someone to download an attachment.
PreviewShip supports the same Claude HTML preview workflow from the browser, CLI, MCP, VS Code, and Cursor, so it works whether the artifact came from Claude chat, Claude Code, or another agent.
Host Claude HTML without GitHub
GitHub Pages is useful for repository-backed sites, but a Claude-generated one-off HTML artifact usually does not need a repo, branch, build configuration, or DNS setup.
PreviewShip keeps the job narrow: browser-ready artifact in, public preview URL out. That makes it a better fit for reports, demos, prototypes, dashboards, and review pages generated during an AI conversation.
Claude HTML preview for agent workflows
MCP lets Claude Code call a deploy tool instead of merely suggesting a command. The workflow becomes complete: generate the page, deploy the artifact, and return the link.
If Claude creates a full app instead of one HTML file, ask it to run the framework build and deploy the output folder. If it creates one .html artifact, deploy that file directly.
FAQ
How do I share Claude HTML with someone else?
Save the Claude output as a complete .html file or paste the full HTML into PreviewShip. Deploy it and send the returned public HTTPS preview URL.
Can I host Claude HTML without GitHub?
Yes. PreviewShip can host a Claude-generated HTML file directly, so you do not need GitHub Pages, a repository, FTP, DNS, or server setup for a quick preview link.
Can Claude Code deploy to PreviewShip directly?
Yes, when PreviewShip MCP is configured. Claude Code can call the deploy tool and return the preview URL.
Does this only work for Claude?
No. The same workflow applies to Cursor, Windsurf, Codex, ChatGPT-generated files, and other tools that produce static HTML.
What is /home/claude/repo/index.html?
It is commonly a local path inside an agent workspace. If that file is browser-ready HTML, deploy the file or its containing static output folder rather than sharing the local path itself.
Can I upload Claude’s source project zip directly?
Only if it is already a static output folder. For framework source projects, build first and deploy the generated dist/build/out folder.
Should I use MCP or CLI?
Use MCP when the agent should own the deploy step. Use CLI when you want a transparent terminal command or CI-friendly fallback.