The fastest way to share an HTML file with your company
One command. Your HTML file becomes a permanent URL that only people with your company email can access. No git repo. No deployment pipeline. No accounts for viewers to create.
The command
dsp publish ./your-file.htmlThat's it. Viewers click the link, authenticate with their company Google or Microsoft email once, and see the full rendered page – interactive charts, animations, tabs, everything.
HTML files don't share. They download.
Drop an HTML file into Slack: recipients get a download button. They open it in a text editor and see raw markup.
Attach it to an email: blocked by most corporate security policies.
Upload to Google Drive: same result – download prompt, not a rendered page.
HTML needs to be served by a web server to render correctly. Every tool that treats it as a file to transfer fails. display.dev serves it as a page.
Works with any HTML file, from any source
| Source | Example | Command |
|---|---|---|
| Claude Code | Architecture diagram, competitive analysis | dsp publish ./output.html |
| Cursor | React dashboard, UI prototype | dsp publish ./dist/ |
| Codex | Data analysis report, tool output | dsp publish ./report.html |
| Claude Code (multi-page) | Research dossier, market map | dsp publish ./dossier/ |
| Manual | Any .html file you created | dsp publish ./file.html |
If it's HTML, display.dev publishes it. It doesn't matter which tool created it.
What your teammates see
- They receive the URL in Slack, email, or Jira
- They click it
- A login screen appears – on Pro, they click "Sign in with Google" or "Sign in with Microsoft". On Free, they enter their email and receive a one-time password.
- They authenticate with the account they already use for work
- They see the full interactive page
One-time authentication. No accounts to create. No app to install. No IT ticket.
Compared to the alternatives
| Method | Renders HTML | Company auth | Persistent URL | Time | Cost |
|---|---|---|---|---|---|
| Slack upload | ❌ (downloads) | – | ❌ | 10 sec | $0 |
| Google Drive | ❌ (downloads) | ❌ | ❌ | 30 sec | $0 |
| GitHub Pages | ✅ | ❌ / $2,100/mo | ✅ | 5–30 min | $0 / $2,100/mo |
| Vercel + SSO | ✅ | ✅ | ✅ | 20+ min | $320+/mo |
| display.dev | ✅ | ✅ | ✅ | 15 sec | $49/mo flat |
Setup (2 minutes, once)
- 1. Install the CLI
- ``
bash npm install -g @displaydev/cli`` - 2. Authenticate
- ``
bash dsp login`` - 3. Configure your company domain
- In display.dev organization settings, add your company domain (e.g.,
acme.com). Anyone authenticating with an@acme.comemail gets access. - Done
- Every future publish takes 15 seconds.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From $499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays a living document, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Claude Code, Codex, and Cursor all work, along with anything else that creates HTML or Markdown output.
Common questions.
Does this work for single-page HTML files with all CSS and JS inlined?
Yes. Self-contained HTML files – which is what most AI coding tools generate – work with zero configuration. One command, one URL.
What about HTML files that reference external CSS or JS?
If the external resources are on public CDNs (e.g., cdn.jsdelivr.net), they load fine. If they're local files in a directory, publish the whole directory: dsp publish ./output/ – display.dev serves all relative asset references correctly.
Can I share with someone outside my company?
Yes. You can add specific external email addresses to the allow-list for a given artifact, or switch the artifact to public mode for unrestricted access.
Is the URL permanent?
Yes. The URL works until you explicitly delete the artifact. It persists through team member changes, billing cycles, and plan changes.
Can I preview before sharing?
Yes. Every published artifact is visible to you immediately. Review it at the URL before sharing it with teammates.
What if I just want a URL for an HTML file – not necessarily for my team?
See /host-html-file. Same product, framed for the utility intent (public URL, allow-listed URL, or company-gated URL – your pick).
What if the HTML is a Claude or AI agent artifact?
See /share-claude-artifact. Same product with the agent-loop framing (inline comments your agent reads back via MCP).
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).