TL;DR

A PDF file on your laptop has no URL — it lives on your disk, not on the web. To "link to a PDF," you upload it to a host that gives it a public address, then share that address. The fastest free path is Google Drive (10 seconds, needs a Google account). Dropbox and OneDrive work identically. If you already have a website, drop the file in a folder and link it directly. If the PDF doesn't exist yet, build it first with Convert Anything to PDF, then host it. This guide walks through each option with the exact clicks.

If you just want the link and don't care which service:

  1. Open drive.google.com in a signed-in tab.
  2. Drag your PDF into the browser window. Wait for the upload bar to finish.
  3. Right-click the file. Pick Share → Share.
  4. Under General access, change Restricted to Anyone with the link.
  5. Click Copy link. Paste it wherever you need to.

That is the entire flow. The link works in email, Slack, WhatsApp, LinkedIn posts, and anywhere else a URL is clickable. The recipient opens it in a browser tab. They don't need a Google account. They don't need to install anything.

Two things worth knowing before you paste:

The default link opens Google's PDF viewer, not the raw file. That's fine for most sharing — the viewer works on phones, doesn't require a download, and shows a page-turning interface. But it embeds your file inside Google Drive's chrome (a header, a download button, a "sign in" prompt in the corner). If you want the link to trigger a direct download instead, or you want the URL to end in .pdf, you need to modify the link — covered later in this post.

The link is public. "Anyone with the link" means literally anyone who has the URL can open the file. Google Drive doesn't index these links in search, but if you paste the link in a public forum, a chat log that gets scraped, or a shared doc that leaks, the file leaks with it. For anything sensitive, use "Anyone in your organization" if you're on Workspace, or password-protect the PDF before uploading (Adobe Acrobat, Preview on Mac, or a tool like Convert Anything to PDF can encrypt).

That's the shortcut. The rest of this post covers when each host is the right choice, and what the tradeoffs are.

Why PDFs need to be hosted first

A URL is an address on a web server. Your laptop is not a web server. When you save a PDF from Word or from a browser's Print dialog, the file lives at a local path like C:\Users\you\Documents\invoice.pdf or /Users/you/Downloads/invoice.pdf. Nobody else can reach that path. Emailing it to yourself doesn't help — the file lives in Gmail's storage, not at a public URL.

To get a URL you need three things:

  1. Storage that's connected to the internet. A folder on a machine that's always online, with a public IP.
  2. A web server that will hand the file to anyone who asks for it. Something that listens for HTTP requests and responds with the file contents.
  3. A domain and path that map to the file. So the request https://example.com/invoice.pdf reaches the right byte range on disk.

Setting all three up yourself is a project. Which is why hosted services exist: Google, Dropbox, Microsoft, AWS, and dozens of others solve the storage + server + URL problem and hand you a link in exchange for a signup (and, past a few gigabytes, some money).

There is no "convert PDF to link" feature in Windows or macOS the way there's a "print to PDF." The PDF is a file. The link is a hosted address. You always need a host, even if the host is your own domain. Anyone who tells you otherwise is either using a hosted service without noticing (email attachments in Gmail are actually stored on Google's servers) or misunderstanding what a URL is.

The rest of this article compares the hosts, in order from fastest-to-set-up (Google Drive) to most-under-your-control (self-hosted).

Google Drive step-by-step

Best for: quick one-off sharing. You probably already have a Google account. Fifteen GB free.

Upload:

  1. Go to drive.google.com.
  2. Click + New in the top-left, then File upload. Or drag the PDF onto the page.
  3. Wait for the progress toast at the bottom-right to say "Upload complete."

