Uploading a PDF is a decision, not a step

    · 6 min read

    Uploading a PDF is the least interesting thirty seconds of your week and one of the more consequential ones. Drag, drop, wait, copy the link, paste it into an email. Done. Except the destination you picked in those thirty seconds quietly decides whether you can fix a typo without resending, whether you can cut off access when the deal dies, and whether you will ever know if the thing was read.

    Nobody thinks about this on the first upload. Everybody thinks about it on the third, usually while writing an apologetic follow-up containing the phrase "ignore the last one".

    What actually happens when you upload a PDF to Drive

    Take the most common route, because it is the one most of us default to. You open Google Drive, drag the file in, right click it, choose Share, and decide who should be able to open it before you copy anything. Adding named people keeps the file restricted to them. Changing General access from Restricted to Anyone with the link makes it open to whoever holds the URL, so only pick that for a file you would be happy to see forwarded. Google's own documentation walks through the same steps.

    Three things are now true that are easy to miss. The link is tied to that specific file object, so if you later upload a corrected version as a new file rather than using Manage versions on the existing one, your original link still points at the old copy, and the person you sent it to will never know. Anyone with the link means anyone: the URL is the credential, and it forwards perfectly well to people you did not have in mind. And Drive will tell you, at best, that someone with an account viewed it, which is not the same as knowing the document was read.

    For a menu, a policy document, an event flyer, none of that matters. Upload it, send the link, move on. The trouble starts when the PDF is doing a job.

    Uploading a PDF that has a job to do

    A proposal, a pitch deck, a client report, a lead magnet. These are documents where you care what happens next, and that changes the calculation entirely.

    What you want in that situation is the ability to replace the file behind the link without reissuing the link, the ability to switch the link off, and some idea of what the reader did. Cloud storage gives you the first if you are disciplined about versions, a partial version of the second, and essentially none of the third. Dedicated hosting and document sharing tools exist precisely to fill those gaps, and I have written up the landscape of those over in PDF sharing sites.

    The one I would push back on is emailing the file as an attachment. It feels safest because it is familiar, and it is the worst of the options. Once it has gone you cannot update it or take it back, you learn nothing about what happened to it, and on a big file there is a fair chance it bounces before it arrives. A sent attachment is a copy you have permanently lost control of. If you are going to send a document that matters, send it as a link.

    The question nobody asks before uploading

    Ask yourself what you want to be able to do a week from now. Fix it, kill it, or measure it. Whichever of those you might need is the thing that should pick the destination, and it takes about five seconds to think about.

    I learned this the slow way. In growth roles before this, I sent a lot of decks and one-pagers, and I got into the habit of uploading to whatever was nearest and pasting the link. Then a version went out with the old pricing on page four, the link was already in six inboxes, and I got to spend a morning writing emails about it. That morning cost more than every minute I ever saved by not thinking about where the file lived.

    When uploading the PDF is only half the job

    There is a category of document where hosting it well still is not enough, and it is worth being honest about which one you have. If the reader needs you to explain the thing, a link to a static file leaves them alone with it. They open it on a phone, skim four pages, form an impression, and reply with something non-committal.

    That is the problem LiveDocument exists for. You upload the PDF or image, record a walkthrough over it, and share one link that carries both the document and your voice, with clickable highlights that jump the video to the section you are talking about and page-level analytics showing where the attention went. It is not storage, it is not an editor, and there is no watermarking or NDA gating in it, so if what you need is a locked-down data room it is the wrong tool and I would say so. What it is good at is the gap between a document being opened and a document being understood.

    Frequently asked questions

    Where is the best place to upload a PDF?

    It depends on what you need afterwards. Cloud storage like Google Drive or Dropbox is fine for documents you will never need to update or measure. For anything client-facing, pick something that lets you replace the file behind the link, revoke access, and see engagement.

    Is uploading a PDF safer than emailing it as an attachment?

    Generally yes, because a link can be revoked and an attachment cannot. That only holds if you actually set the permissions rather than leaving the link open to anyone forever, so treat an open link as public.

    I built LiveDocument after one too many mornings spent chasing a document I had already lost control of. If that sounds familiar, it is at livedocument.com.

    About the Author

    Cameron James

    Cameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.