PDF with video sender: what actually works

Embedding a video in a PDF is possible and usually a bad idea

You can genuinely do it. Adobe's rich media documentation confirms Acrobat handles H.264-compliant video, which in practice means MP4 and MOV. Some other formats may need QuickTime or Windows Media Player installed on the reader's machine to play back in older versions of Reader. FLV and F4V are gone entirely and cannot be embedded.

So the feature is real. The trouble starts after you press send.

Playback depends on what the reader opens the file in, and you do not get to pick that. Gmail's preview pane, Chrome's built-in viewer, Preview on a Mac, whatever a phone decides to do with an attachment. In my own testing, embedded video has come back as a dead grey rectangle more often than it has played cleanly, and I am not sending a prospect a document whose fallback state is a dead grey rectangle. Adobe's page makes no claim either way about third-party viewers, so treat that as my experience rather than documented behaviour, and open it on a phone before you trust it.

Then there is file size. Most email systems cap attachments at around 25 MB, and a three minute screen recording will eat most of that before you attach the PDF. I go into the format and playback detail in can you add a video to a PDF, if you want the longer version.

Two tabs, and the bit that gets lost between them

The workaround most people land on is a Loom link plus the file. Record the walkthrough, drop the link in the email body, attach the PDF underneath. I did that for years, running growth at DataBees and then go-to-market at WaterFull. It works, and it is where I got most of my ideas about what was missing.

The reader has to hold two things at once. Your voice is describing page six of a document that is in another tab, in their downloads folder, or not open at all. When you say "the assumption we made on headcount", they have to go and find the bit you mean. Most people don't bother. They watch the video or they skim the document, rarely both in the order you intended.

You also lose the thread the second it gets forwarded. The email goes to the person who actually signs, the attachment travels, the Loom link sometimes doesn't, and your document is now doing the rounds internally with no explanation attached. If you are weighing that setup against the alternatives, I have put the comparison side by side in LiveDocument vs Loom.

What a pdf with video sender needs to do

Once you have decided to send a PDF with a video rather than embed one, only a few things really matter.

The document and the video need to live at one address. One link, one page, no download step, and nobody having to be told that the video is up in the email somewhere. If someone forwards that link and the whole thing survives, you are most of the way there.

The video also needs to be tied to the document rather than sitting next to it. Clicking a highlighted section and having the video jump straight to the bit where you explain it is what separates a walkthrough from two files in a trenchcoat. It means the reader can skip to the ninety seconds they actually care about, which they will do whether you design for it or not.

And you want to know what happened afterwards, not just that it opened. Which pages held them, what they went back to a second time, whether anyone reached the section you were nervous about. That is the whole point of page-level tracking as far as I am concerned: it tells you what to say on the next call.

That combination is what we built LiveDocument for. You upload a PDF or an image, record a walkthrough over it, add clickable highlights that jump the video to the relevant part, and share it as one link with the video attached to the document. Links can be set to expire, and you can revoke one if a deal dies or it went to the wrong address.

What to actually say in a PDF video walkthrough

This is the part people get wrong before deciding the whole format doesn't work.

A walkthrough is not you reading the document out loud. The reader can read. What they cannot do is ask you the questions they will otherwise sit on for a fortnight.

On a proposal, that is usually: why the number is what it is, what happens if the timeline slips, and the assumption you had to make because you did not have all the information yet. Say the assumption out loud. It is the most useful thing you can put in a walkthrough, because it is what gets quietly misread when nobody is there to explain it.

On a report, name the page that actually matters and say why the others exist. On a pitch deck, talk through the traction slide honestly rather than leaving the numbers to be interpreted by someone who was not in the room.

Keep it to a couple of minutes and do it in one take. A scrappy recording where you sound like a person beats a polished one you rerecorded four times, and it is far more likely to actually get sent.

What LiveDocument will not do for you

There are a few limits worth being straight about, because I would rather you knew now than three weeks in.

It is not storage, and not a video host you can pull an embed code out of. It is not a PDF editor either, so if the document itself is wrong you fix that wherever you made it and upload again. And if you are running a diligence process with folder permissions and hundreds of files, you want a proper data room.

On access control, what exists is link expiry and revocation. No watermarking, no NDA gate. If compliance requires either of those, you need a different tool.

And it will not rescue a document with nothing worth saying about it. A video of you talking through a wrong proposal does not make the proposal any less wrong.

Questions people ask