Adding video to a PDF: three ways, and which one survives contact with a recipient
Adding video to a PDF is not the difficult bit. Adobe has had a tool for it for years and it takes about a minute. The difficult bit is that the video plays perfectly on your machine, you send the file feeling pleased with yourself, and the person at the other end sees a grey rectangle with a play button that does nothing.
Having spent years sending decks and proposals into other people's inboxes, I've learned to assume the recipient's setup is nothing like mine, and video in a PDF is where that assumption gets tested hardest.
There are three genuinely different ways to put a video and a document together. They fail in different places, so the right one depends entirely on who is opening it and on what.
Embedding the file properly, which only Acrobat can do
The literal reading of the question is a true embed, and Acrobat Pro is the tool for it. In current Acrobat you go to the All Tools menu, choose View more in the left sidebar, then Add rich media, then Video. You draw a box on the page, point it at your video file, and Acrobat drops a player into the document. Adobe's rich media documentation is the reference for the exact steps, and it's worth reading because the format rules are stricter than people expect.
The format rule that catches everyone: Acrobat wants H.264 video with AAC audio. If your file came out of an older screen recorder as something else, Adobe's guidance is that earlier Acrobat Reader versions could play other formats but only if the viewer had QuickTime or Windows Media Player installed on their machine. Which, in 2026, is not a bet I would take on a prospect's laptop.
Then there's weight. The video is genuinely inside the file now, so a two-page PDF with a three-minute screen recording in it is a large binary attachment wearing a PDF icon. Gmail caps personal attachments at 25MB and plenty of corporate mail servers are tighter, so the thing you built to impress someone can bounce before it reaches them.
The limitation that ends most of these projects is this: Adobe documents the playback in terms of Acrobat and Acrobat Reader, and Chrome's built-in PDF viewer is not Acrobat. Neither is Apple Preview, nor the preview pane in Outlook, nor whatever renders the attachment when someone taps it on their phone in the back of a taxi. Rich media is an Acrobat feature, and most of the world does not open PDFs in Acrobat.
So embedding is the right call in one situation: the recipient opens PDFs in Acrobat on a desktop, and the file has to work offline as one self-contained object. Training material handed out on a locked-down corporate machine, say. Outside that, it's a lot of effort for a grey rectangle.
A still image and a hyperlink, which breaks nowhere
The pragmatic version. Host the video wherever you already host video (YouTube unlisted, Vimeo, Loom, a link from your own storage), drop a still image into the PDF where the video would go, and hyperlink that image to the video URL.
Acrobat will also let you point the rich media tool at a URL rather than a file, over HTTP, HTTPS or RTMP, which sounds like the best of both. In practice it inherits the same Acrobat-only playback problem as the embed, so a plain hyperlink on an image is the more dependable version of the same idea.
This works everywhere, because a hyperlink is the most boringly compatible thing in a PDF, and how to add a hyperlink to a PDF walks through the mechanics.
What you're giving up is the join between the two things. The reader is now in a different tab, watching a video that talks about "page four" while page four is somewhere behind the browser window they just left. Most people watch thirty seconds, close the tab, and go back to skimming the document without the context you recorded.
It is the right answer when the video is supplementary. A product demo attached to a spec sheet, a founder intro on the back of a one-pager. When the video is the explanation and the document is the evidence, the split tab actively hurts.
Stop putting the video in the file at all
The third option is to give up on getting the video inside the PDF and put both behind a single URL instead, so the reader gets the document and the walkthrough in the same view.
This is what I build, so treat me accordingly. Years of sending decks and proposals in growth roles at DataBees and elsewhere taught me that a PDF in an inbox is a static object with nobody standing next to it. You wrote it knowing which two paragraphs actually matter. The reader doesn't, so they skim, and the nuance you spent an afternoon on evaporates.
LiveDocument attaches a recorded video walkthrough to a PDF or an image, shares the pair as one link with no download and no attachment, lets you add clickable highlights that jump the video to the moment you're talking about that section, and reports page-level engagement so you can see how long someone spent on each page and what they went back to.
Being straight about what it is not: it isn't a PDF editor, it doesn't produce a self-contained file that works with no internet, and if you need watermarking or an NDA gate in front of the document then DocSend does that and we don't. If the requirement is genuinely "one file, offline, no link", a true Acrobat embed is your only option and you should accept the constraint that comes with it. Loom is the better tool if what you actually want is just a video with no document attached to it.
How I'd choose
The deciding question is what the video is for. If it's a nice extra sitting next to the real content, a still image and a hyperlink takes five minutes and never breaks, so do that and stop thinking about it. If the video is the explanation and the PDF is the evidence, splitting them across two tabs undoes the reason you recorded it, and one link with both in it is the version that survives.
True embedding is the exception rather than the default. It earns its place when the file has to work offline as a single object and you know for certain the recipient opens PDFs in Acrobat on a desktop. If you go that way, test it on a machine that isn't yours before you send it, because your machine has Acrobat and theirs might not.
The wider version of that argument is in PDF with video sender, and if you want the short factual answer to the literal question, can you add a video to a PDF covers it in about forty seconds.
Frequently asked questions
Does adding video to a PDF make the file too big to email?
Usually, yes, if you embed the video properly. A few minutes of screen recording runs to tens of megabytes, and Gmail's personal attachment ceiling is 25MB with many corporate servers set lower. Linking to a hosted video instead keeps the PDF small.
What video format does Acrobat need?
Adobe's documentation asks for H.264 video with AAC audio. Other formats have historically played in Acrobat Reader only when the viewer had QuickTime or Windows Media Player installed, which is not something you can count on.
Will an embedded video play in a browser or on a phone?
Adobe documents rich media playback for Acrobat and Acrobat Reader. Browser PDF viewers, Apple Preview and mobile mail previews are different renderers, so the safe assumption is that an embedded video will not play there. Test it on a device you don't own before sending anything that matters.
Can I add a video to a PDF for free?
The embed route needs Acrobat Pro, which is paid. Adding a still image and a hyperlink to a hosted video costs nothing beyond whatever you already use to host video. For the hosted-link approach, check pricing.
If you have ever sent a document and then spent two days guessing whether anyone read past the first page, that gap is the thing worth fixing, and it isn't a file format problem. LiveDocument is my attempt at fixing it.
About the Author
Cameron JamesCameron 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.