DEV Community: xhorizon

Shipping a Single-File HTML Artifact From an LLM to Stakeholders: 7 Pitfalls and How to Fix Them

xhorizon — Fri, 23 Oct 2026 06:33:49 +0000

You asked Claude, ChatGPT or Cursor for a quick internal tool: a pricing calculator, a chart over last quarter's numbers, a clickable onboarding checklist. It works on your machine. Now a product manager, a client or your finance lead needs to open it, and they are not going to clone a repo or run npx serve.

This post is the checklist I run before I send one of these files to anyone. Most of it is about making the HTML genuinely self-contained. The last part is about getting it to people as a URL instead of an attachment.

Pitfall 1: Relative asset paths that only exist on your disk

LLMs love to write <img src="chart.png"> or <link rel="stylesheet" href="styles.css"> because that is what a "real" project looks like. Once the file leaves your folder, those references point at nothing.

Run a quick grep before you ship:

grep -nE '(src|href)="(\./|\.\./|[a-zA-Z0-9_-]+\.(png|jpg|svg|css|js))' report.html

Anything it finds either needs to be inlined or replaced with an absolute HTTPS URL you control. For small images, a data URI is fine:

printf 'data:image/png;base64,%s' "$(base64 -w0 logo.png)"

For SVG icons, paste the <svg> markup inline instead. It is smaller than base64 and stays sharp on retina screens.

Pitfall 2: CSS and JS split into separate files

Same problem, different tag. Ask the model up front: "Return one HTML file. Inline all CSS in a <style> tag and all JavaScript in a <script> tag. No build step, no imports from local files." If it already split them, move the contents in by hand. One file is the unit you can actually share.

Pitfall 3: CDN scripts you didn't notice

Generated dashboards often pull Chart.js, Tailwind's Play CDN or D3 from a CDN. That is usually fine, but check three things:

Pin the version. chart.js@4.4.1, not chart.js@latest. A breaking release next month should not change a report you already sent.
Watch out for ES module imports from bare specifiers. import x from "lodash" works in a bundler and fails in a browser. Use a full URL or drop the dependency.
Know what happens offline. If a stakeholder opens it on a train, does the page fall back to a table, or is it a blank white rectangle? A <noscript> block or a plain HTML table under the chart costs a few lines.

Pitfall 4: Content Security Policy and sandboxing

Wherever you host the file, it will run under somebody's rules. Corporate wikis and some file viewers serve user HTML inside a sandboxed iframe or with a strict CSP. Then inline onclick="" handlers, eval, remote fonts or fetch() calls to your internal API quietly stop working.

Defensive habits that help everywhere:

Attach events with addEventListener in your script block, not inline attributes.
Don't fetch() live data from an internal endpoint. Bake a JSON snapshot into the file as const DATA = {...}. Your stakeholder doesn't have VPN access, and you don't want their browser hitting your API anyway.
Never paste API keys or tokens into the file. LLMs sometimes leave a placeholder key or a real one from your prompt. Search for key, token and Bearer before publishing.

Pitfall 5: It looks great on a 27-inch monitor

Most people will open your link on their phone first, usually from Slack or WhatsApp. Generated layouts often skip the basics:

<meta name="viewport" content="width=device-width, initial-scale=1">

Then check wide tables (wrap them in overflow-x: auto), fixed pixel widths on chart containers, and hover-only tooltips that do nothing on touch. Open Chrome DevTools' device mode at 375px wide before you send anything.

Pitfall 6: Emailing the .html file

This is the step where most of the previous work gets wasted. Email gateways strip or quarantine .html attachments, and phones download them instead of rendering them. That's why "it says I can't open this file" is the most common reply. The dochost guide on sharing an HTML file as a link compares the usual options side by side: single-file hosts, Netlify Drop, GitHub Pages and a few email workarounds.

My rule of thumb: if the artifact is a long-lived app with a backend, deploy it properly. If it is one self-contained file meant for a handful of readers this week, a deploy pipeline is overkill. For the second case I paste it into dochost, which takes raw HTML or Markdown and returns a link without an account. Their write-up on where to host a vibe-coded app makes the same argument in more detail.

If you'd rather skip copy-paste entirely, there's also a dochost MCP server you can add to Claude Code, Cursor or Codex. You then ask the assistant to "publish this as a link" and it returns the URL in the chat.

Pitfall 7: Size limits and the "v2" problem

Two practical things to check before you hit send.

Size. Inlined base64 images add up fast. A dashboard with four screenshots can easily pass 1 MB. Free tiers on single-file hosts usually cap page size, so read the free plan limits for whatever you use. Compress PNGs, prefer SVG for icons and charts, and drop unused fonts.

Updates. Stakeholders will find a typo ten minutes after you send the link. Re-publishing creates a second URL, and now two versions are floating around Slack. Pick a host that lets you update in place. On dochost, a page published without signing in comes with a private edit link that keeps the same share URL. Save it somewhere when you publish.

The pre-send checklist

Copy this into your notes:

[ ] One file: CSS and JS inlined, no local src/href
[ ] Images as SVG or data URIs, total size checked
[ ] CDN scripts version-pinned, with a fallback if JS fails
[ ] No inline event handlers, no live internal fetch()
[ ] No keys, tokens or internal URLs left in the source
[ ] Viewport meta tag, tested at 375px wide
[ ] Shared as a URL, not an attachment, with a way to update in place

LLMs are now very good at producing the artifact. Getting it in front of the people who asked for it, in a state they can actually use, is still on us. Ten minutes on this list saves a lot of "it doesn't open on my phone" replies.

What's your setup for sharing generated HTML? I'm curious whether people mostly use gists, internal wikis or throwaway hosts.

Give Claude Code or Cursor a publish tool over MCP, and keep the same link when it edits the page

xhorizon — Sun, 18 Oct 2026 11:47:50 +0000

Disclosure: I build dochost, the service used in the examples. The setup steps are specific to it; the four rules in the second half apply to any "publish" tool you give an agent. Checked against the live server on October 18, 2026.

Most of what an AI assistant writes for other people ends up as a file: a Markdown report, an HTML quiz, a status page. Then someone has to put it somewhere with a URL. If the assistant can call a publish tool, that step goes away. You ask for the page, the assistant sends the content, and you get a link back in the same reply.

