PDF hosting, without regretting your URL

I had a PDF that needed to live somewhere. Not be emailed, not sit in a folder on my laptop, but actually live at an address I could drop into a footer, a cold email and a bio link without thinking about it again. That is all PDF hosting really is, and most of the tools people recommend for it are quietly solving a different problem.

Hosting a file and sending a file are not the same job. Sending is a one-off: you push a copy at someone and hope. Hosting is a decision about where the file permanently sits and which URL points at it. Once that difference clicks, choosing gets easier, because the question stops being "which host is best" and becomes "what do I need this URL to do".

PDF hosting just means the file lives at an address

Strip the marketing off any online PDF hosting service and it does two things. It keeps your file on a server that stays switched on, and it gives you a link that resolves to that file. Everything else is bolted on top: a viewer, a custom domain, a password, a page counter, a form in front of the download. Those extras are what you are actually paying for, and some of them you will never use. I paid for a custom domain on a hosted PDF exactly once and regretted it inside a month, because nobody was typing the URL. They were clicking it.

There is also a floor under this decision. Most inboxes still cap attachments around 25 MB, and Google lifted its own send limit to 50 MB only for Workspace Enterprise Plus accounts, from February 2026. Past that you are hosting the file whether you call it hosting or not.

The better reason to host rather than attach is boring and it holds up. One copy exists. You can fix a typo on page four at four in the afternoon and everyone who opens the link afterwards gets the corrected version, including the people who opened it yesterday. Once a PDF is in someone's inbox it is frozen, and every correction after that is a new email starting with "sorry, use this one instead".

Free PDF hosting is real, and the file size cap is where it bites

Free PDF hosting exists and it works. The catch is almost never the price, it's the ceiling.

Take Tiiny Host, one of the better ones for turning a PDF into a webpage. The free plan gives you a yourname.tiiny.site address, 5,000 visits and 5 GB of bandwidth a month, and a cap of 0.5 MB on a PDF. Half a megabyte. Fine for a two-page price list, useless for anything with photographs in it. Removing the banner and lifting that cap to 25 MB puts you on their entry paid plan, $5 a month when billed annually ($60 upfront) or $9 month to month, and password protection plus a custom domain sits above that again, per their pricing.

Issuu does the same thing from a different angle: the free tier allows five publications at ten pages each, with its own branding and third-party ads wrapped around your document. Fine for a portfolio piece. Not fine for a client proposal, unless you enjoy explaining the advert.

Neither of those is a criticism, it's the business model, and an honest one. But it does mean "free PDF hosting" is a real answer for a small, light, low-stakes document and a trap for anything else. Work out your file size first, then go shopping. I've watched people compress a perfectly good report into a blurry mess to squeeze under a cap, then call it a win.

A Google Drive link is hosting, it just isn't publishing

Most people's first PDF host is Google Drive, and for good reason. It's already there, the storage is generous, and set to "anyone with the link" it gives you a working URL in about fifteen seconds.

What you get is a Drive viewer wrapped around your file: Google's chrome around the edges, a download button, and a sign-in prompt for some people depending on how their account is set up. It reads as a file someone shared with you, not as a document that lives on the internet. For an internal report that's worth nothing. For something going to a prospect, it's the difference between looking organised and looking rushed.

The bigger problem is that the link hangs off the file's permissions rather than a page you control. Moving the file usually keeps the same link, but change the share setting, transfer ownership, or leave the organisation that owns the Drive, and the link stops working for everyone who had it. I've been on the receiving end of that more than once: a link in an old email that now resolves to a request-access screen.

For the mechanics of getting a shareable link out of a file, I've written that up in file to URL and in the plain-English version of sharing a PDF as a link. For the tool-by-tool comparison, PDF sharing sites is the honest rundown.

The decision is what happens after someone clicks

Most hosting comparisons skip this bit. Every option will store your PDF and hand you a URL, and they stop being interchangeable at the moment someone opens it.

A plain host tells you nothing, or a visit count if you're lucky. A tracking tool such as DocSend tells you it was opened, how long they stayed and which pages they lingered on, which is genuinely useful and is why people pay for it. None of them tell you whether the document made sense, because a PDF sitting on a server has nobody next to it explaining anything.

That gap is why I ended up building LiveDocument. You host the PDF, record a short video walkthrough over it, and the reader gets one link with the document and your face and voice beside it, plus clickable highlights that jump the video to the bit they care about. I get page-level engagement analytics and can see where someone slowed down. It is not storage, not a PDF editor and not a data room: the access controls are link expiry and revocation, so if you need watermarking or an NDA wall in front of the file, DocSend is the honest pointer and I'd send you there. Pricing is on the pricing page.

For a menu or a spec sheet, that is overkill and a static host is the right answer. For a proposal, where the whole point is that someone understands it, hosting the file and then walking away has always struck me as stopping just short of the useful bit.

What I'd actually do

If the document is small, public and unlikely to change, put it on a dedicated PDF host, use their subdomain and spend nothing. If it's going to be updated, keep the source somewhere you control and treat the host as a publishing step rather than storage. If it's going to one person who has to act on it, the URL was never the hard part and you should be thinking about whether they'll understand the thing.

I still send plenty of plain hosted links, and most of the time that is the right call. I've just stopped treating the link itself as the work.

FAQ

Is free PDF hosting safe to use for client documents?

For anything genuinely confidential, no. Free tiers typically publish to a public URL with no access controls, so anyone who has or guesses the link can read it. Use a host with password protection or link expiry, and check the free plan actually includes those before you upload. Usually it doesn't.

Can I host a PDF online permanently for free?

You can, as long as you accept the size ceiling and the provider's branding, and keep the account alive. Some free plans require you to log in periodically to stay active, so read that bit of the terms. If the document matters, a few pounds a month buys a link you don't have to babysit.

Will Google index a hosted PDF?

Yes, Google crawls and indexes PDFs and ranks them like any other document, which is why a well-written hosted PDF can quietly pull search traffic for years. It also means "unlisted" is not the same as private, so don't rely on an obscure URL to keep something unpublished.

Can I tell if someone read a PDF I hosted?

A basic host gives you visits at best, while a tracking tool gives you opens, dwell time and page-level detail. I've gone into that difference in can you tell if someone opened a PDF, including why an open is a much weaker signal than it feels like.

PDF hosting explained, and how to pick a host you won't regret