Best free way to share a PDF as a link: the options compared

The PDF is done. The proposal, the report, the portfolio, the price list: exported and sitting in your downloads folder. The only question left is how it reaches the other person. That's where it goes wrong. The attachment bounces off their mail server. The Drive link won't open for them. You try three "PDF to link" sites and still can't tell how they differ.

They are different, and the difference isn't which tool is best. It's which one is built for the job you're doing.

Before you pick: what does the other person have to do with it?

Three questions settle most of it.

Do they need to read it, or keep it? Reading needs a link. Keeping it, whether that's a contract going into e-signature, an invoice going into accounts, or a file a procurement portal wants uploaded, needs the file. When a system on their side has to hold the file, give them the file.

Do you need to know whether they opened it? An attachment tells you nothing after you hit send. Most link-based routes can at least tell you it was opened. A few can tell you how far they read.

Does the link have to work next month? A proposal gets revised. A price list changes. If the link will be clicked again later, you want to be able to change what's behind it, or have it stop working when it should.

What are the ways to share a PDF as a link?

There are five, and each is designed for a different job:

The next table has the details that change: who needs an account, whether you can swap the file, passwords, expiry, and what's free. Those numbers change, so they're dated and only come from each vendor's own pages.

Checked against each vendor's own help, pricing and FAQ pages on 19 September 2026, rechecked 19 October 2026 (Smallpdf's expiry and password rows comes from its own blog). "Not stated" means we couldn't find it on their pages, not that they don't offer it. Every vendor sets its own limits and changes them without telling us, so check their site for what's current. Our own row comes from our pricing page and plan limits.

Which one should I use?

The short version:

• They need the file itself. It's going into e-signature, an accounts system or a procurement portal, or they asked for "the PDF". Attach it. If they asked for the file, send the file.
• They need to sign it. Use an e-signature tool such as DocuSign or Acrobat Sign. A link to a PDF only lets them read it, and they still can't sign it.
• You want to know which pages they read, and for how long. That's a document-tracking tool, the kind sales teams use for decks. A basic link tells you whether it was opened. Page-by-page reading time is a different product, and if that's the question you're asking, use one.
• Your team already works in Google Workspace and the document will keep being edited there. Share it from Drive. Everyone is signed in already, and moving the file somewhere else just adds a second copy.
• You need to shrink, edit or convert the PDF first. That's what the PDF-tool suites are for. Do that step there, then share the result however suits the job.
• It's finished, it's going to specific people, and you want to keep control of the link: swap the file after a correction, put a password on it, or let it lapse after the pitch. A private-link host.

If the document isn't a PDF yet and you can still choose the format, why HTML beats PDF for deliverables makes the case for the other format. This page assumes the PDF already exists. For the wider trade-off between sending a file and sending an address, see an email attachment vs a link for deliverables.

What won't any of them fix?

A few things belong to the PDF, not to how you share it. Changing tools won't change them.

Pages don't reflow. A PDF is laid out at a fixed size. A dense A4 page is still a dense A4 page on a phone, whichever viewer draws it. Viewers can scale the page and keep it sharp, but they can't turn it into a column of text. If phone reading matters most, the document needs to be a web page, not a PDF.

A PDF locked with an open password is fragile as a link. The "open password" is the one needed just to read the file, not the one that restricts printing or copying. A viewer that draws the pages in a browser has to be able to ask your reader for that password, and ours can't. We tested it: the reader saw one line of error instead of the document. So we now refuse those files at upload rather than hand you a broken link. If you're using another tool, test a locked file in a private window before you send it. Either way, the fix is usually to put the password on the link instead of in the file. Password-protect the link, not the PDF covers the difference between the two PDF passwords.

It's a snapshot. A figure that changes tomorrow changes in the source document, and you export again. The link can point at the new export. It can't update the old one.

Can I share a PDF without letting them download it?

People ask this a lot, and the honest answer is shorter than most tools make it sound.

Our viewer has no download button. The reader scrolls through the pages in their browser and that's it. That is not download protection, and we won't call it that. To draw the pages, the file has to reach the reader's browser, and someone who knows where to look can keep a copy. Screenshots and printing are always there too.

Some drives and tools have a setting that hides download or print for viewers: Google Drive lets the owner turn it off, and Dropbox, FlipLink, tiiny and Jumpshare offer one on paid plans. Dropbox's own help page is candid that it "doesn't prevent people from saving the content" another way. Whatever it's called, it removes a button. It doesn't stop the reader keeping a copy. Anything shown on a screen can be captured.

So here's the practical rule. A link controls who can open the document, and for how long. It doesn't control what happens on their machine afterwards. If a document truly must not leave your hands, don't put it behind a link, ours included.

When a private link is the right shape

That's the job miinideck is built around: a finished PDF, going to specific people, where you want to keep the link in your hands.

You upload the PDF exactly as you exported it. It isn't converted to anything and it's stored byte for byte, so your fonts, spacing and images are the ones you chose. Your reader opens the link and the pages are drawn in their browser, on a laptop or a phone. They don't need an account, a PDF app or a download. If they turn the phone sideways, the pages are redrawn for the wider screen rather than stretched.

The link ends in 32 random characters, so nobody can guess it, and the page tells search engines not to index it. That's private in the practical sense: the people you send it to can open it, and so can anyone they forward it to. When that isn't enough, put a password on the link. It's free on any account and checked before any page loads.

After you send it, the link is still yours:

• Replace the file with a corrected version, and the link already in their inbox opens the new one.
• Let it expire. Free-account links run 7 days by default, and you can keep one on permanently. On paid plans you pick a date or leave it on.
• See whether it was opened. Every account shows how many times a link has been opened. Solo and Studio add when it was last opened and a day-by-day count. We don't do page-by-page reading analytics. If you need that, use a document-tracking tool.

The limits, stated plainly: a No-account upload takes a PDF up to 3 MB, runs for 7 days and can't be replaced. The Free tier takes 10 MB per file. Solo ($4.99/mo) takes 25 MB and Studio ($14.99/mo) takes 50 MB. A photo-heavy PDF exported for print gets big fast, and exporting at screen resolution usually brings it down. Putting the PDF inside another website isn't supported right now. Link to it instead.

---

If you already know which route you need, upload a PDF and get a link. There's no account needed for a quick one. If you want to see what the reader sees and what a link does and doesn't change about a PDF, read sharing a PDF as a private link.