The best way to share AI-generated HTML
You have two kinds of options: plain static hosts (GitHub Pages, Netlify Drop, Cloudflare Pages, tiiny.host) or ilolink. The static hosts get you a link. ilolink gets you a link plus a record of what happened after you shared it.
What are you actually choosing between?
Three buckets, each with a real trade-off:
- Developer static hosts — GitHub Pages, Netlify Drop, Cloudflare Pages. Free, with full control over the output. The cost is a repo, a build, or a deploy step, plus you own the config. Good fit if you already work in that toolchain.
- Quick-drop hosts — tiiny.host and similar. Paste or drag a file, get a link in seconds. Fast, but free links can expire and free-tier size caps tend to be small, so check the current terms before you rely on one.
- ilolink — also a drop-in: paste HTML or Markdown, or drop a file, get a link. The difference is what comes after — view and scroll analytics, click and scroll heatmaps, and reader feedback on the same page, with no account.
None of these is wrong. The question is whether a link is the whole job or just the first half of it.
How do the options compare?
Cells below are honest trade-offs, not a scoreboard. Where a specific competitor number would be a guess, it says varies — go read their current pricing page.
| Static hosts | Quick drop hosts | ilolink | |
|---|---|---|---|
| Setup | Repo / build / deploy | Paste or drag a file | Paste or drop a file |
| Free link permanence | Permanent while hosted | Can expire (varies) | Permanent; expiry is opt-in |
| Analytics | None (bring your own) | Basic counts (varies) | Views, approx. uniques, scroll depth |
| Heatmaps | None | Rare (varies) | Click + scroll maps |
| Reader feedback | None | Rare (varies) | Reactions, notes, comments |
| Handles messy AI HTML safely | You review it | Varies | Sanitized under default-src 'none' |
| File cap | Large (varies) | Small on free (varies) | 15 MB per doc |
So which should you pick?
Pick a raw static host if you want a repo, full control over the build, and you don't care who read the page — you just need it online. In return for the setup, you get permanent hosting and no size cap to speak of.
Pick ilolink if you want the page live in seconds and you want to see how it landed — who opened it, how far they scrolled (bucketed at 0/25/50/75/100%), where they clicked, and what they said. The link is the same shape; you just also get the second half of the job. Every doc is served from the isolated view.ilolink.com origin under a strict CSP, so pasting AI HTML you didn't write is safe by default.
Questions
- Do ilolink links expire?
- No — links are permanent by default. Expiry is an opt-in visibility mode you can turn on per doc, alongside public, unlisted, private (teamspace members only), and password. It's a choice, not a free-tier penalty.
- Is there a free tier?
- Yes. Publishing is free for one person, up to 3 published documents. You need a free account to publish; readers never need one. Inviting teammates takes a paid plan: a one-time $9 for 5 people or $19 for 10, paid once and kept forever.
- Can it host a whole framework app?
- Not by default. Interactive JavaScript is frozen to static on ingest, so a live React or Vue app won't run — build it to a static HTML file first, then share that. But if you mark the doc trusted at publish time, it runs as-is inside a sandboxed frame on the isolated origin.
- Is pasted AI HTML safe to share?
- Yes. Untrusted HTML is sanitized on ingest — javascript:, data:, and vbscript: URLs are dropped, forms are made inert — and every doc is served from view.ilolink.com under default-src 'none'. CSS is kept so mockups still look right.
Try it on your own doc
See the difference on your own doc.