Do your PDF's bookmarks actually work? Find out before you send it.

Drop PDFs below — get the whole bookmark outline listed with title, nesting and the page each entry jumps to, broken destinations flagged, plus a verdict per file. Checked entirely on your device.

  • Your file data never leaves the device
  • Batch up to 20 PDFs + reports
  • Broken destinations flagged
  • Password-protected PDFs refused

Add your PDF files

Drag & drop PDF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Checked in your browser with pdf.js — every bookmark's destination is resolved against the file's own page tree on your device. Nothing is uploaded.

    No files yet. Everything stays on this device. Reports download instantly.

    Privacy you can verify, not just trust

    Most online bookmark tools upload your documents to their servers first — and several are editors that rewrite your file. This one can't: pdf.js opens your PDF and its outline is read entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the check itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Check any PDF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — checking still works.

    How to check the bookmarks in a PDF without uploading it

    A broken bookmark is the quietest way a PDF disappoints: the outline looks complete in the sidebar, the chapter titles are all there, and clicking one does nothing — or lands on the wrong page. It happens whenever pages are deleted, files are merged or split, or a named destination is renamed in one place and not the other. The usual advice is to open the Bookmarks panel and click through every entry by hand, which nobody does for a 300-page manual.

    This tool does exactly that, where the file already is: on your own device. When you drop a PDF here, your browser:

    1. Checks the file is really a PDF — by its %PDF magic bytes, not its name — and that pdf.js can open it, so a corrupt or truncated file is refused with a clear message instead of producing a wrong report. A JPEG renamed to .pdf is refused the same way, and a PDF renamed to .txt still checks.
    2. Reads the outline from the PDF's own objects — including outlines stored in compressed object streams, which most modern producers use — and walks the whole tree: every title, every nesting level, every destination. Each destination is resolved against the file's own page tree, so a jump to a missing page or an undefined named destination is caught, not silently skipped.
    3. Gives each file a verdict — Healthy outline, Mostly healthy, or Risky — with the broken entries named and the page they were supposed to reach, so you know what to fix and where. A downloadable text report per file (or one combined report for the batch) carries the same detail to whoever needs it.

    What makes this checker different

    The pages that top the results for this search mostly list bookmarks, edit them on a server, or need an account — and the free client-side listers we found show the outline with no checking at all: a broken destination looks exactly like a working one. This page is the only free, fully client-side dedicated PDF bookmark checker we found that actually verifies the structure — resolving every destination to a real page, flagging broken jumps, empty and duplicate titles, very deep nesting and count mismatches, across a batch of 20 PDFs, with a verdict per file and a free downloadable report for every file — with no daily limits, no account and no watermark — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.

    When is checking the right choice — and when is it the wrong one?

    Checking is right whenever a PDF has to navigate reliably somewhere else: a book manuscript for KDP or IngramSpark, a manual or report sent to a client, course material for students, or an archived document that people will actually read on screen. It is the wrong choice for a scanned PDF — Scanned PDFs have no outline, so there is nothing to check — and for a file you only ever open yourself, where a broken bookmark never bites anyone else. If the destination accepts the source document, fix the headings there instead of patching the PDF.

    Honest limitations

    Outline only, not full preflight

    This tool reads the outline dictionary — it is not a preflight engine. It cannot judge fonts, colour spaces, image resolution, or any other print condition.

    It does not check headings

    The bookmarks are checked against the file's pages, not against the document's actual headings. A bookmark that jumps to the right page but carries the wrong chapter title will not be flagged.

    Destination zoom is not judged

    A destination also carries a zoom level and a view rectangle. This tool resolves the page and reports it; it does not judge whether the zoom is sensible.

    Titles may render approximately

    Outline titles are PDF text strings. A leading byte-order mark means UTF-16BE; anything else is read as PDFDocEncoding, approximated as Latin-1, so unusual characters may render approximately in the report.

    No password-protected PDFs

    Password-protected PDFs are refused, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then check the unlocked copy.

    It never changes your PDF

    This tool only reports — it cannot add, remove or repair bookmarks. To fix a broken outline, repair the headings or links in the source document and re-export.

    Frequently asked questions

    Do my PDFs upload anywhere?

    No. Your PDFs are opened and their bookmark outline is read entirely in your browser with pdf.js — your file data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the checker.

    How do I check the bookmarks in a PDF?

    Drop the PDF on this page and read the verdict: every bookmark is listed with its title, nesting level and the page it jumps to, and anything broken is flagged — a destination that points at a page that does not exist, a named destination the file does not define, or a bookmark with no destination at all. In Adobe Acrobat the same outline is in the Bookmarks panel; a reader's sidebar shows the same list, but neither tells you which entries are broken.

    What is a broken bookmark destination?

    A bookmark whose jump target does not exist in the file: it points at a page object that is not in the page tree, at a page number beyond the end of the document, or at a named destination that is never defined. The entry still shows in a reader's sidebar, but clicking it does nothing useful. It usually happens when pages are deleted, files are merged or split, or a named destination is renamed in one place and not the other.

    Why does my PDF have no bookmarks at all?

    Because no outline was ever added when the file was made. Scanned PDFs never have one, and quick exports often skip it. Add bookmarks from the headings in the application that made the file — Word has a 'Create bookmarks using headings' option in its PDF export, InDesign has a Bookmarks panel, and LaTeX adds them with the hyperref package — then drop the new file here and check the verdict.

    Are duplicate bookmark titles a problem?

    Not a breakage, but a usability problem: two bookmarks at the same level with the same title cannot be told apart in a reader's sidebar, so a reader may open the wrong chapter. This checker flags duplicates at the same level as a small issue, not a failure. Give each chapter a distinct title — add the part or section number — and the flag goes away.

    What counts as very deep nesting?

    Bookmarks nested more than 6 levels deep are flagged here. Most readers indent each level, so a seventh-level entry is squeezed into a narrow strip and easy to miss, and deep trees usually mean the heading structure in the source document ran away. Flatten anything deeper than a chapter, section and subsection.

    Can I check several PDFs at once?

    Yes. Drop up to 20 PDFs at a time, up to 25 MB each, and check them all in one go. Every file gets its own verdict and bookmark tree, the summary strip totals the batch, and Download all reports collects every file's report into one text file (or a ZIP). There is no daily limit, no account and no watermark — a 200-page cap per PDF applies because very page-heavy PDFs are memory-bound in the browser.

    Can I check a password-protected PDF?

    No. Password-protected PDFs are refused with a clear message, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then check the unlocked copy here.

    What does this tool NOT check?

    It reads the outline dictionary; it is not a full preflight engine. It cannot tell you whether a destination's zoom level or view rectangle is sensible, check the bookmarks against the document's actual headings, or see bookmarks stored anywhere but the standard outline tree. It never changes your PDF — it only reports. For a full preflight, use Acrobat Preflight or a dedicated validator.