This is a short guide to wiring that up over the Model Context Protocol (MCP). It also covers the part people skip: what happens on the second request, when you ask the agent to fix a typo on a page someone already has open.

One URL, two ways to authenticate

The server is a remote Streamable HTTP endpoint:

https://dochost.io/api/mcp

tools/list answers without auth, so you can see what you're connecting to before you sign in. Tool calls need an account, and there are two ways to give one:

You are using	Use	Why
Claude Code, Claude Desktop, ChatGPT, Cursor, VS Code, Windsurf	OAuth	The client opens a browser window and you approve once. Nothing gets pasted into a config file
A cron job, your own script, a headless agent (OpenClaw, Hermes)	API key	There's no browser to approve in, so the agent sends a bearer token

Both end up as the same account. Ownership, quota and plan limits come from the account, never from the tool arguments.

Connect it

Claude Code (one line, then run /mcp inside Claude Code and approve in the browser):

claude mcp add --transport http dochost https://dochost.io/api/mcp

Add --scope user if you want it in every project, not only the current one.

Cursor, VS Code, Windsurf, Claude Desktop config:

{
  "mcpServers": {
    "dochost": {
      "type": "http",
      "url": "https://dochost.io/api/mcp"
    }
  }
}

Claude Desktop (UI): Settings → Connectors → Add custom connector, paste the URL, Connect.

ChatGPT: Settings → Connectors (developer mode), add a connector with the same URL. Custom MCP connectors have to be available on your ChatGPT plan.

Headless agents: create a key in Settings → API keys, store it as DOCHOST_API_KEY in the agent's environment (never in a repo), and send it as Authorization: Bearer …. Rotating a key kills the old one immediately, so a leaked key is a 30-second fix.

The server supports OAuth dynamic client registration, so clients that implement the MCP auth spec don't need a pre-registered client ID.

What the agent gets

Eight tools:

publish creates a page from Markdown or HTML and returns the URL
update_page replaces a page's content in place
get_page_content reads back the current source of a page
get_page returns metadata only (title, status, views, expiry, password yes/no)
set_page_options changes visibility, search indexing or password without republishing
list_my_pages, get_account, delete_page

Pages are unlisted unless you ask for public. HTML JavaScript runs in a sandbox on a separate origin (dochost.co), so an AI-made quiz or calculator stays interactive without touching your session on the app domain.

Four rules so the agent doesn't break the link you already sent

The first publish is easy. The trouble starts on revision two. Here's what to tell your agent, or put in your project's agent instructions file.

1. Update, don't republish

If the page already exists, the agent should call update_page, not publish. A second publish creates a second URL. The person you sent the first link to keeps seeing the old version and never finds out there's a new one. update_page keeps the URL, view count and expiry, and resending identical content does nothing.

A line that works in a CLAUDE.md or .cursorrules:

When revising a page you already published, call update_page with its slug. Only call publish for a new page.

2. Read before you overwrite

update_page replaces the whole body. If the agent edits from memory (a new chat, a compacted context, or a page you tweaked by hand on the website), it silently drops whatever it can't see. So the rule is: unless the agent wrote the live content earlier in this conversation, call get_page_content first, edit that, then update.

3. Change settings without touching content

"Make it private", "add a password", "stop search engines indexing it" are settings changes, not new pages. set_page_options changes them in place. Deleting and publishing again would change the link you already shared.

4. Know the limits before you promise a link

Free links expire after 7 days (3 days for private, link-only pages). Paid plans make links permanent and add custom slugs and passwords. If a page has to outlive next week, have the agent call get_account first and tell you, rather than handing over a link that dies on Friday. There's also a rate limit (20 publishes a minute, 300 an hour), which only matters if you script it.

When this is the wrong tool

A multi-page site with a build step: use a real static host (GitHub Pages, Netlify, Cloudflare Pages) and let the agent push to a repo.
Anything that needs a backend: a form that has to store submissions needs a server. A sandboxed page can calculate in the browser, but it doesn't collect data for you.
Permanent free hosting: the free tier here expires by design.

For one document that a person needs to open today, and that you'll probably ask the agent to fix twice, a publish tool with an in-place update beats exporting a file every time.

Setup page with per-client snippets: dochost.io/mcp. The server source and stdio bridge are MIT-licensed at github.com/zyli5313/dochost-mcp.

This article was drafted with AI assistance and checked by hand against the live MCP server's tool list.

Tip Toeing in My Jordans vs IntoTheMeme: which tip-toe generator should you use?

xhorizon — Sun, 18 Oct 2026 09:31:34 +0000

Verdict in three lines

Pick Tip Toeing in My Jordans (tiptoeinginmyjordans.meme) if you need vertical 9:16, optional 2K, a 12-second clip, Full body or Face only, or you’re casting a pet / drawing.
Pick IntoTheMeme if you want the lowest per-video price, a free still preview before you spend a credit, or one credit balance that also covers other meme templates on their site.
If you only need the original imp overlaid on your own footage for free, skip both generators and use a CapCut template instead.

Disclosure: I built Tip Toeing in My Jordans. Every number below is from each site’s public pages on October 18, 2026 (Asia/Singapore). Prices and features change — confirm before you pay. Not affiliated with IntoTheMeme, Riff Raff, Nike/Jordan Brand, or the creators of the original AI clip.

Quick context

Both tools turn a clear photo into a remake of the viral tip-toe / Rumpelstiltskin barn dance (usually paired with RiFF RAFF’s “Tip Toe Wing In My Jawwdinz”). Neither is a CapCut green-screen overlay: you become the dancer (and optionally cast a second person as the watcher).

Comparison table (public pages only)

	Tip Toeing in My Jordans	IntoTheMeme (tip-toe tool)
