Embed files into PDF: how it works and its limits

A PDF can carry other files inside it. A spreadsheet, a Word document, a zip, an image, a video. You attach them, save the PDF, and they travel with it as one file. That's what people mean when they search to embed files into a PDF, and yes, it's a real feature of the format.

The catch is on the receiving end. Embedded files sit in a corner most readers never open, so the thing you tucked inside is often the thing nobody finds. I've done this myself and then wondered why a proposal's pricing sheet never got a reply.

There are two different things people call embedding

It's worth separating them, because the tools and the failure modes differ.

The first is an attachment. The file is packed inside the PDF and listed in an attachments panel, or pinned to the page as a small paperclip or pushpin icon. Click it and the reader can open or save the file. The PDF itself looks exactly the same as before.

The second is rich media, where the file is meant to play or display inside the page. That's how video and audio get into a PDF. It's a much more fragile thing, and I've covered it separately in how to get a video into a PDF file and adding video to a PDF. This post is about the first kind: bundling files of any type into the document.

How to attach a file to a PDF

The exact menu names move around between versions, so I won't pretend there's one click path. The shape is the same in most PDF editors that support it.

Open the PDF in an editor, find the attach or add file option, and pick the file. You usually get a choice between two placements:

A page-level icon. The file is pinned to a spot on a page, so you can put it next to the paragraph that refers to it.
A document-level attachment. The file goes into the attachments list for the whole document, with no mark on any page.

If you'd rather not touch an editor, some command-line and scripting libraries can do the same job, which is how invoices get a machine-readable data file packed inside them automatically. That's the one genuinely good use of this feature I've seen in the wild, and it works because the reader is software, not a person.

Then save, and check the file size. Everything you embedded is now part of the PDF, so the PDF grows by roughly the size of whatever went in.

Embedded files make the PDF heavy

This is the first thing that bites. Embed three attachments and you haven't made one tidy file, you've made one big one. Email providers cap attachment sizes, and the cap applies to the whole PDF, embedded contents included. Mine bounced more than once before I stopped doing this. If that's your problem, what to do when a file is too big to upload is the practical way out.

Heavy PDFs also open slowly on phones, which is where a lot of PDFs get opened first.

Most readers never open the attachments

This is the real problem, and no setting fixes it.

A PDF reader shows you pages. The attachments panel is a side tab you have to go looking for, and nothing on the page tells the reader it exists unless you pinned an icon. Some viewers handle attachments well. Others, particularly the quick previews built into mail apps and phones, may not show them at all. I can't give you a clean list of which, and I'd distrust anyone who claims one, so the safe assumption is that your recipient won't see them.

Then there's trust. An embedded file is an executable-shaped surprise. Security tools and cautious people treat PDFs with attached files as suspicious, and some mail filters flag them. Sending a client a PDF with a zip hidden inside it is a good way to have it quarantined.

So embedding is a reasonable choice when the reader is software, or when the recipient is someone who knows exactly where to look. For a person you're trying to persuade, it's a bad bet.

When embedding is actually the right call

I'd use it in three situations and no others.

The files must stay together offline. An archive, a compliance pack, anything that gets stored and opened years later with no link to rot.
A machine reads it. Structured invoice data riding inside the human-readable PDF.
You control the recipient's setup. Internal teams on the same software who've been told where the attachments live.

If none of those is you, skip it.

What to do instead

Work out what the extra files are for. They're usually one of two things.

They're supporting material: a spreadsheet behind the numbers, the source files, a few images. Put them in their own place and give people a link, or name them in the body of the PDF. A line that says "the model is linked here" does more than a paperclip nobody sees. If you're sending several files, the best way to send multiple files via email goes through the options, and sharing the PDF as a link keeps the file itself out of the inbox.

They're explanation: a video, a voice note, a walkthrough of what the document means. This is where hiding things inside the file hurts most, because the explanation is the part you most want seen. That's the problem I built LiveDocument for. You attach a recorded video walkthrough to a PDF or an image, and share both as one link. There's no download and no attachment, so nothing to bounce or miss. You can add clickable highlights that jump the video to the right moment, and page-level engagement shows you where people spent their time.

To be straight about the limits, it's not a way to bundle arbitrary files. It attaches a video to a PDF or an image, and that's all. If what you need is a spreadsheet and a zip riding inside one self-contained file, a PDF attachment is the right tool and LiveDocument isn't. Pricing is on the pricing page.

Frequently asked questions

Can you embed any type of file in a PDF?

In principle, yes. The format treats attachments as generic files, so a spreadsheet, image, document or archive can all go in. What varies is whether your software lets you add them and whether the reader's software lets them open them.

How do I embed a file in a PDF without Adobe?

Plenty of PDF editors and some scripting libraries can attach files. Look for an attach or add file option, or the equivalent in a library's documentation. The result is a standard PDF attachment, so it doesn't depend on which tool made it.

Will the recipient be able to see embedded files?

Not reliably. Some desktop viewers list attachments in a side panel, but many people never open it, and quick previews on phones and in mail apps may not show them at all. If it matters that they see the file, say so in the email or on the page.

Is embedding files into a PDF the same as adding a video?

No. A file attachment is stored inside the PDF for the reader to open or save. A video embedded as rich media is meant to play on the page, and that only works in some viewers. Adding a video to a PDF compares the options.

Put the explanation where people will see it

Hidden files are fine for archives and software. For people, I'd rather put the context in front of them. If you want a quick feel for what that looks like, the demo shows it, and I built LiveDocument because I was tired of sending things into the void.