ON THIS PAGE
You click a blue-looking link in a PDF, but nothing happens. Maybe it works in Acrobat and fails in a browser preview, or it opens on your laptop but not on your phone. A hyperlink in a PDF does not work for one of two broad reasons: the PDF's link annotation or destination is faulty, or the viewer is blocking or ignoring a valid link.
The fastest fix is to diagnose those layers separately. First verify the URL or internal destination, then inspect or recreate the annotation, and finally test the repaired file in another PDF viewer.
Table of Contents
- Why Your Hyperlink in PDF Does Not Work
- The Four Most Common Causes of Broken PDF Links
- How to Verify Link Targets Before You Fix Anything
- Recreating Links and Fixing Destinations in the PDF
- Reader-Side Fixes for Security and Viewer Behavior
- A Reliable Workflow to Bring Dead Links Back to Life
- Frequently Asked Questions About PDF Hyperlinks
Why Your Hyperlink in PDF Does Not Work
A PDF link is more than underlined text. It normally uses a Link annotation, a defined clickable area, and an action that tells the viewer where to go. External web links commonly use a URI action with PDF entries such as /S /URI and /URI, while internal jumps can use a GoTo action or a named destination. A visible URL can therefore look correct while the underlying annotation is missing or malformed. PDF link mechanics are described in this technical overview.
That creates the first diagnostic layer, the document itself. The annotation may point to an outdated web address, a missing page, a renamed bookmark, or a page position that changed after you merged, removed, or reordered content. A PDF created through a print workflow can also flatten interactive elements and strip link annotations. Normal export or conversion settings are more likely to preserve them, as explained in this guide to common PDF link failures.
The second layer is the viewer. A browser preview, mobile reader, or desktop application may block external navigation, handle security prompts differently, or fail to expose annotations after importing the file. In that situation, the PDF can be valid even though clicking appears to do nothing.
Practical rule: Don't rebuild a link until you've confirmed that its destination is correct. Recreating a perfectly valid annotation won't fix an outdated URL or missing internal target.
Start with a short check:
- Try the same file in another reader. If the link works elsewhere, investigate viewer behavior.
- Copy the visible URL into a new browser tab. A dead page and a dead annotation are different problems.
- Test a known-good link in the same file. If every link fails, suspect export or viewer settings.
- Check how the PDF was created. A print-to-PDF workflow deserves immediate suspicion. If the source was a Word file, this Word to PDF conversion guide can help you compare export methods.
The Four Most Common Causes of Broken PDF Links
Most reports that a hyperlink in a PDF does not work fit one of four patterns. Matching the symptom to the cause keeps you from changing settings at random.
1. The destination moved or disappeared
Internal links are especially vulnerable after page editing. A table of contents entry may still point to a named destination that existed before chapters were merged or pages were reordered. The text remains visible, but the target no longer matches the document structure.
A link can also point to a page index that shifted after insertion or deletion. Check the destination panel, bookmark list, or tag structure rather than trusting the page number printed on the page.
2. The URL is malformed or dependent on a file location
External links need a complete, valid destination. Missing or an incorrect path, stray spaces, a dead page, or a relative path can make a link fail. Relative paths are particularly risky because they may work beside the original source files but fail after someone emails or uploads the PDF.
Paste the URL into a fresh browser tab. If it doesn't resolve there, repairing the PDF annotation won't solve the problem.
3. The reader blocks the action
PDF viewers may restrict external links, local file links, JavaScript actions, or navigation from untrusted documents. PDF/A files can also receive special handling for actions such as GoToR, URI, and SubmitForm, which may affect how a reader exposes or activates interactive content. This PDF/A discussion explains the controlled treatment of those actions.
4. The preview or device doesn't honor the annotation
Browser previews and mobile readers don't all interpret PDFs in the same way. Some show selectable text without activating the associated link area. Others intercept the click, display a security warning, or require the file to be downloaded before external navigation works.
| Cause | Symptom | Where to Check |
|---|---|---|
| Broken internal destination | The link stays in the file but jumps nowhere or lands on the wrong page | Bookmarks, named destinations, page order |
| Malformed or outdated URL | The browser shows an error, redirect, or certificate warning | Extracted URL and destination page |
| Viewer security restriction | The link exists but activation is blocked or prompts for trust | Reader security and protected-mode settings |
| Preview or device limitation | The link works in one app but not another | Downloaded file, desktop reader, mobile reader |
Protective settings can also complicate testing. If the file is password protected, first confirm that the security settings allow the actions you need. This password protection guide covers the distinction between securing a document and making it usable for recipients.
How to Verify Link Targets Before You Fix Anything
A dead PDF link can have two separate causes: the document annotation may be wrong, or the viewer may handle a valid annotation differently. Inspect the file before editing so you repair the correct layer.
1. Extract the links into a usable list
Use a PDF link inspector or extractor that exposes each annotation. Review the link type, source page, destination URL, and internal target. Separate external web links from internal jumps, since each requires a different check.
For an external link, confirm that the address is absolute and includes its protocol. Copy it into a fresh browser tab rather than clicking from the PDF. That test distinguishes a dead webpage, redirect, or certificate warning from a problem in the PDF annotation.
2. Check internal destinations against the current file
An internal link should reach the intended page, heading, or bookmark after editing is complete. Open the destination panel or bookmark structure and confirm that the named target still exists. Compare it with the current page order, especially after pages were inserted, removed, or rearranged.
Conversion can also change internal targets. If the file came from an export workflow, this PDF to Word conversion guide explains common conversion pitfalls that can disrupt destinations.
A named destination may fail even when the visible table of contents looks unchanged. Destination names or exported target lists may differ from what a particular reader expects. Adobe community examples show how named destinations can behave differently across software combinations.
3. Record what you find
Create an audit list and mark each link as reachable, redirected, missing, or structurally uncertain. Correct the target before recreating an annotation that points to the wrong location.
For a standards-based check, verify that the link is tagged as a Link annotation, inspect the tag tree, confirm the /Link entry, check exposure through the accessibility API, and tab to the link before pressing Enter. W3C's PDF11 technique documents this validation process.
Recreating Links and Fixing Destinations in the PDF
Once the target is confirmed, rebuild the link inside the PDF. The exact button names vary by editor, but the sequence stays consistent.
1. Open the document in a browser-based editor
Load the PDF in an editor that supports link annotations. Select the link tool, then drag a rectangular hotspot over the intended text or page area. The clickable area should cover the words users will recognize, not an unrelated part of the page.
Paste the confirmed external URL into the action field. For an internal jump, select the current page or named destination that matches the corrected document structure.
2. Update internal targets after page changes
If pages were inserted, removed, or reordered, don't assume the old destination remains valid. Reopen the destination selector and choose the target from the current file. A bookmark that once led to a chapter may now lead to a different page or may no longer exist.
For internal navigation, test both the visible link and the bookmark entry. Those objects can be maintained separately, so fixing one doesn't necessarily repair the other.
A link that reaches the wrong page isn't working correctly, even if the viewer responds to the click.
3. Test before and after saving
Use the editor preview to activate every repaired link. Then download the saved PDF and test the downloaded copy, not only the in-browser editing session. Some workflows preserve the appearance of a link but fail to retain its annotation during export.
If you need to edit a PDF from a Chromebook, use a browser workflow that preserves the original file and lets you download the result for independent testing. This guide to editing PDFs on a Chromebook covers that type of workflow.
For accessible documents, use meaningful link text instead of displaying a long raw URI whenever possible. Screen readers should announce the purpose of the link, and keyboard users should be able to reach it and activate it with Enter.
Reader-Side Fixes for Security and Viewer Behavior
Sometimes the file is sound and the reader is the obstacle. Start by downloading the PDF instead of relying on an embedded browser preview. Open the downloaded copy in a dedicated reader, then test the same link again.
Browser previews in Chrome, Edge, and Safari can handle links differently from desktop PDF applications. A preview may show the document correctly while intercepting external navigation or requiring an extra confirmation. If the link works after download, the preview environment is the likely cause.
Check trust and protected-mode settings
Review the reader's security preferences for external links and document actions. Some applications block navigation from untrusted files or restrict JavaScript-based actions. Don't lower security broadly just to force a click. Instead, use the reader's trusted-document or allowed-action controls when you know the file is safe.
Local file links deserve extra caution. A viewer may intentionally prevent a PDF from opening a file on your device, even when the annotation is valid. Replace that workflow with a reachable web destination when appropriate.
Compare readers and devices
Test the repaired file in a second desktop reader and on a mobile device. A link that works in Acrobat but fails in a browser preview points toward reader behavior. A link that fails everywhere points back to the PDF annotation or destination.
On mobile, long-press the link rather than tapping repeatedly. The menu may reveal whether the reader recognizes a link, offers to open it externally, or treats the content as plain text.
Password restrictions can also prevent editing or interaction. If you're working with a file you own, this PDF unlocking tool can help you remove an existing password before you inspect or repair the document.
A Reliable Workflow to Bring Dead Links Back to Life
Use the same order every time:
- Identify the failure point. Test the PDF in another reader and distinguish an absent annotation from a blocked click.
- Verify URL reachability. Extract each destination, paste external URLs into a browser, and confirm internal targets still exist.
- Recreate or update the annotation. Draw the clickable area again and assign the verified URL or current internal destination.
- Test in the target viewer. Open the downloaded file on desktop and mobile, then check keyboard activation where accessibility matters.
This order prevents wasted edits. It also catches both transport problems, such as an unreachable web address, and structural problems, such as a missing or untagged annotation.
For a browser-based repair, use a free online editor that lets you add or update PDF annotations, download the result, and test it independently. The best workflow is the one that leaves you with a verified file, not just a link that happened to work in an editor preview.
Frequently Asked Questions About PDF Hyperlinks
Why does a link work in Acrobat but fail in a browser preview?
The PDF may contain a valid annotation, while the browser preview blocks or handles it differently. Download the file, open it in a dedicated reader, and check whether the preview has an option to open links externally.
Can screen readers navigate repaired PDF hyperlinks?
They can if the link is exposed as a tagged Link annotation with readable link text. Test the tag tree, accessibility exposure, keyboard focus, and Enter activation. If the PDF was exported without proper structure, recreate the link and export it with tagged document structure.
Why do external and internal links behave differently on mobile?
External links usually hand navigation to a browser, while internal links must resolve a page, bookmark, or named destination inside the PDF. On iOS or Android, long-press each link and confirm that the reader recognizes its action. Test both types after downloading the file because mobile previews can behave differently from stored PDFs.
PDFKing offers free browser-based PDF tools for editing and repairing documents, with no watermark and nothing to install. Visit PDFKing to fix your PDF links online and download a clean, tested file.