Product URL	tiptoeinginmyjordans.meme	intothememe.com/tip-toe-in-my-jordans
Input	1 dancer photo + optional observer	1 dancer photo + optional friend
Modes	Full body or Face only	Template scene with your face (costume from template)
Clip length	12 seconds	10 seconds
Aspect ratio	9:16 or 16:9 (your choice)	16:9
Resolution	768P or 2K	720p
Free try before paying for video	Not stated on pricing / home	Yes — free preview stills (3/day on free tier; 20/day on paid packs)
One video (cheapest pack)	$8.99 (Single, 768P)	$4.99 (Starter)
Multi packs	Trio $19.99 (3×768P or 2×2K); Party $37.99 (6×768P or 4×2K)	Party Pack $14.99 / 5; Legend $34.99 / 15
Effective $/video (largest pack, tip-toe only)	~$6.33 at 768P (Party)	~$2.33 (Legend)
Sound in the download	Not guaranteed; preview and add a licensed track in-app	Silent; add the trending sound in TikTok / Reels
Subscription	No — one-time packs	No — one-time packs
Credit life	365 days	Never expire (stated on pricing)
Other memes on same credits	Tip-toe focused product	Credits work across other IntoTheMeme templates
Pets / drawings	Explicitly supported on home	Photo guide focuses on a clear adult face
Failed render	Credits returned (stated on home / FAQ)	Not verified here from a public refund policy page
Watermark	Not advertised as watermarked	“No watermark” stated for paid video

Sources (re-check before republishing):

Ours: home, pricing
IntoTheMeme: tip-toe generator, pricing
IntoTheMeme’s own 11-tool roundup (also lists us): Best Tiptoeing In My Jordans AI Generators (2026)

Rows I could not verify from a public page today are omitted (e.g. exact render minutes for us, IntoTheMeme cash-refund wording).

Where IntoTheMeme is better

I’m not hedging this for marketing. On several buyer jobs, IntoTheMeme is the rational pick:

Price. A single tip-toe video is $4.99 there vs $8.99 on my Single pack. Their bulk packs go to about $2.33/video. If you only need one casual post and 720p is fine, paying nearly half as much matters.
Try before you spend a video credit. Their free still preview lets you check likeness and composition before burning a credit. I do not currently advertise a free preview. That is a real trust advantage for first-time buyers.
One wallet, many memes. If you chase several trends in a month, IntoTheMeme credits are not locked to tip-toe. Mine are built around this dance.
Silent-on-purpose workflow. Their download is silent by design, which matches how most people post: add the official TikTok/Reels sound. My audio is “not guaranteed,” which means you should preview anyway — so their honesty is cleaner for that workflow.
Faster “is my face OK?” loop. Still previews in ~20 seconds (their claim) beats waiting on a full paid render to discover a bad selfie.

If those five points describe you, use IntoTheMeme’s tip-toe tool. Seriously.

Where Tip Toeing in My Jordans is the better pick

Choose us when the output constraints matter more than the sticker price:

Vertical 9:16. Every clip can be phone-shaped for TikTok / Reels / Shorts. IntoTheMeme’s tip-toe output is 16:9.
2K option. When the face has to survive a big crop or a TV, Trio/Party packs can spend into 2K. Their tip-toe max is 720p.
12 seconds vs 10. Slightly longer take of the dance.
Full body or Face only. Keep the original velvet costume (Face only) or bring your outfit/pet body into the scene (Full body).
Pets and drawings called out. Home page examples include dogs, cats, sponge characters — not just adult headshots.
Failed-task credit return stated on the product surface.

Make one here: tiptoeinginmyjordans.meme.

How I’d choose in 20 seconds

“Cheapest one video, check my face first.” → IntoTheMeme.
“TikTok vertical today.” → Tip Toeing in My Jordans (9:16).
“Need it sharp / 2K.” → Tip Toeing in My Jordans (Trio or Party).
“Also making other meme trends this month.” → IntoTheMeme.
“My dog is the dancer.” → Tip Toeing in My Jordans.
“Free, and the original imp is fine.” → CapCut template, not either paid AI.

Same rules no matter which tool you use

Only use photos of people (or pets) you have permission to use.
Label AI-generated content where the platform asks.
Prefer the platform’s licensed “Tip Toe Wing In My Jawwdinz” sound over whatever landed in the file.
Expect AI likeness to drift between takes.

FAQ

Is IntoTheMeme the same product as Tip Toeing in My Jordans?

No. Different sites, prices, aspect ratios, and preview models. Both remake the same viral barn dance from a photo.

Who is cheaper?

IntoTheMeme, on every public pack compared above (as of 2026-10-18).

Who supports vertical video?

Tip Toeing in My Jordans offers 9:16 or 16:9. IntoTheMeme’s tip-toe page states 16:9.

Can I try IntoTheMeme free?

They advertise free preview stills before spending a video credit. Confirm current limits on their pricing page.

Can I try Tip Toeing in My Jordans free?

A free preview is not stated on our public pricing/home pages today. Packs start at $8.99 for one 768P video.

Where should I go next?

Specs and packs: our pricing. Or open the generator: Make a tip-toe meme.

Tip toe meme generator FAQ: price, video length, 9:16 vs 16:9, 768P vs 2K, refunds

xhorizon — Sun, 18 Oct 2026 02:49:59 +0000

Tip Toeing in My Jordans (tiptoeinginmyjordans.meme) is a browser-based AI generator that turns one or two photos into a 12-second clip of the viral tip toe barn dance, in 9:16 or 16:9 and 768P or 2K. It sells one-time packs starting at $8.99, with no subscription, and a failed render returns its credits.

Disclosure: I built Tip Toeing in My Jordans. It's an independent fan tool, not affiliated with Riff Raff, the 1987 film Rumpelstiltskin, or the artists who made the original AI clip. Facts below are from the site as of October 18, 2026; check pricing before you buy.

These are the questions people ask most, in roughly the order they ask them.

How much does the tip toe meme generator cost?

Three one-time packs:

Pack	Price	768P videos	or 2K videos	Per 768P video
Single	$8.99	1	â€” (2K needs Trio or Party)	$8.99
Trio	$19.99	3	2	$6.66
Party	$37.99	6	4	$6.33

You can mix 768P and 2K from one balance on Trio and Party. Credits last 365 days. Nothing renews.

Is it free?

No. There's no free tier and no free preview; each render uses credits from a pack. If you want to see something before paying, some other tip toe generators offer free preview stills.

Do I need a subscription?

No. Packs are one-time payments.

Do I need an account?

Yes. The account holds your clips, your take history and your credit balance. You can sign in with Google or email.

How long is the video?

Every clip is 12 seconds: the shush, the grin, the tip toe across the straw, the gasp, and the slipper close-up.

That's the length of the output, not the wait. Rendering time depends on the provider queue and the quality you pick. You can leave the page while it renders and follow progress in your Library.

Should I pick 9:16 or 16:9?

9:16 (vertical) fills a phone screen. Use it for TikTok, Instagram Reels, YouTube Shorts and Snapchat.
16:9 (horizontal) keeps a wider composition. Use it for YouTube, X, Discord embeds, or playing on a TV.

