Sharing AI Artifacts (Live HTML) Securely
Upload an .html/.htm AI artifact from Claude or GPT to a Peony data room and share it live — JavaScript runs for the viewer, under screenshot protection, NDA, permissions, and analytics.
Last updated October 24, 2026
This page covers how to share an AI-generated HTML artifact — a dashboard, calculator, financial model, or mini-app built in Claude, ChatGPT, or any tool — through a Peony data room so it runs live for the recipient while staying under a security layer. Peony renders .html and .htm natively in the in-browser viewer with JavaScript executing, so the artifact works as intended instead of being flattened into a dead PDF or a screenshot.
HTML artifacts upload on every plan, including Free. The security controls that wrap the live render are screenshot protection, NDA gates, granular permissions, and analytics.
If you have an interactive work product you built with an LLM and you need to send it to investors, buyers, lenders, or a board without losing control of who opens it, this is the workflow. For the commercial overview and use cases, see Share AI-generated documents securely.
What is an AI artifact, and does Peony render it live?
An AI artifact is a self-contained interactive file — usually a single .html file — that an LLM generates for you: a valuation dashboard, a pricing calculator, a scenario model, a one-page mini-app. It has its own HTML, CSS, and JavaScript, so it does real work in the browser rather than just displaying text.
Yes, Peony renders it live. When you upload an .html or .htm file, Peony displays it in its secure in-browser viewer with JavaScript executing, so the artifact runs exactly as it would in a normal browser — sliders move, inputs recalculate, charts redraw. It is not converted to a static image or a PDF first. This is the difference that matters: most data rooms convert HTML to a watermarked PDF before showing it, which kills interactivity and turns a working app into a flat page. Peony keeps the artifact live and wraps it in a control layer — screenshot protection, NDA gate, granular permissions, page-level analytics, and instant revoke.
For the format reference, see Supported File Formats. For the deal-side context, see how to securely share a Claude artifact.
How do I upload and share a live HTML artifact?
Export the artifact as a single .html file, upload it to a data room, layer your security on the link, and send a per-viewer link. The artifact previews live in the browser; the viewer sees the running app inside Peony's viewer rather than a screenshot.
The key is to keep the artifact self-contained. If your LLM produced one HTML file with the CSS and JavaScript inline, it will render cleanly. Save Claude or GPT output as a .html file (most tools have a download or export option, or copy the code into a file ending in .html), then follow the numbered setup below.
Numbered setup: share an AI artifact in 6 steps
-
Export the artifact as one
.htmlfile. From Claude, ChatGPT, or your editor, save the interactive output as a single file ending in.html(or.htm). Inline CSS and JavaScript render most reliably, and a self-contained file with no external links behaves best in the viewer. -
Create or open a data room. From the Data rooms list, use Create data room (or open an existing one). Creating a data room requires the Business plan or above. Name it by the deliverable and audience, for example "Project Atlas — Lender Model".
-
Upload the
.htmlfile. Drag it into the room or use the upload control. Peony detects it as HTML and previews it live in the viewer — open it once yourself to confirm JavaScript runs and the artifact behaves as expected. -
Set granular permissions. Open the Permissions tab. Each group opens a two-step wizard — step 1 Visitors (who has access), step 2 Document permissions (which files each group can open). Create a separate group and gated link per viewer or per group so each one carries its own trail.
-
Layer security on the link. Turn on the protections your audience requires — screenshot protection, NDA gate, email verification, download prevention, and link expiry. See the next section for which tier unlocks each.
-
Send the per-viewer link and watch the analytics. Share the gated link. From the Analytics tab you see who opened the artifact, for how long, and how often. Revoke any link the moment access should end.
How do I secure a shared AI artifact?
Layer Peony's controls on the link so the live artifact carries a real protection layer. Each control sits at a specific plan tier — here is exactly where.
| Control | Works on live HTML | Plan |
|---|---|---|
| Screenshot protection | Yes. This is the deterrence layer that does apply to a live HTML render: the viewer wraps the running artifact in screen-capture blocking across major browsers on macOS and Windows. Screenshield makes screen capture harder on iOS, iPadOS, and Android. | Business+, Screenshield Data Room+ |
| Dynamic watermark | No. See the warning below. | Data Room+ |
| NDA gate | Yes. See the NDA tiers below. | Business+ |
| Granular per-file permissions | Yes. Control who sees the artifact versus the rest of the room, and create one gated link per viewer so each has isolated access. | Data Room+ |
| Download prevention | Yes. The Allow downloads toggle lets you stop viewers from downloading the raw .html. On Free the toggle shows a Requires Business plan badge. | Business+ |
| Page-level analytics | Yes. The Analytics tab shows who opened the artifact, total time on it, and return visits. | All plans |
| Instant revoke | Yes. Kill any shared link and the holder loses access the next time they try to open the artifact. To revoke one viewer while everyone else keeps theirs, use granular per-viewer permissions. | One viewer only: Data Room+ |
NDA gate (Simple NDA on Business; Advanced NDA on Data Room). Require a viewer to accept an NDA before the artifact opens. Business includes a Simple NDA (view and acknowledge). Data Room adds the Advanced NDA — a digitally signed PDF sent to both parties, with countersigning, stored for counsel. See NDA Gates or the NDA feature page.
Live HTML doesn't carry the dynamic watermark
Peony's per-viewer dynamic watermark (name, email, and timestamp) is drawn over PDF, image, Office and Google document, audio/video, CSV, and TXT previews, but not over a live HTML render: the artifact runs in a sandboxed frame with no watermark overlay. For an interactive artifact, lean on screenshot protection, the NDA gate, and the access log for attribution. If you need a watermarked copy on the record, export the artifact to PDF and upload that alongside the live version. See Which files carry the watermark or the watermarks feature page.
Because screenshot protection is a deterrence layer, treat it as identity-binding on the live render, not as a physical barrier against a determined leaker. The combination — signed NDA, blocked capture, download prevention, and a complete access log — is what makes a leak traceable and a deal-grade artifact defensible.
Can I connect my own LLM and audit it?
Yes, on the Enterprise plan, scoped per use case, and the connected AI gets a row in the audit log like every other viewer: see Connect your own AI and audit it.
What if my artifact won't render?
If a .html file doesn't render as expected, it is almost always because the artifact pulls assets from external sources, or because it tries to open a link in a new tab. Self-contained files with inline CSS and JavaScript render most reliably. There is no fixed size cap on the HTML preview, but very large single files load slowly — keep the file lean and self-contained.
A common gotcha: the artifact must not open links in a new tab. Peony does not modify uploaded HTML, so a target="_blank" link (or a script that opens a new window) breaks rendering inside the sandboxed viewer. Remove target="_blank" from any anchors before uploading.
Re-export the artifact as a single file with styles and scripts inline rather than linked, confirm the extension is .html or .htm, and open it once yourself in the viewer before sending. If it still won't preview, contact support — and as a fallback, any artifact can be shared as a PDF, though that flattens the interactivity.
Common Questions
My artifact links out to individual files in the room — which URL should I put in the HTML?
Do not paste the raw file-explorer URL from your browser address bar. That URL is not a controlled, analytics-tracked link. Instead, open the Permissions tab for the item you want to link to, create a brand-new link with the control settings you want, and use that link inside your HTML. Only a purpose-created link preserves the controlled viewing experience and per-link analytics. (Also remember the artifact must not open those links in a new tab — no target="_blank".)
Do I need a paid plan just to upload an HTML artifact?
No. HTML/HTM uploads on every plan, including Free. Creating a data room to hold it requires Business and above.
Related Articles
- Share AI-generated documents securely (Solution)
- Supported File Formats (Including Live HTML & AI Artifacts)
- Dynamic Watermarks: Setup and Limits
- Screenshot Protection: What's Blocked and What Isn't
- NDA Gates: Signed Before Access
- AI Q&A: Ask Questions About Your Documents
- How to Securely Share a Claude Artifact
- Which Data Rooms Support HTML Display
- HTML Viewer (Feature)
