Claude wrote me an .html page. How do I show it to my team?

Claude has been quietly excellent at emitting complete .html files for the past year. Ask it for a landing page, a one-pager pitch, a slide deck, an email template, you'll often get back a self-contained HTML document with embedded CSS and, sometimes, working interactivity. Same is increasingly true for Gemini and ChatGPT.

The output is impressive. The friction is what comes next. You have a file on your desktop, you want to show it to a colleague or get sign-off from a stakeholder, and the usual answers (Slack the file, email it, paste it somewhere) all break in subtle ways. This post is the shortest answer that works.

The bad options

Before the good option, let's name what doesn't work:

• Slack the file. Slack happily attaches it but most of your team will click it, see a download prompt, hesitate, and ignore it. Even when they do download, double-clicking the file opens their browser with a file:// URL that can't be linked to or commented on.
• Take a screenshot. Now the file isn't interactive, the text isn't selectable, comments are detached from sentences, and updates require new screenshots.
• Paste the HTML into Notion or Google Docs. The rendered output looks nothing like the original. Layout breaks, fonts substitute, embedded scripts silently don't run.
• Spin up a temporary web server. Works for one developer, doesn't work for the marketer who needs to review by Friday.

The 60-second answer

Drop the .html file onto the box below. The page renders immediately, with embedded CSS, fonts, and (in a sandbox) scripts. Click Share at the top to get a URL. Send the URL to your team. They open it in any browser, see the rendered page, and can leave inline comments by highlighting any sentence.

The page you're on right now is the tool. Drop the file from Claude directly onto this paragraph and you'll be in the editor a second from now.

Three modes for three kinds of HTML

Claude's HTML outputs aren't one thing. They're roughly three shapes, and the editor handles each one.

1. Landing pages and one-pagers

These render full-width in Edit mode. Click any heading or paragraph to tweak the copy directly. The Mobile toggle in the toolbar shows the page at a 390-pixel iPhone width, useful because Claude's first-draft HTML often breaks on mobile in non-obvious ways. Fix in Code mode if it needs CSS surgery.

2. Slide decks

If the file has multiple sections with class slide or page, Present mode automatically detects the pattern and wires up arrow-key navigation. Spacebar advances, shift-space goes back, PageDown / PageUp work too. Each viewer's current slide syncs via the cursor presence layer, so you can do live walkthroughs.

3. Email templates

Email HTML is its own beast (inline styles only, no external CSS, table-based layouts in the worst case). Render Vela Docs in Mobile mode to see how the email will look on phones (where most opens happen). Don't expect Edit mode to be useful here, email HTML is too brittle for inline-text edits. Code mode is the right tool.

How collaboration actually works

You share the link. Your colleague opens it. They see the rendered HTML in the editor. They highlight a sentence, a small floating Comment button appears, they type a comment, hit submit. The thread shows up in a right-side rail with a margin pin next to the sentence, same idiom Google Docs uses, but on rendered HTML instead of prose.

You see their cursor move as they read. You see their avatar in the top-right. If they have edit access, you see their typing in real time, character by character. Resolve a comment by clicking the green check on the thread.

Safety: is it OK to render arbitrary HTML?

Yes, with the caveat that you should trust the source. Vela Docs renders every HTML file inside a sandboxed iframe with no same-origin access. Embedded scripts can run inside that sandbox (so interactive demos work) but cannot read your other tabs, your cookies, your local files, or the parent page's auth state. The page can make outbound network requests to its own endpoints, so for very sensitive cases, treat it like opening any untrusted webpage.

For AI-generated HTML specifically, the risk is low. Claude doesn't insert phishing scripts. The bigger risk is the file accidentally calling out to a service whose availability changes (a CDN, an external font host) and silently looking different a month later. The Code mode tab is useful for spot-checking what's loaded externally.

Wait, what about .md files? ChatGPT mostly gives me those.

Same idea, different file type. The Markdown story is in a separate post . the short answer is also "drop it onto Vela Docs."

One short takeaway

Claude is great at writing complete HTML files; the bad part is that "showing them to a teammate" is a multi-step ritual by default. Drop the file onto Vela Docs, click Share, send the link. Three steps. Your colleague clicks once and reads it in their browser.