Free hosting comes in two shapes, and they fail in opposite directions. Here's what actually happens when a free quota runs out, what expiry does and doesn't destroy, and how to match the shape to what you're sharing — including where we're the wrong answer.
Someone in a group chat asked how to share a site they'd just built. A few link tools got suggested. Their reply was the interesting part: free plans have daily or monthly limits — and they went off to learn a repository-based host instead, describing themselves as a non-technical person the whole way.
That's not an irrational choice. It's a reasonable answer to a question nobody had answered for them: will this link still be there when I need it?
Every free tier is free for a reason, and the reason tells you how it will behave in six months.
Free because the page is public and permanent. Repository-based and static hosts give you space on the web. Permanence is the entire product; there's no clock. What they ask for instead is a bit of setup — a repo, a build, some deploy vocabulary — and openness, since the page is on the public web by default. The cost is front-loaded, once.
Free because the link is short-lived. Handoff tools give you speed: file in, URL out, no configuration. What they ask for is that the link has a lifespan, because these tools exist for work that has a lifespan — the draft, the proposal, the report you send on Tuesday and nobody opens after Friday.
Reading a free tier as "generous" or "stingy" gets you nowhere. Reading it as a statement about what the tool is for tells you everything. Trouble comes almost entirely from putting a permanent job on a temporary tool.
This is where most of the anxiety lives, and it's mostly answerable. Two very different events get discussed as if they were one:
A ceiling — storage, page count, uploads per day. You hit it and the next upload is refused: a message telling you to delete something or move up. Everything you've already published keeps working. Nobody holding one of your links notices anything. This is survivable, and it's the kind of limit most people are actually worrying about when they say "free plans have limits."
A clock — expiry. This retires links you already handed out, on a schedule you agreed to at upload. Nothing is refused; something you sent stops working. This is the one that can embarrass you, and it's also the one that's entirely within your control if you set it deliberately.
A free tier can have both. Ask which you're dealing with before you build anything on it.
Worth checking per service, because the answers genuinely differ and the difference is large.
Here, expiry retires the link, not the document. The page stops serving to visitors; the document stays in your dashboard marked expired, and giving it a new window puts it back. That makes expiry a scheduling decision you can reverse, rather than a deletion you can't. (What a visitor sees when they arrive at a retired link is its own small design question — what the reader sees on the other end covers that side.)
Elsewhere, expiry can mean the file is gone. The question to put to any service is exactly one sentence: after it expires, is my file still there?
Since this is our blog, it would be evasive to describe everyone else's limits and not our own.
A free account here gets a 10 MB total budget, links on a seven-day default window, and one slot you can keep permanently. Paid plans drop the clock entirely — Solo and Studio let you set any window or none, on as many pages as you want, with more space.
The seven days is deliberate rather than a crippled trial: the majority of what people send through a tool like this is a deliverable, and a link that retires itself is doing the tidying you were never going to do. The single permanent slot exists because almost everyone has exactly one page that shouldn't retire — the portfolio, the menu, the link in a bio.
And the honest edge: if what you want is five permanent public pages for nothing, we're the wrong tool and a repository-based host is the right one. That's not modesty, it's a match problem — those services are free because permanence and openness are the deal, so you should take the deal. Where the shorter route earns its place is when the page is private, or temporary, or when you'd genuinely rather not learn a deploy workflow to put one file online. The free options compared side by side is the fuller version of this, including where each one is the wrong answer.
Everything above is recoverable except this: a link with a clock behind something printed.
Ink lasts years. A seven-day link doesn't. A QR code on a table, a business card, a package insert or a poster is a promise you've made in a medium you can't edit — so the link behind it needs to be one of your permanent ones, on a host where replacing the content keeps the same address instead of issuing a new one. Both halves matter, and both are decisions to make before the print run, not after.
For everything that lives in a chat window, the stakes are lower than the worry suggests: hit a ceiling and you delete something; retire a link and you can set a new window. The one to get right the first time is the one you can't reprint.
Instant hosts trade takedown for tamper-proofing — and most people meet that trade at the worst possible moment. What immutable actually means, why support usually can't help, and the three questions worth asking before you press publish.
Grok's share button makes a public link, and xAI says plainly it can be indexed by a search engine. On Grok Business the same button does close to the opposite. Here's what the person on the other end receives, and the page where you revoke it.
Anthropic's docs are explicit: on Free, Pro and Max, publishing makes an artifact publicly available to anyone with the link. Org-only sharing is a Team and Enterprise feature. Here's what that means if you're an individual sending work to one named client.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.