HTML to URL: five ways to turn an HTML or Markdown file into a shareable link

xhorizon — Fri, 07 Aug 2026 15:10:14 +0000

You have an HTML file, or a Markdown document, and the person who needs to look at it needs the rendered page — not the code. Converting HTML to a URL should be one click, and it is. Which tool you pick still changes what you get.

If you ask ChatGPT or Claude for a full HTML page you hit this immediately: the output is stuck in a chat window as markup. Forwarding the code hands someone homework. A screenshot loses the layout on mobile. Sharing the whole conversation overshares every dead end you went down first.

Here are the five options that work without a build step, what each one costs you, and the single question that picks between them.

1. GitHub Gist

Paste the file, then view it through a renderer like htmlpreview.github.io or raw.githack.

Good: free, versioned, you already have the account.
Costs you: the raw Gist URL serves the file as plain text, so you need a third-party viewer in the chain, and the URL you send looks like it.

2. Netlify Drop

Drag the file onto the page, get a live URL. This is a real deploy.

Good: JavaScript runs. It is a genuine static site.
Costs you: anonymous drops are temporary — you need an account to keep the URL. It is also a whole site deploy to show one file.

3. CodePen / JSFiddle

Good: ideal when the page is the demo and you want people poking at the source.
Costs you: editor chrome wraps your page, and the result reads as a code sandbox rather than a document. Wrong frame if you are showing a client a pricing page.

4. Pastebin-style services

Good: instant, no account.
Costs you: most show the source, not the rendered page. That is the opposite of what you want here.

5. dochost

Disclosure: I built this one, so weigh the rest accordingly.

Paste HTML or Markdown, or upload a .html / .md file, and get a link. No account needed; free links expire after 7 days. Markdown gets a live GitHub-flavored preview before you publish, so Markdown to HTML and HTML to URL are the same two clicks.

Costs you: your JavaScript will not run. Shared pages are served from a separate cookieless domain with script-src 'none' and Set-Cookie stripped.

That last point is the whole design, so it is worth explaining rather than listing.

Why one of these deliberately breaks your JavaScript

A "paste HTML, get a URL" tool is, by default, a hosted cross-site-scripting engine. Whatever markup a stranger pastes gets served to whoever opens the link. If those pages live on the same origin as the app's own login and cookies, one pasted <script> is reading sessions.

Two ways out. Sandbox the untrusted page on a separate origin and let scripts run there, or serve it with scripts off entirely. The second is stricter and costs real functionality — interactive pages stop being interactive — but nothing an author pastes can execute in a reader's session, which matters more when the HTML was written by a model and nobody has read it line by line.

Neither answer is universally right. It is a genuine tradeoff, and it is the tradeoff you are actually choosing between in this list.

The question that decides it

Does your page need JavaScript to be worth looking at?

Yes — an interactive demo, a chart that renders client-side, a form: Netlify Drop or CodePen. Anything that strips scripts will show your reader a blank box.
No — a pricing table, an email mockup, a report, a quiz that is pure HTML and CSS: any of them work. Pick on how the URL looks and whether you want to make an account.

Most AI-generated pages people need to show someone fall in the second group. Inline <style> blocks travel with the markup, so the page arrives looking the way the model built it.

One thing to check regardless of which you pick

Ask the model to inline its CSS. If it references an external stylesheet it never gave you, the page renders unstyled wherever you put it, and you will blame the host.

What do you use for this? I am most interested in whether anyone has found a good answer for the interactive case that does not require a deploy step.

Three ways to share your ChatGPT / Claude output as a real web page

xhorizon — Sun, 14 Jun 2026 06:25:17 +0000

Your LLM just produced a great report, a README, a doc, a table. Now you want to send it to someone. Pasting raw Markdown into Slack looks broken. A screenshot isn't searchable or copyable. Forwarding the whole chat shares more than you want. So how do you turn one AI output into a clean, linkable web page?

Here are three approaches I've used, with the trade-offs.

1. GitHub Gist

Paste the Markdown into a .md Gist and share the link. Free, durable, and developers trust the domain.

Downsides: it renders in GitHub's wrapper (not a clean standalone page), HTML isn't rendered live, and it's a weird link to send a non-technical person. Good for code snippets, awkward for a polished doc.

2. Publish from a static-site setup

Drop the content into a repo with GitHub Pages, Netlify, or a notebook tool. Maximum control.

Downsides: it's a project, not a 10-second action. Overkill when you just want one page to exist at one URL.

3. A paste-to-link publisher

Tools in this category take Markdown or HTML, render it, and hand you a URL. No repo, no build. Options include Telegraph, JotBird, mdshare, and dochost (which I built, so fair disclosure). The differences worth knowing:

HTML support — some only take Markdown. If your AI produced an HTML artifact, you want one that renders HTML directly. dochost does; most don't.
Permanence — free tiers often expire links (dochost's free links last 7 days). Fine for a quick share, check the tier if you need it to live forever.
Password / private — for client work or internal docs, you want a password option.

A concrete walkthrough (paste-to-link)

Copy your Markdown or HTML out of ChatGPT/Claude.
Paste it into the publisher's box.
Get a URL. Send it.

That's the whole loop. For AI output specifically, this is the lowest-friction of the three — no repo, renders HTML, and you're sharing a normal web page instead of a screenshot or a raw blob.

Which to pick

Code snippet for other devs → Gist.
A page you'll maintain and grow → static site.
One-off doc / AI output you just need to send → a paste-to-link tool.

Pick the boring one that matches the job. For me, sharing LLM outputs landed on the third.

DEV Community: xhorizon

HTML to URL: five ways to turn an HTML or Markdown file into a shareable link

1. GitHub Gist

2. Netlify Drop

3. CodePen / JSFiddle

4. Pastebin-style services

5. dochost

Why one of these deliberately breaks your JavaScript

The question that decides it

One thing to check regardless of which you pick

Three ways to share your ChatGPT / Claude output as a real web page

1. GitHub Gist

2. Publish from a static-site setup

3. A paste-to-link publisher

Which to pick