The original reference clip is 16:9, so a 9:16 render is a vertical reframe. Cropping and subject placement can differ from the original; watch it once before posting.

What's the difference between 768P and 2K?

768P is the standard size for social feeds and is fine for most posts. 2K is sharper and worth it when you'll crop, zoom, or show it on a big screen. A 2K clip uses one and a half times the credits of a 768P clip, which is why the Single pack can't cover one.

What's the difference between Full body and Face only?

Full body (the default) uses the dancer photo's face, body proportions and outfit.
Face only puts the face on the original dancer and keeps the velvet tailcoat and costume.

Both keep the original dance and the pointed black shoes. Use a full-body photo for Full body; a clear front-facing face photo is enough for Face only.

Can I put two people in it?

Yes. The first photo is the dancer who tip toes. The optional second photo replaces the person sitting in the straw, so they become the one who gasps. Skip it and the original woman stays in the scene.

Does it work with pets or drawings?

Yes. Pets and drawings work as dancer or observer photos. The site's own examples include a dressed-up corgi dancing for a surprised cat.

Can I change the scene or the dance?

No. This preset uses a fixed barn scene and dance. There are no custom scene or choreography prompts. You choose the photos, the mode, quality and framing.

Does the video include the Riff Raff song?

It isn't guaranteed. The reference clip has audio, but generated sound can vary, and the tool doesn't grant music rights. Preview the finished file, then add "Tip Toe Wing In My Jawwdinz" from the licensed sound library in TikTok, Instagram or CapCut when you post.

What if a render fails? Can I get a refund?

If a task is marked failed or canceled, the credits it used come back to your balance automatically. That's a credit refund, not an automatic cash refund of the pack.

A completed clip that just doesn't look how you hoped isn't a failed task. Another take uses new credits. Earlier takes stay in your Library, so check status there before starting another paid render.

How close will it look to my photo?

Close, but not guaranteed. AI likeness and motion vary between takes. A sharp, well-lit, front-facing photo with one subject and nothing covering the face gives the best result. If a face drifts, try a clearer photo or switch modes before buying more.

Who can see my video and photos?

Your input photos stay private. Finished videos aren't listed publicly, but anyone you give the share link to can view and download that video.

Can I use a photo of someone else?

Only if you have the right to use it and the person agreed. The terms forbid making content of a real person without consent or passing an AI clip off as real footage. Label your clip as AI when you post.

Can I use the clip commercially?

The terms say you may use media generated for you, including commercially, subject to the terms and the underlying model's policies. Music rights are still your responsibility.

Is it the same as the 1987 movie or the Shrek Rumpelstiltskin?

No. The clips are new AI generations based on an online dance reference, not extracts from Rumpelstiltskin (1987). It's not the Shrek character, and the song isn't Jason Derulo's "Tip Toe." For the background, see the Rumpelstiltskin meme explainer.

How do I contact support?

Through a support ticket from your dashboard, or by email at contact@tiptoeinginmyjordans.meme.

Quick reference

Question	Answer
Price	$8.99 / $19.99 / $37.99 one-time packs
Subscription	None
Clip length	12 seconds
Framing	9:16 or 16:9
Quality	768P or 2K (2K = 1.5Ã— credits)
Photos	1 dancer + optional observer
Pets / drawings	Yes
Custom prompts	No (fixed scene and dance)
Failed render	Credits returned
Credit expiry	365 days
Sound	Not guaranteed; add licensed track in-app

Best ways to make the tip-toe Jordans meme in 2026: AI generator vs CapCut template vs editing yourself

xhorizon — Sun, 18 Oct 2026 02:49:25 +0000

There are three practical ways to make the tip toeing in my Jordans meme in 2026: a photo-to-video AI generator such as Tip Toeing in My Jordans (tiptoeinginmyjordans.meme), a CapCut template or green-screen overlay, or building it yourself in a general AI video tool or editor. If you want you (or your dog) to be the dancer with the least effort, use an AI generator; if you just want the original imp dropped into your own footage for free, a CapCut template is enough.

Disclosure: I built Tip Toeing in My Jordans, one of the tools compared below. I've tried to keep the comparison factual and to point out where other options are better. Not affiliated with Riff Raff, the 1987 film, or the creators of the original AI clip.

Quick context if you landed here first: the meme is an AI-generated clip of a Rumpelstiltskin-like imp tip toeing through a straw barn, usually set to Riff Raff's 2014 song "Tip Toe Wing In My Jawwdinz." The remake format is to swap in someone new.

What are the options for making the tip toe meme?

1. Dedicated AI generators. You upload a photo; the tool renders a new take of the barn dance with that person as the dancer. Several exist. I compare three here: Tip Toeing in My Jordans, IntoTheMeme's tip-toe tool, and rumpelstiltskin.dance.

2. CapCut templates and green screens. CapCut has user-made templates under names like "RUMPELSTILTSKIN MEME," and green-screen cut-outs of the original dancer circulate on TikTok and Facebook. Typically the original imp is layered over your footage, rather than you becoming the dancer. Template availability changes by region and app version.

3. Doing it yourself. Use a general AI video model with a reference clip and a photo, or edit by hand. Maximum control, most effort.

How do the AI generators compare?

Checked against each site's own public pages on October 18, 2026. Prices and features change often, so confirm before you pay.

	Tip Toeing in My Jordans	IntoTheMeme (tip-toe tool)	rumpelstiltskin.dance
Input	1 photo (dancer) + optional 2nd (observer)	1 photo + optional friend	1 photo
Modes	Full body or Face only	Template scene with your face	Swap into original clip, or new dance video
Clip length	12 s	10 s	~15 s (swap) / ~10 s (new dance)
Aspect ratio	9:16 or 16:9 (your choice)	16:9	16:9 (swap) / 9:16 (new dance)
Resolution	768P or 2K	720p	Not stated on homepage
Free preview	No	Yes, free preview stills	Not stated
Price	One-time packs: $8.99 / 1, $19.99 / 3, $37.99 / 6 (768P)	$4.99 / 1, $14.99 / 5, $34.99 / 15	One-time payment per video; price shown before paying
Subscription	No	No	No
Sound	Not guaranteed; preview, add licensed track in-app	Silent	Song included, plus a no-song version
Pets	Yes	Not stated; photo guide asks for one adult	Yes
Failed render	Credits returned	Not checked	Retry, then refund

