Interactive prototype
Comments land on the screen they are about. The fix publishes to the same link.
See live examplePublish your work-in-progress on private URLs. Share with your team and other stakeholders for commenting and iterations.
An agent publishes the Mossvane onboarding prototype to Display. The owner shares the private URL with everyone at Mossvane and adds an outside reviewer, who signs in with a one-time password. Priya, a Mossvane teammate, opens it and clicks through to step two. She selects Edit, changes the step-two headline from “Pick a look.” to “Find your look.” on the page and selects Save changes, which publishes v2. Then she comments on v2 that most creators pick a theme later. The agent adds a “Skip for now” link, publishes v3 at the same URL and resolves her comment.
Used by top teams at


Keep every prototype, presentation and pre-build review in your team's Space.
Your team comments on the doc. You or your agent updates it. The next version lands at the same URL.
Two quick steps and everyone can add expenses.
The shorter flow is clearer. Keep it at two steps.
Show the empty state. First-time users land here with nothing in the group.
Added the empty state to Expenses and published v4.
Fix any line right where you read it.
A Q3 delivery report is open on Display, with 89.7% in its On-time rate tile. Someone selects Edit in the header, changes the tile to 94.4% on the page, and selects Save changes. The report reopens as version 4 at the same URL.
Shows this step in the loop
Three common moments when product designers need the team to experience the work instead of interpreting another static handoff.
Comments land on the screen they are about. The fix publishes to the same link.
See live exampleEvery draft on one URL. Reviewers comment on the page itself, not in a thread.
See live exampleControl who can access each URL. Keep work private by default, then invite teammates and external reviewers when you are ready.
Every URL stays private until you share it with the people and groups you choose.
On Solo and higher plans, teammates continue with the Google or Microsoft account they already use.
Invite reviewers and engineers by email, and give each one a role: Viewer, Commenter, Contributor or Editor.
On Team and Business, see who opened what, and when, before you follow up.
“Before display.dev, we were sharing artifact files with each other in Slack and putting our comments there… display.dev is sort of a perfect elegant solution for us.”
Start with one project
$0
Publish your first review link free. No credit card required, and viewers stay free. Never pay for seats.
Start freeA Space for every team, with folders inside and its own permissions.
You and your agents can search every doc you can open.
Claude, ChatGPT or Cursor, on personal or company plans. One doc, one URL.
Develop applications that pull data from your sources.
Pull data from the sources your team already uses.
No. Display publishes coded HTML or Markdown rather than Figma files.
A new doc is private by default. You can share it with people and groups, open it to everyone in your company, or make it public. People sign in with Google, Microsoft or a one-time password before a private or company doc opens. Enterprise adds SAML sign-in, for example with Okta.
Teammates comment on any line of the page. People with edit access select Edit and change the doc right on the page. Your agent reads the doc and its comments, publishes the next version at the same URL, and resolves the threads it answered. Each save or publish adds a new version. On Solo and higher plans, you can open and restore earlier versions.
Yes. Invite them by email to a doc or a folder, and give them a role: Viewer, Commenter, Contributor or Editor. They sign in with a one-time password, Google or Microsoft. They do not join your organization.
Yes. Display does not check anyone's AI plan. Everyone signs in to your Display organization with their work email, whether their agent runs on Claude Pro, Max, Team or Enterprise. They all publish to and open the same docs.
Any agent that writes HTML or Markdown, for example Claude Code, Claude, ChatGPT, Codex and Cursor. Agents connect through the Display MCP server, the CLI or the API. Each person can use a different agent on the same doc.
HTML and Markdown files open as pages: reports, dashboards, specs, prototypes and slides. Folders also store other files, for example images, PDFs and data files, so people and agents find everything in one place.
Yes, for the docs that your team and your agents write: specs, plans, reports and wikis. Spaces and folders organize them, search finds them, and people comment and edit right on the page. To move existing pages, export them from Notion or Confluence as HTML or Markdown, and ask your agent to publish them.
Yes. On Solo and higher plans, every doc shows its view count. Team and Business also show who opened each doc, and when.
Yes. An Owner adds the domains of those services to the domain allowlist in Settings. Your published HTML pages can then get data from those domains and send data to them, for example from a form to a webhook. The other service must also accept the request. Display does not add a login or an API key, so keep secrets out of the page. The Business plan includes the domain allowlist.
No. We do not use customer content to train or fine-tune any AI or machine-learning model.
Display works with output from Cursor, Codex, Claude Code, or any other agent that writes HTML or Markdown. Each person can use their own agent and plan, personal or company, on the same doc.
No card required · Unlimited viewers