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.
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.
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.
| 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 |
| Windsurf | Web app build, component library | dsp publish ./build/ |
| Playwright | HTML test report | dsp publish ./playwright-report/ |
| Jupyter | jupyter nbconvert --to html output | dsp publish ./notebook.html |
| CI/CD pipeline | Build artifacts, coverage reports | See CI guide |
| 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.
One-time authentication. No accounts to create. No app to install. No IT ticket.
| 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 |
1. Install the CLI
npm install -g @display-dev/cli
brew install display-dev/tap/display2. Authenticate
display login3. Configure your company domain
In display.dev workspace settings, add your company domain (e.g., acme.com). Anyone authenticating with an @acme.com email gets access.
Done. Every future publish takes 15 seconds.
Free — one-time password authentication, 50MB, unlimited viewers
Teams ($49/month) — Google + Microsoft SSO, 25GB, custom domain, unlimited viewers
Share your first HTML file free →
Yes. Self-contained HTML files — which is what most AI coding tools generate — work with zero configuration. One command, one URL.
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.
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.
Yes. The URL works until you explicitly delete the artifact. It persists through team member changes, billing cycles, and plan changes.
Yes. Every published artifact is visible to you immediately. Review it at the URL before sharing it with teammates.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).