Where each generator is the better pick

IntoTheMeme is cheaper per video, especially in its larger packs, and it lets you see a free preview still before spending a credit. If price and "try before you pay" matter most and 16:9 at 720p is fine, it's a sensible choice.

rumpelstiltskin.dance offers two distinct products: putting a face into the original clip, or generating a new dance. It also states that the song comes on the file, with a version without it. If you want audio baked in, that's its edge.

Tip Toeing in My Jordans is the one I built, so weigh this accordingly. Its differences are that you choose vertical or wide for every clip, you can render in 2K when the face has to stay sharp, you can cast a second person as the observer in the straw, and pets and drawings are explicitly supported. It's not the cheapest, and it doesn't offer a free preview. Pricing details are on the pricing page.

When is a CapCut template the better choice?

When you don't need to be the dancer. If the joke is "the imp shows up in my kitchen" or "the imp creeps up on my roommate," a green-screen overlay over your own video is free and fast, and you control every cut. CapCut also handles the Riff Raff sound through its own music library.

The trade-off: you're editing (import, key out the green, position, sync, export), and the face doing the dance is still the original imp. Some CapCut templates may need CapCut Pro; check before you start.

When is doing it yourself worth it?

If you already pay for a general AI video model and want a different dance, a custom scene, or full control over shots, DIY is the flexible route. Expect to source a reference clip, tune settings and re-render. Dedicated generators exist mainly so you don't have to. For example, the Tip Toeing in My Jordans preset uses a fixed scene and dance and doesn't take custom prompts.

How do I choose in 30 seconds?

"I want my face in the dance, posted to TikTok today." An AI generator with 9:16 output.
"I want to see it before paying." A generator with a free preview (IntoTheMeme offers one).
"I want the song already on the file." A generator that says it includes audio (rumpelstiltskin.dance says it does).
"I want it sharp on a big screen or I'll crop it." A generator with 2K output.
"I want two people: dancer and observer." A generator with a second photo slot (several have one).
"I want it free and don't mind the original imp." A CapCut template or green screen.
"I want a totally different scene." DIY in a general AI video tool.

What applies no matter which method you use?

Consent. Only use photos of people who agreed to it. Don't present an AI clip as real footage.
Music rights. Add "Tip Toe Wing In My Jawwdinz" from the platform's licensed sound library (TikTok, Instagram, CapCut) rather than relying on whatever audio a tool produced.
Label it as AI. Most platforms ask for an AI-generated content label. Use it.
Expect variation. Every AI take differs. Likeness, timing and small details can drift.

FAQ

What's the best tip toeing in my Jordans generator?
It depends on what you value. IntoTheMeme is cheapest with a free preview; rumpelstiltskin.dance includes the song; Tip Toeing in My Jordans (tiptoeinginmyjordans.meme) offers 9:16 or 16:9, 768P or 2K, and a two-person cast.

Is there a free way to make the tip toe meme?
A CapCut green-screen template is free, but the original imp does the dancing. Putting yourself in the dance generally means a paid AI render; some tools offer free previews first.

Which generator makes vertical 9:16 videos?
Tip Toeing in My Jordans lets you pick 9:16 or 16:9 for any clip. rumpelstiltskin.dance's new-dance option is 9:16. IntoTheMeme's tip-toe output is 16:9.

Do any of these need a subscription?
None of the three generators compared here require one; all sell one-time packs or per-video payments.

Can I use my pet?
Tip Toeing in My Jordans and rumpelstiltskin.dance both say pets work.

How to make the tip toeing in my Jordans meme with your own photo

xhorizon — Sat, 17 Oct 2026 17:43:38 +0000

Disclosure: I work on Tip Toeing in My Jordans, an independent fan tool that turns your photos into the tip-toe meme video. This article describes how that flow works as of October 2026. Pack prices and features can change — check the site before you buy. Not affiliated with Riff Raff, Jordan Brand, the 1987 Rumpelstiltskin film, or the original AI artists who made the viral barn clip.

You have seen the clip: a small Rumpelstiltskin-looking dancer tip-toes across a straw barn, shushes the observer, grins like he knows the joke, and the whole thing rides Riff Raff’s “Tip Toe Wing In My Jawwdinz.” Friends want your face in it. Group chats want the dog in the velvet coat.

Short answer: take one clear photo of the person (or pet) who should dance, open a tip-toe meme generator such as tiptoeinginmyjordans.meme, choose full-body or face-only, pick 9:16 or 16:9, and render a 12-second clip. Optional second photo puts someone in the observer role. You do not need a CapCut template link or a long prompt.

Below is the practical path — what the meme actually is, how to shoot a usable photo, the click path on the generator I use, and a short FAQ.

What people mean by “tip toeing in my Jordans”

Two things got glued together in late 2026: an AI-generated barn dance that looks like an ’80s fantasy film (Know Your Meme treats the late-August Instagram collaboration as AI, not movie footage), and Riff Raff’s 2014 track “Tip Toe Wing In My Jawwdinz” — the phonetic title behind most “tip toeing in my Jordans” searches.

The remake format is simple: put a new face or full body into that tip-toe choreography, then post vertical for TikTok / Reels / Shorts. CapCut templates still work if you already have the ID; dedicated generators skip the hunt.

Deeper timeline: Rumpelstiltskin meme explained. Song facts: Riff Raff song. Not the 1987 film: Rumpelstiltskin 1987.

What you need before you click Generate

One photo of the dancer — face visible, not tiny in the frame, no heavy sunglasses if you care about likeness. Full-body shots usually dance better when you choose full-body replacement; a tight portrait is enough for face-only.
Optional second photo — the observer (the person watching from the straw). Same rules: one clear subject.
Permission — only use photos you own or have rights to process.
Aspect ratio decision — 9:16 for TikTok / Reels / Shorts; 16:9 for YouTube, X, Discord embeds, and desktop group chats.
Quality decision — 768P is fine for most feeds; 2K when the face has to stay sharp on a big screen.

Pets and drawings are fair game on generators that say so explicitly. Likeness still varies shot to shot — that is normal for reference-to-video models.

Step-by-step on Tip Toeing in My Jordans

This is the flow on https://tiptoeinginmyjordans.meme/:

