Sending a PDF via text: what actually works

Sending a PDF via text is easy. You tap the paperclip or the plus icon, pick the file, hit send. Done in ten seconds.

Whether the other person opens it, reads it, and gets what you meant is a different question. A PDF dropped into a text thread has nothing around it. No context, no guide, and it's sitting between a photo of someone's dog and a "running 5 mins late".

Here's how I'd do it, and when each method makes sense.

The two ways of sending a PDF by text message

There are only two real options.

Attach the file. Your phone's messaging app sends the PDF itself. On an iPhone that's Messages, on Android it's Google Messages or whatever your carrier pushes, plus WhatsApp and the other chat apps if you're not using plain SMS.

Send a link. You upload the PDF somewhere, copy the URL, and paste it into the message. The recipient taps it and the document usually opens in their browser, though exactly what happens depends on the host and their phone.

Attaching feels like the obvious choice because it's what you'd do in email. For a text, I think the link is usually better. I'll explain why.

Attaching a PDF works, until it doesn't

Attachments are fine for a one-pager going to someone you're already talking to. A receipt, a boarding pass, a signed form your mum needs.

They get awkward fast. Messaging apps and carriers can cap file sizes, and the limits differ between plain texts, iMessage and chat apps, so a big PDF can fail or get compressed depending on who's on the other end. Check your own phone and app rather than trusting a number from me.

There's also the opening problem. Tapping an attachment on a phone often means a preview, then a share sheet, then a PDF viewer. If the file is a deck built for a wide screen, they're pinching and zooming on a tiny window.

And once you've sent it, that's it. You can't reliably fix a typo, swap in a newer version or pull it back. Some phones let you unsend within a short window, but recipients on older systems may still see it, so assume the old one stays in their thread.

Sending a link is cleaner than attaching the file

A link sidesteps most of that.

Size stops mattering. A link is a line of text, however big the PDF behind it.
One version. If you update the file behind the link, everyone sees the current one. If you'd rather stop access, you can turn the link off.
It usually opens in a browser. Often no viewer app and no download, though that depends on the host and the recipient's phone.
You get a signal. With the right tool you can see whether it was opened. A bare attachment tells you nothing beyond "delivered".

If you haven't got a link yet, the quickest route is a free PDF to link converter, and I've written up what each one quietly costs you. The longer explanation of why a URL beats a file is on sharing a PDF as a link.

A quick practical note: paste the link on its own line, with a short sentence before it saying what it is. A naked URL from a number they don't recognise looks like spam. "Here's the proposal we talked about, page 3 has the numbers" doesn't.

How to send a PDF by text, step by step

On your phone, the flow is roughly the same everywhere.

Get the PDF onto your phone, or make sure it's in your cloud storage or files app.
Decide: attach it (small, simple, informal) or link it (anything that matters).
For an attachment, open the thread, use the attach or plus button, choose the file, send.
For a link, copy the URL from wherever the file is hosted, paste it into the thread, and add one line of context.
Check it opens properly on a phone. Open it yourself from the thread if you can.

That last step is the one people skip. If it's a PDF someone will read on a phone, you want to know it's readable on a phone before you send it to a client.

A PDF in a text gets ignored more than one in an email

This is the opinion bit. Texts feel casual, so people send serious documents through them with casual effort. A proposal with no intro, a contract with no explanation, a deck with "see attached" energy.

I spent years in growth roles sending decks and one-pagers, and the ones that landed were never the ones with the best formatting. They were the ones where the reader knew what to look at and why. In a text thread, with notifications stacking up, that matters even more.

A text is a nudge. The document is the substance. If you hand over the substance with no guidance, don't be surprised when the reply is "thanks, will have a look" and then silence.

When the PDF needs explaining, put your face on it

If the document is more than a receipt, the fix isn't a better attachment. It's explaining it.

You could type a long message walking through the pages, but nobody wants to read an essay in a text thread. You could record a video on your phone and send it separately, but now there are two things to open and the reader has to match one to the other.

This is what I built LiveDocument for. You attach a short video to your PDF (or an image file), and it goes out as one link. You talk the reader through it, you can add clickable highlights that jump the video to the right moment, and you see page-level engagement afterwards, so you know whether they got to page six. It works well in a text because it's just a link, and it makes a document feel like a conversation rather than a file dump.

It isn't a document editor or a storage tool, and it doesn't do e-signature. It's for the moment where you need someone to understand a PDF, not just receive it. There's more on how that works at sharing a PDF with a video walkthrough, and if you want the broader version of the video-plus-PDF idea, PDF with video sender covers why embedding video in the file tends to fail.

For tracking what happens after you send, that's PDF tracking software territory.

Texting a PDF to several people

Sending one PDF to one person is simple. Sending the same file to ten people by text is where attachments get silly, because you're uploading it ten times and losing track of who has which version.

A link fixes that too. One URL, pasted into each message, one version of the document. If you're moving more than one file around, the best way to send multiple files is worth a read, since the same logic applies outside email.

FAQ

Can you text a PDF from an iPhone or Android?

Yes. Both let you attach a PDF in a message, or paste a link to one. Attaching is quick for small files. A link is more reliable for anything large or important.

Why won't my PDF send by text?

Usually the file is too big for the messaging service or carrier, or the thread is set to plain SMS where attachments are limited. Sending a link instead gets round the size problem.

Is it safe to send a PDF via text?

Texts aren't a controlled channel. Anyone with the phone can open the thread, and an attachment can't be reliably recalled. For sensitive files, use a link restricted to the intended recipient, ideally one you can expire or revoke, which is safer than a file sitting in a thread forever. Revoking a link won't recall copies already downloaded.

What's the best way to send a PDF by text message?

For a small, casual file, attach it. For anything the reader needs to understand or you need to track, send a link with a line of context above it.

Send the link, not the file

Sending a PDF via text takes seconds. Getting it read takes a bit more thought: a link, a line of context, and ideally your voice on the document.

I built LiveDocument because I was tired of sending things into the void. If that's a feeling you know, it's at livedocument.com and the details are on pricing.