Lifetime launch - 23 of 100 spots at $99 · $149Claim your spot

HTML hosting

Host one HTML fileas a live link

Drop a single HTML file here and get one clean link that renders it live in the browser, no server, no DNS, no build step.

Drop your file here

Drop several at once and they become one album link

Files up to 100 MB free

Free: 20 links, up to 100 MB · Pro: unlimited links, bigger uploads

1

Drag in your site files

From your desktop or phone, any file works

1 / 4
creating your link…

index.html

42 KB

Drop to upload

12 files · 1.4 MBSSL included
Opened·first view 2 min after sending

By the numbers

1,800+

people sharing files

3,400+

links shared

13,200+

times opened

Host an HTML file in four steps

  1. 1

    Make it one self-contained file

    Inline your CSS in a <style> tag and your JS in a <script> tag, and reference any images by full https:// URLs or as base64 data URIs. If your CSS/JS/images live in separate files right now, this is the only prep step that matters, everything the page needs has to be inside the one .html you upload.

  2. 2

    Upload the .html file

    Drag it onto the card and sign in with Google, one tap, no form. A free account gives you 20 hosted pages, up to 100 MB each. The file is validated by its real bytes, not its name, so only genuine HTML is accepted.

  3. 3

    Open the live link to check the render

    Your page is served at a clean, shareable link and shown live in a sandboxed browser view. Open it yourself first, because scripts run isolated, a page that reaches for a parent window or a same-origin cookie will behave differently than it did on localhost. Fix and re-upload if needed.

  4. 4

    Share the link (or its QR code)

    Send the URL, or download the auto-generated QR code to drop into a slide, a printout, or a poster. Every open increments a view counter so you can see the page is actually getting looked at.

A one-page site with zero infrastructure

The classic case: you hand-coded an index.html, a coming-soon page, an event RSVP, a link-in-bio, a wedding details page, and every hosting guide wants you to buy a domain, point nameservers, and wait for propagation. Here the page is live the second the upload finishes, at a link you can share by text. Because it renders live rather than showing markup, visitors see the real page with its layout, fonts, and hover states intact. The honest limit: it's genuinely one file. If your site is index.html plus a /css folder and an /images folder, either inline everything into that one file or this isn't the right tool, a bucket of assets won't wire itself together.

Sharing an exported HTML report

Plenty of tools export a self-contained .html: a pytest or Jest coverage report, a Playwright run, an Allure or pandas-profiling summary, a Lighthouse audit, a Jupyter notebook saved as HTML. These are already built to be one file with everything inlined, which makes them a near-perfect fit. Instead of zipping the report and emailing it, where the recipient has to download, unzip, and find the entry file, you send one link that opens the interactive report in their browser. The view counter tells you the client or teammate actually opened it, and the link keeps working for the next person who needs it. Interactive charts and collapsible tables keep working as long as their JS was inlined into the export.

Previewing a coded email or newsletter

HTML email is its own painful format, nested tables, inline styles, no external stylesheets, and before you push a campaign you want a stakeholder to see the rendered result, not the source. Paste your Mailchimp, Klaviyo, or MJML-compiled output into a .html file, host it, and send the link for sign-off. Two honest caveats worth stating up front: a browser render is not a true inbox render (Gmail and Outlook strip and rewrite things their own way, so use this for layout/copy review, not final QA), and any tracking pixels or click-tracking links baked into the export will still point at your ESP. Strip those out of the review copy if you don't want your own test opens counted.

A rendered landing snippet or code demo

When you're prototyping, you often have a single file that is the whole thing: a Tailwind-via-CDN landing hero, a CSS animation you're proud of, a canvas sketch, a small D3 or Three.js demo, a component you built to show a client. A live link beats a CodePen or a screenshot when you want it to look like a real page on a real URL, no editor chrome around it, opens full-screen on a phone. As long as your libraries load from a CDN over https and your code is inlined, it runs. This is the fastest way to turn 'here's a rough idea' into 'open this on your phone' without a deploy pipeline.

Why it renders in a sandbox (and what that means)

Your HTML is served inside a sandboxed frame without same-origin access. This protects both you and every visitor: untrusted markup can't read cookies, can't reach the parent page, and can't act as if it's part of the host. For 95% of pages, layout, styling, animations, CDN libraries, self-contained scripts, you'll never notice. Where you will notice: code that assumes it owns the top-level window, that needs first-party cookies or localStorage, or that talks to an API which only allows a specific origin (CORS). Those are custom-app concerns, and for them a real host is the right call. On Pro you can put a hosted page on your own domain in the address bar with automatic SSL, but the page still renders sandboxed, so the same script limits apply. For hosting a page to be looked at, the sandbox is a feature, not a limit.

Who this is for, and who should look elsewhere

Great fit: developers, designers, students, marketers, and no-code builders who have a finished single .html and need a URL now, a demo for a client, a report for a manager, a snippet for a teammate, a one-pager for an event. Not the right fit: a multi-page site with internal links between .html files, an app that needs a backend or environment variables, anything requiring your own domain in the URL bar, or a build step that outputs a /dist folder of separate assets. For those, use a real host. If your only blocker was 'I don't want to set up hosting for one file,' this removes exactly that blocker and nothing more.

What will you share?

Pick a file type to see what the person you send it to gets. No app and no account needed to open any of them.

Websites & HTML

A live web page from one HTML file

Upload an HTML page, a prototype or something an AI tool built for you, and it's live at a clean address. On Pro, drop a whole ZIP and the site goes up with SSL.

Frequently asked questions

Still stuck? Ask us directly — a real person answers.

Yes. Everything the page needs must be inside the one file or loaded from an https:// URL, inline your CSS and JS, and reference images as full URLs or base64 data URIs. Separate .css/.js files or an images folder won't be linked up.

Plans priced for client work, not per seat

Compare every plan →
Free
$0

20 links · 100 MB total · 3 albums

  • Clean links, QR codes & in-browser preview
  • View counts on every link
  • No app or account for viewers
  • Links never expire, nothing goes offline
Start free
Pro · Monthly
$9/mo

Unlimited links · 15 GB · 200 MB per file

  • Password, expiry & view limits
  • Notify-on-open + advanced analytics
  • Custom link name, no branding
  • Watermark, email gate & static hosting
  • Cancel anytime
Go monthly
Most popular
Lifetime
$99 once

Unlimited links · 30 GB · pay once, keep it

  • Everything in Pro, forever
  • One payment, no subscription
  • Best value for steady client work
  • 30 GB storage, 250 MB per file
Buy Lifetime

Coming from WeTransfer, DocSend or tiiny.host? See the comparisons →

Your link is 10 seconds away

Sign in free with Google — one tap, no form — and share one clean, trackable link.