Open the generator on the homepage (or the dedicated Rumpelstiltskin AI video generator page).
Upload the dancer photo. Start with one photo if you only want the tip-toe character replaced.
Optionally add the observer photo after the dancer is set — two people in the barn instead of one.
Choose replacement mode
- Full body — uses face, body, and outfit from your photo.
- Face only — keeps the original costume/body and swaps the face. Both modes keep the tip-toe choreography and the pointed black shoes from the template.
Pick framing: 9:16 or 16:9.
Pick quality: 768P or 2K.
Start the render. Queue time varies. When it finishes, download the MP4 from your work / history area. New videos are reachable by share link; input photos stay private and finished clips are not listed in a public gallery.

Pricing (one-time packs, no subscription) — confirm on Pricing before you pay:

Pack	Price	What you get
Single	$8.99	1×768P video
Trio	$19.99	3×768P or 2×2K (mix from one balance)
Party	$37.99	6×768P or 4×2K

That works out to about $6.33 per 768P video on Party. Credits last one year. If a render fails, credits come back.

Preview the generated sound before you post, and use the licensed sound on TikTok / Reels / Shorts if your platform requires it. The generator does not grant music rights.

Photo tips that improve likeness

Face toward camera; avoid extreme side profiles for face-only mode.
Even lighting beats dramatic neon for identity.
One subject per photo — cut off third people in the background.
If the first take drifts, change the crop or try the other replacement mode before buying another pack.

Alternatives (without the drama)

You have options. CapCut / green-screen templates are free if you already know the template ID and are willing to edit. Other tip-toe sites exist under .com / .net / .org domains and on multi-tool video platforms — some are 16:9-only, some include the beat in the file, some price differently.

I use and recommend tiptoeinginmyjordans.meme because it matches how I actually post: 9:16 and 16:9, 768P or 2K, full-body or face-only, one or two photos, and one-time packs instead of a subscription. Compare those axes on any other site before you buy. This article is not a hit piece on competitors.

Posting checklist

Download the MP4.
On TikTok / Instagram Reels / YouTube Shorts, attach the official Riff Raff sound if your export audio is not the one you want public.
Caption ideas people already copy-paste from the meme: “me at 2am going for snacks,” “sneaking back in after curfew,” “my cat at 3am.”
If you need a silent loop for Discord or GIPHY, convert a trim of the MP4 to GIF in a separate editor — see Tip Toeing in My Jordans GIF.

FAQ

Is the viral barn dance from the 1987 movie?

No. It is AI-generated. The 1987 Cannon musical exists, but that tip-toe clip is not a recovered scene from it.

Can I put two people in one video?

Yes — dancer photo first, then an optional observer photo.

Is this affiliated with Riff Raff or the original AI artists?

No. Independent fan tool. Credit the meme’s origin when you explain it; buy music rights the normal platform way when you publish.

What if generation fails?

On this tool, failed tasks refund credits.

Where do I start?

https://tiptoeinginmyjordans.meme/ — upload the dancer photo and pick 9:16 if you are posting to TikTok or Reels today.

Netlify Drop, GitHub Pages, Tiiny Host: what the free tiers actually do with one HTML page (Oct 2026)

xhorizon — Thu, 15 Oct 2026 09:52:43 +0000

Disclosure: I build dochost, one of the four tools below. I've tried to state its limits as plainly as the others'. Everything was checked against each provider's own docs on Oct 15, 2026.

Ask an AI assistant "how do I put this HTML page online?" and you'll usually get Netlify Drop first, then GitHub Pages. Both are good answers, for a site. For one page you need someone to open today, the details of the free tier matter more than the brand. Here's what actually happens to your link on each.

The part that surprises people

Netlify Drop without an account is temporary. An unclaimed drop sits behind a temporary password until you claim it, and Netlify's CLI docs say anonymous deploys must be claimed within one hour or they're removed. Claim it with a free account and it stays up, with a free custom domain.
Tiiny Host's free link has no expiry date, but it has an activity rule. One project stays online as long as you log in at least once every three months. Free uploads are capped at 3 MB and show a Tiiny Host banner.
GitHub Pages on GitHub Free needs a public repo. So your source is public too. Changes can take up to 10 minutes to go live, and the terms rule out running a business/SaaS on Pages.
dochost free links expire. Public pages after 7 days, private (link-only) pages after 3 days. Permanent links are a paid feature. What you get in exchange is no account and a paste box: paste the HTML the assistant gave you, publish, send the link.

At a glance

	dochost	Netlify Drop	Tiiny Host	GitHub Pages
Signup to keep the link	Not needed (but link expires)	Yes (claim the deploy)	Yes	Yes (account + repo)
Paste HTML directly	Yes	No, drop a file/folder/zip	Yes	Commit a file
Markdown rendered	Yes	Needs a build step	Not advertised	Yes, via Jekyll
Free link lifetime	7 days public / 3 days private	Permanent once claimed	Permanent while you log in every 3 months	Permanent
Free custom domain	No (Max plan)	Yes	No (Solo plan)	Yes
JavaScript runs	Yes	Yes	Yes	Yes

Which one, for which job

Multi-file site (separate CSS, images, scripts): Netlify Drop. Drop the folder.
Portfolio or docs you'll maintain for years: GitHub Pages if you're fine with Git, otherwise a claimed Netlify Drop site.
One small page that should stay up for free with no dev tools: Tiiny Host, if the banner is OK.
One AI-generated page (a quiz, a report) someone needs to see this week: dochost. Nobody signs up, inline JS runs, and the link cleans itself up. If it needs to live longer, that's where the others win.

A practical check before using any single-file publisher: search the HTML for src=" and href=" pointing at local files. A relative path to an image you didn't upload will break on every host above except a full folder deploy.

The full comparison (pricing, password options, an FAQ) is on the original post: https://dochost.io/blog/netlify-drop-vs-github-pages-vs-tiiny-host?utm_source=devto&utm_medium=referral&utm_campaign=compare-2026-10

What's your default for "just put this one page online"? I'm curious which trade-off people hit first: the expiry, the account, or Git.

Why your HTML loses styles or images after upload: a debugging checklist

xhorizon — Tue, 13 Oct 2026 08:30:36 +0000

An HTML page can look correct on your laptop and lose its images or styling after you upload it. The first thing to check is what the browser is trying to fetch—not which host has the nicest landing page.

