Open benchmark protocol
Test ten parts of an HTML artifact handoff
A vendor-neutral protocol and blank evidence scorecard for publishing, review, recovery, automation, access, portability, setup time, and price transparency.
Open the benchmarkPractical guides
Clear, workflow-first answers for turning AI-generated HTML into a live page people can review—and an agent can revise.
Open benchmark protocol
A vendor-neutral protocol and blank evidence scorecard for publishing, review, recovery, automation, access, portability, setup time, and price transparency.
Open the benchmarkOpen research checklist
Thirteen reproducible checks for artifact access, review, versions, agent continuity, discovery, accessibility, and security—with a downloadable CSV and citation text.
Open the checklistOpen examples pack
Download source files, open revised results, and inspect the exact review prompt and change summary for five common team artifacts.
Open the examplesAI HTML hosting
Claude, ChatGPT, Codex, and Cursor can produce a polished HTML report, dashboard, or prototype in minutes. The awkward part comes next: putting it somewhere a client or teammate can open, review, and discuss. HTML Docs publishes the file as a durable browser link and adds the review layer around it.
Read the guideClaude artifact sharing
Claude often produces richer work in HTML than in a chat response: visual reports, prototypes, calculators, and complete explainers. Downloading the file solves storage, but not review. HTML Docs gives that output a stable URL, then keeps the human feedback and agent revisions connected to it.
Read the guideCodex publishing
Codex can research, design, and build a complete HTML artifact inside a workspace. HTML Docs lets the agent publish that file, hand back a browser link, and continue working after a human leaves feedback. The output becomes a living collaboration object instead of a final attachment.
Read the guideHTML preview links
A preview link is the fastest way to move an HTML file from one computer into a real review. HTML Docs goes beyond a temporary render: the page gets a durable URL, reviewers can comment on it, and later versions replace the content without replacing the conversation.
Read the guideHTML review
HTML review often gets split across a browser tab, screenshots, Slack messages, and a source-code diff. HTML Docs puts the feedback layer on the actual artifact. Reviewers keep the layout and interactions in view while comments stay connected to the content being discussed.
Read the guideCollaborative HTML
Traditional HTML is easy to render and awkward to collaborate on. HTML Docs breaks an imported page into editable regions, then adds familiar document behavior around them: comments, live collaborators, sharing controls, and versions. The result stays visually expressive without becoming an opaque file.
Read the guideHTML publishing CLI
When the artifact already exists on disk, opening a dashboard and rebuilding its context is unnecessary. The HTML Docs CLI publishes the file from the directory where you created it and returns a live URL. That makes it a natural last step for scripts, coding agents, and repeatable report workflows.
Read the guideArtifact hosting
An AI artifact is often more than a web page and less than a production application. It may be a report, plan, prototype, dashboard, or explainer that needs to be understood and approved. HTML Docs treats hosting as the entry point and collaboration as the reason the page remains useful.
Read the guideHTML hosting alternatives
Both HTML Docs and ShareHTML help turn generated HTML into a link. The meaningful choice is what happens after the first share. HTML Docs is designed for artifacts that will be commented on, edited as structured regions, versioned, and revised by a person or agent through an API.
Read the guideAI artifact alternatives
BinHTML and HTML Docs both address the gap between generated HTML and a shareable browser URL. HTML Docs leans into the next problem: helping a stakeholder review the rendered work and helping a human or agent revise the same artifact without losing context.
Read the guideStatic hosting alternatives
Netlify Drop is a convenient path from a static folder to a deployed site. HTML Docs serves a different job: turning a generated HTML deliverable into a reviewable page with comments, versions, and agent-driven updates. The right choice depends on whether infrastructure or collaboration is the center of the task.
Read the guideAI output formats
Markdown remains excellent for portable prose, source-controlled documentation, and simple structure. HTML becomes the better output when the artifact must explain through layout, charts, controls, responsive composition, or interaction. The decision should follow the reader’s job, not a trend.
Read the guidenpx @html-docs/cli installRead the CLI and API reference →Open the guided product tour to see inline comments, live collaboration, editing, and publishing before you create an account.
Try the guided tour →