How to create a PDF with hyperlinks that still work when it lands

Why PDF links break between your laptop and theirs

The usual version goes like this. The table of contents jumps to the right pages, the case study link opens, the email address starts a new message. You test it, you attach it, and the prospect replies that the links are dead.

Most of the time the link was lost on export, not in transit. A PDF hyperlink is not coloured text. It is a link annotation: a rectangle on the page with a destination attached, which can be another page, a website, another file or an action. The visible words and the clickable rectangle are separate things, so an export can keep every word and quietly drop every rectangle. Adobe's own help for InDesign is blunt about this: links only carry into the exported PDF if the Hyperlinks option is ticked in the export dialog, and links exported from InCopy are not active at all. Printing to PDF, flattening or a heavy compression pass can do the same thing.

The other common failure is a link to a file on your own drive. It works perfectly for you and for nobody else.

Then there is the viewer. Once the file leaves you, it might open in a browser preview, a phone app, a desktop reader or a document panel inside someone's CRM. They all render the page the same and they do not all handle annotations the same.

So my rule is simple: test the exported file, never the source. The export is what your recipient gets. If you protected the file after adding the links, check that too, because permission settings are another place interactivity goes missing. I went through that one in changing a secured PDF.

How to create a PDF with hyperlinks in Acrobat

The mechanics are close to identical in Acrobat Pro and most online PDF editors.

1. Open the final PDF. Not an older export, the version you are actually sending.
2. Pick the link tool. In Acrobat Pro it is Create Link, and you drag a box over the text, button or image that should be clickable.
3. Choose the destination. A page view for an internal jump, a full HTTPS address for a website, or an email action for an address. With email, check the editor created a real mail action and not just blue text.
4. Set the appearance. A visible border helps people spot the link but is not what makes it work.
5. Save as a new copy. Keep the original export untouched so you have something to compare against if a later edit breaks things.

Preview on a Mac is fine for reading and marking up a PDF, but I would not build client-facing links in it. If you want the free routes and their trade-offs, I compared them in adding a link to a PDF for free, and there is a shorter walkthrough in how to add a hyperlink to a PDF.

For a table of contents, aim each internal link at the top of its section. Internal page links have their own failure modes, which I covered in hyperlinking to a page in a PDF. For references, link the exact page the reader needs, not a homepage they then have to search.

The link a screen reader cannot see

This is the bit most people never check. A link can work perfectly with a mouse and be invisible to assistive technology.

In a tagged PDF, W3C's technique for providing links using the Link annotation and the Link structure element explains why: the annotation is tied to a region of the page, not to any text, so on its own it tells a screen reader nothing. The link has to sit inside a Link tag in the document structure, with a reference tying that tag to the annotation and to the text it covers. That is what lets assistive technology announce it as a link with meaningful words.

The practical upshot: create links in the authoring tool before you export, rather than drawing boxes over a finished PDF. A rectangle drawn after export can give you a working mouse target with none of the structure behind it.

In the final file, check:

• Tags. The link shows up as a Link element in the tag tree.
• Wording. The tagged text says where the link goes.
• Reading order. The link appears where a reader would meet it, not tacked on at the end.
• Keyboard. You can tab to it without a mouse.
• More than colour. Underlining or wording backs up the colour, so it is not the only signal.

If accessibility is part of a procurement or compliance requirement, make this a step in your publishing process, and get someone other than the author to do it. The author already knows where every link goes, which makes them the worst person to notice one missing.

A working link solves navigation, not attention

Here is the part that actually bothered me for years. A PDF with hyperlinks that all work still tells you nothing after you hit send. You do not know whether they opened it, reached the pricing page, or clicked the case study you were counting on. So you write the email everyone writes: "Did you get a chance to look at it?"

How you send it should depend on what you need back.

Attach it when the recipient needs a file to keep, the document is short, and engagement is not part of the decision. A signed contract is the obvious case.

Share it as a hosted link when the document is part of a live conversation. A tool with page-level PDF tracking shows which pages were viewed and for how long, instead of a download event and a guess. DocSend does this well and plenty of teams use it.

Treat what you see as a signal, not a verdict. A long stop on the pricing page may mean interest or may mean confusion, and the only way to find out is to ask a better question than "any thoughts?".

Add explanation when the file needs context the page cannot carry on its own. That is what I built LiveDocument for: you record a video walkthrough that sits alongside the PDF, share it as one link, and get page-level analytics and a notification when it is opened. It works with PDFs and images, not Word files or spreadsheets, and it is not a place to store or edit documents, so you still need your editor to make the links in the first place.

Whichever route you take, keep the important context in the document itself. If a pricing assumption matters, say it on the page and link to the detail, rather than hiding the assumption behind the link.

A checklist before you send

• Click every link in the exported file. Internal jumps, web pages and email actions, in a browser and a desktop reader, and on a phone if that is how they will read it.
• Check the tags. Each link is a Link element, with descriptive text, reachable by keyboard.
• Check the boxes. Every hotspot covers its phrase and nothing else.
• Check the destinations. HTTPS, the domain you expect, and the page you meant. Links inside PDFs are a known phishing route, with malicious links sending people to spoofed login pages, so a careful recipient may hover before clicking. Make sure what they see matches what they expect.
• Pick the delivery method on purpose. Attachment if they need to keep it, hosted link if you need to know what happened.

FAQ