Disclosure: I work on dochost, one of the publishing options mentioned below. This guide was drafted with AI assistance. The examples explain browser URL resolution; they do not claim that every upload problem has the same cause.

What does a relative path mean after publishing?

Consider this HTML:

<link rel="stylesheet" href="./styles.css">
<img src="./images/chart.png" alt="Monthly totals">

Those references do not include the files. They tell the browser where to request them relative to the document's base URL. If you uploaded only report.html, its neighboring stylesheet and image may never have reached the host.

You can inspect resolution without making a network request:

new URL('./images/chart.png', 'https://example.com/reviews/report.html').href
// https://example.com/reviews/images/chart.png

new URL('/images/chart.png', 'https://example.com/reviews/report.html').href
// https://example.com/images/chart.png

The leading slash changes the location. A <base href="..."> element can also change the base used by relative links. See the MDN URL constructor reference for how relative references resolve.

Read the failed request before editing the page

Open the published link, open browser developer tools, select Network, and reload. Inspect failed requests for CSS, JavaScript, fonts, and images.

For each request, compare the requested URL with the intended asset location. A 404 suggests checking the path and whether the file was deployed. A 200 is not sufficient: inspect the response type and body. Some hosts return an HTML fallback page at a missing asset URL, which is still the wrong content for a stylesheet.

Also check filename capitalization. A reference to Chart.png can fail when the deployed file is named chart.png. Do not assume that a local filesystem and a remote host treat names identically.

Choose a single file or a complete folder

If the report is small, make it self-contained where practical. Put CSS in a <style> element and small browser scripts in a <script> element. For images, use a supported asset upload workflow, appropriate embedded image data, or stable public URLs. Weigh document size and privacy before embedding or publicly hosting an image.

dochost publishes pasted or uploaded HTML and Markdown as shareable pages. For a single HTML document, include the dependencies the page needs and test the public result. Published HTML supports JavaScript in a sandbox; that does not mean every browser API or external resource will work. Free links expire after seven days.

If the page belongs to a multi-file site, deploy the complete browser-ready folder instead. Netlify's manual deployment documentation explains uploading a prebuilt site folder. A source project with package imports may need a build first; uploading source code is not the same as deploying its generated output.

If the files load, inspect the interaction

Once CSS and images are present, a broken button is a separate diagnosis. Read the Console for JavaScript errors. Check whether the element exists when the script runs and whether its selector matches. For a form, decide whether you want a normal navigation or a client-side interaction; an unintended submission can reload the page and discard the result.

Do not label every failure as “the host blocks JavaScript.” An incorrect path, a missing file, an error in the script, or a sandbox restriction can produce different symptoms. Use a small reproduction to separate them.

Test the recipient's version

Open the link in a signed-out browser or a separate profile, then on a phone. Confirm that images and source links do not depend on your login. Try the actual buttons and check the expiry window against the review date.

Keep the original HTML and its assets separately. The repair should leave you with a reproducible document or deployment folder, not a page that happens to work only in your own browser.

How to share a ChatGPT HTML quiz with students: a preflight checklist

xhorizon — Sun, 11 Oct 2026 14:18:52 +0000

An AI assistant can give you a complete HTML quiz, but a code block in a chat is not a classroom link. Before choosing a host, check whether the output is actually a self-contained browser page.

Disclosure: I build dochost. I will use it as one single-file publishing option below, alongside folder and repository hosting. Free dochost links expire after seven days, which matters if students will return to the quiz later.

1. Ask for a browser-ready deliverable

A useful prompt is:

Make this quiz a single self-contained HTML document. Put CSS in a style element and JavaScript in a script element. Do not require npm, a development server, a backend, API keys or local files. Keep the questions and answer checking in the document. Use standard HTML form controls and show accessible feedback after submission. Return the complete HTML source.

This makes the requirements explicit; it does not prove the generated result is correct. If you need saved scores, accounts or a teacher dashboard, you are asking for an application with data handling, not just one static file.

2. Test the submit button, not just the appearance

Save the source as quiz.html and open it locally. Try an unanswered question, a wrong answer and a correct answer. Check whether the score changes and whether reset clears it.

For a form-based quiz, the JavaScript normally prevents the browser's default navigation and handles submission itself:

const form = document.querySelector('#quiz');
form.addEventListener('submit', (event) => {
  event.preventDefault();
  // Validate the answers and render feedback here.
});

This is an event-handling pattern, not a complete quiz. Ask the assistant to connect it to the actual questions and feedback elements. A page that looks finished can still have an unwired button.

3. Check what the file depends on

