Solutions

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.

Free tierGoogle + Microsoft SSOInline commentsUnlimited viewers
terminal
$ display publish ./report.html
 
Uploading    47kb
Auth       Google Workspace ✓
 
✓ Published
 
→ https://view.display.dev/p/f474hfd/8f3kx9
 
Viewers    anyone at acme.com
Expires    never
Version    1
 
$ 

The command

dsp publish ./your-file.html

That'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

SourceExampleCommand
Claude CodeArchitecture diagram, competitive analysisdsp publish ./output.html
CursorReact dashboard, UI prototypedsp publish ./dist/
CodexData analysis report, tool outputdsp publish ./report.html
PlaywrightHTML test reportdsp publish ./playwright-report/
Jupyterjupyter nbconvert --to html outputdsp publish ./notebook.html
CI/CD pipelineBuild artifacts, coverage reportsSee CI guide
ManualAny .html file you createddsp publish ./file.html

If it's HTML, display.dev publishes it. It doesn't matter which tool created it.


What your teammates see

  1. They receive the URL in Slack, email, or Jira
  2. They click it
  3. 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.
  4. They authenticate with the account they already use for work
  5. They see the full interactive page

One-time authentication. No accounts to create. No app to install. No IT ticket.


Compared to the alternatives

MethodRenders HTMLCompany authPersistent URLTimeCost
Slack upload❌ (downloads)10 sec$0
Google Drive❌ (downloads)30 sec$0
GitHub Pages❌ / $2,100/mo5–30 min$0 / $2,100/mo
Vercel + SSO20+ min$320+/mo
display.dev15 sec$49/mo flat

Setup (2 minutes, once)

1. Install the CLI

npm install -g @displaydev/cli

2. Authenticate

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.com email gets access.

Done. Every future publish takes 15 seconds.


Pricing

Free — one-time password authentication, 50MB, unlimited viewers
Pro ($49/month) — Google + Microsoft SSO, 25GB, custom domain, unlimited viewers

See all pricing →


Share your first HTML file free →


Features

Authentication. 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.

Comments. Inline comments on every artifact. Your agent reads them via MCP, updates the document, resolves the thread. The artifact stays a living document, not a one-shot screenshot.

Publish in 15 seconds. dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.

Permanent URLs. Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.

Unlimited viewers. No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.

Any agent. Claude Code, Codex, and Cursor all work, along with anything else that creates HTML or Markdown output. Not locked to one provider.


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.

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).