Technically yes — the PDF specification supports embedding video files. In practice, embedded video in PDFs is fragile, poorly supported across viewers, and usually the wrong solution. Understanding what works and what doesn't prevents you from building a PDF that plays video for you but shows nothing to your audience.
What the PDF Spec Actually Supports
PDF 1.5 and later versions allow rich media annotations — video and audio content embedded directly in the file. PDF 2.0 extended this further. In theory, you can embed an MP4 video in a PDF and have it play when a reader clicks a play button on the page.
Adobe Acrobat Pro is the primary tool for embedding video this way, and it works reliably — in Adobe Acrobat Reader. The problem is that most PDF viewers are not Adobe Acrobat Reader, and most don't support embedded rich media. Browser-based viewers (Chrome, Firefox, Edge, Safari's built-in viewer) don't play embedded video. Preview on Mac doesn't support it. Many mobile PDF viewers don't either.
File Size Is the Other Problem
Video files are large. A two-minute HD video might be 100-300MB. Embedding it in a PDF creates a massive file that's slow to open, slow to transfer, and impossible to email. A PDF that was 2MB for the document content becomes 200MB with an embedded video. This limits how it can be shared and strains any system that needs to process it.
The Better Alternative: Video Links Instead of Embedding
Instead of embedding a video file inside the PDF, add a clickable hyperlink or a linked image that opens the video in a browser or video player. The video lives on YouTube, Vimeo, or your hosting platform, and the PDF contains only a link or a thumbnail image that points to it. This works in every PDF viewer, keeps the file size small, and gives viewers the full video platform experience (quality controls, full screen, etc.).
A play-button image overlay on a screenshot of the video thumbnail looks professional and clearly communicates that clicking will play the video. This approach requires internet connectivity at viewing time, but for most use cases that's a reasonable assumption.
When Embedding Makes Sense
There are narrow use cases where embedded video in PDF is the right choice. Kiosk applications running on controlled hardware where only Adobe Reader is installed. Offline presentations where internet connectivity can't be guaranteed. Digital publications where the audience is known to use Adobe Acrobat. Trade show demos on managed devices.
In these controlled environments, you know exactly what viewer will be used and can test that the embedded video works before deployment. The viewer support limitation doesn't apply when you control the display environment.
PDF/A and Video: Incompatible
PDF/A — the archival format — explicitly prohibits embedded video and audio. The archival standard is designed for long-term preservation, and multimedia content that depends on specific codecs or players to render correctly undermines the self-contained nature that makes PDF/A suitable for archiving. If you need to create a PDF/A document, embedded video isn't an option by design.
Interactive PDFs: A Middle Ground
For rich presentations that combine document content with media, interactive PDF tools create documents with clickable hotspots, hover effects, and media links that feel more dynamic than a static PDF. Adobe InDesign's interactive export and tools like Foleon or Visme create HTML-based publications that look like PDFs but aren't — they're web pages that open in a browser and support video natively without any embedding limitations. For client-facing materials where rich media matters, this approach often produces better results than trying to embed video in a traditional PDF Tools workflow.