Search the HTML for src=, stylesheet links, fetch( and paths such as C:\\ or /Users/. A local image or a missing CSS file will not magically be included when you publish just the HTML.

For a single-file publisher, inline the assets or use public asset URLs.
For a folder host, upload the HTML and its CSS, JavaScript and images together, keeping the relative paths.
For a framework project, build the static output first, or use a host that supports its build workflow.

Public external assets can still fail because of permissions, browser rules or service outages. Test the hosted result too.

4. Pick the sharing workflow

One self-contained HTML file: dochost accepts pasted HTML or an uploaded file without an account or build setup. Its HTML JavaScript runs in a sandbox. Publish and copy the returned link. The free link lasts seven days; check the current plans if you need a permanent link.

A folder of assets: Netlify Drop is a folder-based deployment option. Manual deployment does not run a build, so provide the ready-to-serve output.

A site you will maintain in Git: GitHub Pages serves static HTML, CSS and JavaScript from repository content. It suits a versioned course site better than a one-off paste workflow.

5. Open the final link as a student

Use a separate browser session. Submit the quiz, reset it and try it on a phone. Check the expiry against the lesson date. Do not rely on your own signed-in access as evidence that students can open it.

Before sharing, remove student names, credentials and any secret API keys. Browser code can be inspected: if answers are embedded in the JavaScript, students can find them. This is suitable for practice and self-checking, not secure high-stakes assessment.

The final test is simple: can a student open the URL, answer the questions and see useful feedback during the time they need it? That is a better publishing check than whether the screenshot looks polished.

Building a citation-first game fieldguide without inventing the missing stats

xhorizon — Fri, 11 Sep 2026 15:35:34 +0000

Game databases have a data-integrity problem that looks deceptively simple: users want complete tables, while the primary sources are incomplete.

For a new or Early Access title, the tempting implementation is to copy a value from a video, a beta screenshot, or another guide and render it with the same confidence as publisher-confirmed data. That produces a tidy UI and a weak reference.

I used a stricter model while building the independent WARDOGS Fieldguide: every claim belongs to an evidence grade, and unknown is a real value rather than an empty authoring task.

type EvidenceGrade = "official" | "confirmed" | "beta-observed" | "unknown";

type Fact<T> = {
  value: T | null;
  grade: EvidenceGrade;
  sourceUrl?: string;
  observedAt?: string;
  note?: string;
};

That small distinction changes the whole publishing workflow.

An official store statement can be shown directly. A value visible in a dated beta frame can be useful, but it gets a beta label and does not silently survive into the launch build. A repeated community claim with no traceable source remains unknown. The interface renders the gap honestly instead of coercing it into a number.

The same rule applies at page level. A launch guide can say that WARDOGS supports up to 100 players, uses three teams, puts one randomized 2 × 2 km Control Zone inside a 256 km² map, and awards the match to the first team reaching 100 points. Those are sourced facts. A complete weapon-price table is not, because the official material does not publish one.

The public WARDOGS database is the resulting example. It is less “complete” than pages that guess, but it is easier to update and audit:

Store the claim with its evidence grade.
Keep the source URL and observation date beside the value.
Render unknowns explicitly.
Downgrade beta observations when the build changes.
Never promote a repeated secondary claim without finding its origin.

This pattern is useful beyond games. Any product catalog, compatibility matrix or living documentation set benefits when uncertainty is modeled instead of hidden.

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 Markdown document from ChatGPT or Claude. The recipient needs the rendered page, not a code block. The useful question is: are you sharing one self-contained file, a folder of assets, or a project that needs a build?

Disclosure: I built dochost, one of the options below. This is a workflow comparison, not an independent ranking. Updated October 11, 2026: the earlier version incorrectly said dochost disabled JavaScript. Its published HTML now runs JavaScript in a sandbox; the seven-day free-link expiry still applies.

Choose by what you actually have

What you have	A suitable starting point	Main trade-off
One HTML quiz, calculator or Markdown report	dochost	Free links expire after seven days; single-file assets need to be self-contained or publicly accessible
A folder containing HTML, CSS, JS and images	Netlify Drop	Upload the built folder; manual deployment does not run a build
A static site you want to maintain in Git	GitHub Pages	Repository and Pages setup; no server-side application runtime
Prebuilt site assets and a Cloudflare account	Cloudflare Pages Direct Upload	Account/project setup; a Direct Upload project cannot later switch to Git integration
A frontend experiment where readers should inspect the code	CodePen / JSFiddle	A code playground rather than a document-first sharing workflow

These are starting points, not exclusive capabilities. For example, a single HTML file can also live in a repository or a static-site folder.

1. Netlify Drop: upload the whole static folder

If your page references style.css, app.js and an images/ directory, keep those files together. Netlify documents a drag-and-drop deployment of the project's build/output folder. A manual deploy does not run a build command: if an AI assistant gave you a framework project, build it first and upload the output, not the unbuilt source.

For a simple site, put the entry page at index.html and retain the relative asset paths. When you change the site, upload the updated folder. Check the current account and plan requirements for keeping and managing the deployment.

Source: Netlify deployment documentation.

2. GitHub Pages: use a repository when maintenance matters

GitHub Pages publishes a static website from repository content, including HTML, CSS and JavaScript. It is a sensible choice when the source should be versioned and future edits should follow a Git workflow.

The cost is setup rather than a paste-only workflow: create or use a repository, configure Pages and make subsequent changes in that repository. Static hosting does not give your page a Node.js/Python backend or a database. A secret API key embedded in browser JavaScript remains visible to readers.

Source: What is GitHub Pages?.

3. Cloudflare Pages Direct Upload: publish prebuilt assets

Cloudflare Pages supports Direct Upload through Wrangler or dashboard drag and drop. The dashboard accepts a folder or ZIP; Wrangler accepts a folder. This works when you already have the static files and want a managed static-site project.

One decision to make early: Cloudflare says a Direct Upload project cannot later switch to Git integration. If automatic repository-based deployments are your likely next step, choose that workflow at project creation instead.

Source: Cloudflare Direct Upload documentation.

4. CodePen / JSFiddle: share an experiment and its source

A code playground is useful when the recipient is another developer who wants to inspect and modify the HTML, CSS and JavaScript. It is less natural when the deliverable is a report or lesson that should open as a finished page.

Match the environment to the generated code. A full HTML document, external libraries and a multi-file project may need adaptation to the playground's editor and dependency setup. Do not assume any code block from an AI assistant will run unchanged in every editor.

5. dochost: publish one HTML or Markdown document

Paste HTML or Markdown, or upload a .html/.md file, then publish a shareable link without creating an account or configuring a build. Markdown renders as a page; HTML JavaScript runs in a sandbox, so self-contained quizzes and calculators can remain interactive.

The important limitation is retention: free links expire after seven days. Paid plans provide permanent links and additional options. If students need the page next month, a seven-day link is not enough.

This is a single-document workflow. Inline separate CSS/JS files, or reference assets at publicly accessible URLs. Sandboxed browser JavaScript is not a backend: do not expect server code, private local files or every browser capability to work unchanged.

Start with the HTML publishing page, and check the current plans before choosing a permanent-link option.

Check the file before sharing

Open it locally and test the actual interaction: submit the quiz, calculate a result, or switch the chart.
Look for local file paths and missing assets. Folder hosts need the referenced files included; single-file publishers need inline or public assets.
Remove secrets and personal data you did not intend to publish. Browser source is accessible to recipients.
Open the final URL in a separate browser session and test again. Local success does not prove hosted success.
Check the link lifetime and access settings against how long the recipient needs it.

For a classroom quiz, the deciding factors are working interaction, student access and retention. For a maintained website, repository-based deployment may be a better fit. Pick the workflow that matches the deliverable.

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, 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; check the input formats supported by each publisher.
JavaScript — dochost runs HTML JavaScript in a sandbox, so self-contained quizzes and calculators can stay interactive. This does not supply a backend or guarantee every browser capability.
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 — check whether protection is available on your plan. An unlisted URL is not the same as a password-protected page.

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.

Updated October 11, 2026. For a more detailed comparison of file, folder and repository workflows, see five ways to publish HTML or Markdown.