Get the link:

  1. Right-click the file in the file list. Pick Share → Share (yes, it's nested).
  2. In the dialog that opens, under General access, click Restricted and change it to Anyone with the link.
  3. Leave the role as Viewer (unless you want people to be able to comment or edit — you almost never do for a PDF).
  4. Click Copy link at the bottom-left, then Done.

The link you copied looks like:

https://drive.google.com/file/d/1AbCdEfGhIjKlMnOpQrStUvWxYz/view?usp=sharing

That's the viewer link. Opens Google's built-in PDF preview in a browser tab. Fine for 90% of sharing.

If you want a direct-download link — the recipient clicks and their browser starts downloading the file instead of previewing it — replace view?usp=sharing with uc?export=download:

https://drive.google.com/uc?export=download&id=1AbCdEfGhIjKlMnOpQrStUvWxYz

The id= value is the same long string in the middle of the original URL.

Watch out for:

  • Google Drive scans PDFs for viruses before letting large files download. Files under 100 MB download instantly; larger files show a "we can't scan this file" warning that recipients have to click through.
  • If your Google account is at the 15 GB storage limit (email + Drive + Photos combined), the upload will fail silently until you free space or upgrade.
  • If you're on a Workspace account with sharing restrictions, "Anyone with the link" may be greyed out. In that case you're limited to sharing inside your organization.

Dropbox step-by-step

Best for: sharing with people who also use Dropbox, or when you want a slightly cleaner viewer experience. Two GB free (upgraded plans get more).

Upload:

  1. Go to dropbox.com and sign in.
  2. Click Upload in the top-right, then Files. Or drag the PDF onto the file list.
  3. Wait for the "Uploaded" confirmation.

Get the link:

  1. Hover over the file. Click Share on the right side of the row.
  2. In the dialog, click Create link (or Copy link if one already exists).
  3. Paste the link where you need it.

Dropbox links look like:

https://www.dropbox.com/scl/fi/abc123xyz/invoice.pdf?rlkey=somekey&dl=0

The dl=0 at the end opens the file in Dropbox's viewer. Change it to dl=1 and the link triggers a direct download instead. You can also use raw=1 to get the raw PDF served inline (useful if you want to embed the PDF in an <iframe> on a page you control).

Watch out for:

  • Free Dropbox accounts get a bandwidth cap. If your shared link gets hit by thousands of downloads in a short window, Dropbox will temporarily disable the link. For most personal sharing this doesn't matter; for a link you're posting somewhere with real traffic, it does.
  • Dropbox's viewer is cleaner than Google's — less UI, closer to just showing the PDF — but it still shows a "Sign up for Dropbox" banner at the top for non-users.

OneDrive step-by-step

Best for: Windows and Microsoft 365 users. Five GB free on personal accounts; 1 TB if you have a 365 subscription. Business users get whatever their tenant allots.

Upload:

  1. Go to onedrive.live.com and sign in.
  2. Click Upload at the top, pick Files. Or drag the PDF into the browser.
  3. Wait for the upload counter to finish.

Get the link:

  1. Right-click the file in the file list. Pick Share.
  2. In the dialog, click the pencil icon next to "People you specify can edit" to change permissions.
  3. Change People you specify to Anyone with the link.
  4. Change Can edit to Can view (unless you actually want editing).
  5. Optional: set an expiration date and a password. This is the only free consumer host that offers both.
  6. Click Copy link and paste.

OneDrive links look like:

https://1drv.ms/b/s!AbCdEfGhIjKlMnOpQrStUvWxYz

Short, but it's a redirect. The final URL is a long OneDrive viewer URL. To force a direct download, add ?download=1 to the final URL after it resolves.

Watch out for:

  • OneDrive's viewer is the weakest of the three — it sometimes fails to render PDFs generated by non-Microsoft tools, showing "This item might not exist or is no longer available."
  • Business tenants often lock down external sharing. If Anyone with the link isn't available, your admin has disabled it, and you're limited to sharing with specific email addresses.

Self-hosted (your own domain, S3, GitHub Pages)

Best for: PDFs you'll share often, embed on a website, or link from something you're publishing. No banners, no login prompts, no bandwidth caps you didn't sign up for. The URL is yours, on a domain you control.

Three practical options, in order of difficulty:

GitHub Pages. Free. If you have a GitHub account, create a public repo, drop the PDF into the repo root, enable Pages in the repo settings, and the file lives at https://yourusername.github.io/reponame/yourfile.pdf. Setup takes about ten minutes if you've never used GitHub, five seconds if you have. Downside: the whole repo is public, so the file is technically discoverable by anyone browsing your GitHub profile.

A folder on your own website. If you already run a site — WordPress, Ghost, Squarespace, a plain HTML site on Netlify or Vercel — most platforms let you upload a PDF and get a URL like https://yoursite.com/uploads/2026/whitepaper.pdf. In WordPress it's Media → Add New. In Ghost it's in the file uploader on any post. On a static site, it's git add whitepaper.pdf, commit, deploy. This gives you the cleanest link, no viewer chrome, no third-party branding, and analytics if your site is set up to track file downloads.

Amazon S3 (or Cloudflare R2, Backblaze B2). Best for developers who want cheap, scalable storage and don't mind clicking through a cloud console. Create a bucket, upload the file, set the object's ACL to "public-read," and the file is available at https://your-bucket.s3.amazonaws.com/yourfile.pdf. Costs pennies per month for casual use. R2 and B2 are cheaper if you'll get any real traffic — S3 charges for egress, R2 and B2 don't.

For any of these, the URL you get is a direct link to the raw file. No viewer, no login. When someone opens it, their browser either displays the PDF inline (using its built-in PDF renderer) or downloads it, depending on their browser settings. This is the cleanest possible link — what everyone thinks a "PDF link" is before they discover Google Drive's viewer wrappers.

The tradeoff is setup time and ongoing maintenance. A GitHub Pages repo will still be there in three years. An S3 bucket will still be there in three years. A shared Google Drive link will still be there in three years too — until you (or Google) delete the file. Pick based on how much control you want vs. how much time you want to spend.

Direct-download URL vs viewer URL

Every hosted service produces two kinds of URLs for the same file, whether they tell you or not:

  • Viewer URL: opens the file in the host's in-browser preview (Google Drive viewer, Dropbox viewer, OneDrive viewer). The URL usually doesn't end in .pdf. The user sees the PDF wrapped in the host's UI — a header, sometimes a login prompt, usually a Download button.
  • Direct-download URL: the browser either downloads the file or renders it inline using its own PDF viewer. The URL often ends in .pdf. No wrapper, no branding, no login prompt.

Which one you want depends on the audience:

  • Sharing with one person over chat? Viewer URL is fine. Less scary than a random download starting.
  • Linking from a webpage, an email newsletter, a job application? Direct-download URL. Recipients trust example.com/resume.pdf more than drive.google.com/file/d/xyz....
  • Embedding the PDF inside a page (<iframe> or <embed>)? You need a raw direct link. Google Drive's viewer URL will render an iframe that shows a Google login prompt for logged-out users, which is a broken experience.
  • Legal / compliance archive? Neither, really. Use a service that produces a signed URL with an audit trail (SharePoint, Box, DocuSign), or self-host on infrastructure you control. A "public link" on a consumer service is fine for convenience, not fine for evidence.

The conversion from viewer to direct-download is different for each host — Google Drive uses uc?export=download&id=, Dropbox uses ?dl=1, OneDrive uses ?download=1. Save these three transformations somewhere; they cover 95% of the "how do I get the direct link?" cases you'll hit.

Comparison table of hosts

HostFree storageSetup timeDirect-download link?Password protectionCustom domainBest for
Google Drive15 GB (shared with Gmail, Photos)Under 1 minYes (URL edit)No (Workspace only)NoFast one-off shares
Dropbox2 GBUnder 1 minYes (?dl=1)Paid plans onlyNoSharing with Dropbox users
OneDrive5 GB (1 TB with 365)Under 1 minYes (URL edit)Yes, freeNoWindows / 365 users
GitHub PagesUnlimited (100 MB/file)~10 minYes (native)NoYes (custom domain)Devs, public docs
Your own websiteDepends on hostDepends on stackYes (native)Depends on stackYesPDFs you'll share often
S3 / R2 / B2Pennies/month~15 minYes (native)Signed URLsYesHigh-traffic hosting

The three consumer options (Drive, Dropbox, OneDrive) are almost interchangeable at the free tier for casual use. Pick whichever ecosystem you already live in. The three developer options (Pages, own site, S3) all produce cleaner URLs at the cost of more setup — pick based on where you already have infrastructure.

If you don't have the PDF yet — you have a webpage, a Word doc, a set of images, or something else you need to turn into a PDF first — do the conversion locally before uploading. Convert Anything to PDF handles the common formats in your browser without uploading the source file anywhere, which matters if the content is sensitive. Related walkthroughs: convert HTML files to PDF locally and batch convert files to PDF.

If you're linking to a webpage and thinking about whether a PDF is even the right format, how to save a webpage as a PDF covers the tradeoffs. Sometimes a PDF is the right archive; sometimes an actual link to the live page is better. For public URLs that need to survive after the source page changes, save it as a PDF and host that.

Frequently asked questions

Upload the PDF to a hosted service (Google Drive, Dropbox, OneDrive, or your own website) and copy the sharing URL it hands back. A PDF file on your own device has no URL — it lives locally, not on the web. Google Drive is the fastest option if you already have a Google account: drag the file to drive.google.com, right-click, pick Share, change access to "Anyone with the link," and copy. The whole flow takes about thirty seconds and gives you a URL you can paste anywhere.

There's no button on your computer that "converts" a PDF into a link — a link is an address on a web server, and your computer isn't one. What you actually do is upload the PDF to a service that has a web server (Drive, Dropbox, OneDrive, S3, your own hosting), and that service gives you back a URL pointing at the uploaded file. Any of the flows in this guide will get you there in under a minute for a normal-sized PDF.

Highlight the text you want to link, click the link icon in the toolbar (or press Cmd/Ctrl+K), and paste your PDF URL. If the PDF is already on Google Drive, you can also click Insert → Link, search for the file by name, and Google Docs will insert the sharing URL for you. Make sure the PDF's sharing permission is set to "Anyone with the link" — otherwise readers who click the link will hit a "You need access" wall.

Nothing in normal usage — people use "link" and "URL" interchangeably. A URL (Uniform Resource Locator) is the technical name for the web address, and a link is what you click to visit that address. When someone says "make a PDF link," they mean "get a URL pointing to a PDF and put it somewhere clickable." Some services distinguish between the viewer URL (opens the file in their in-browser preview) and the direct-download URL (browser downloads or inline-renders the raw file), but both are URLs and both are links.

Dropbox and OneDrive work exactly the same way — drag the file to their web interface, right-click, share, copy the link. Both have free tiers. If you already have a website (WordPress, Ghost, Squarespace, a static site on Netlify or Vercel), upload the PDF through your site's media manager and use the URL it gives you — that's the cleanest option because the URL lives on your own domain. GitHub Pages is the developer-friendly free option: commit the PDF to a public repo, enable Pages, and the file is available at https://username.github.io/repo/file.pdf.

Bottom line

There's no such thing as a standalone "link to a PDF" — every URL points to a file that lives on a server somewhere. The fastest way to get a link is Google Drive, but the best link (short, on your own domain, no viewer chrome) is one you host yourself on a website, GitHub Pages, or S3. Pick based on how often you'll share the file and how much control you want over the URL.

If the PDF doesn't exist yet — you're starting from a webpage, a Word doc, images, or something else — build it first with Convert Anything to PDF, then upload it wherever you're going to host. Local conversion, no uploads of the source file to a random converter, and the finished PDF is on your disk ready to share.