Remove Bookmark Tree

When preparing documents for public release, regulatory filing, or external client delivery, ensuring absolute structural hygiene is paramount. Often, documents authored in word processors or desktop publishing software automatically export chapter outlines that reflect confidential internal project codenames, author initials, or unapproved working titles that should never be visible to external audiences.

Furthermore, after merging multiple disparate PDF files or extracting a small subset of pages, existing bookmarks often become completely broken. A bookmark pointing to page 85 of an original source manual becomes a dead link when that manual is merged into an unrelated 10-page brief. Dead or malfunctioning bookmarks degrade reader trust, disrupt accessibility tools, and project an unprofessional image to clients.

By systematically removing all bookmarks, you present a clean, unencumbered document. For publications where a printed appearance is paramount, stripping the outline tree ensures that readers focus exclusively on the designed page content without distracting, half-functional sidebars.

Under the ISO 32000 specification, a document's bookmark structure is anchored to the root Catalog dictionary through the /Outlines key. This key points to an indirect dictionary object containing /First, /Last, and /Count keys, which in turn reference a cascading network of /OutlineItem objects linked by /Next, /Prev, and /Parent pointers.

To safely and completely remove the bookmarks, a compliant engine must perform two essential structural operations:

First, it must delete the /Outlines key from the document's root Catalog dictionary. Once the catalog reference is severed, conforming PDF viewers will immediately recognize that the document has no outline tree and will disable the bookmarks icon in their user interface.

Second, our engine traverses the document object table to decouple all orphaned outline item dictionaries and destination action objects. During serialization, these disconnected objects are excluded from the newly generated cross-reference table (XRef), permanently purging the outline data from the physical file byte stream and reducing file size.

A critical flaw in poorly designed PDF utilities is that they delete the /Outlines dictionary but leave the document catalog's /PageMode setting configured to '/PageMode /UseOutlines'. When a reader opens a file modified in this careless manner, the PDF viewer dutifully attempts to open the bookmarks sidebar—only to display an unsightly, empty gray panel or throw a non-critical parsing warning.

Our client-side tool specifically inspects the root Catalog dictionary for the /PageMode directive. If it is set to /UseOutlines, our engine automatically resets the key to /UseNone (standard clean view) or preserves user-selected alternatives like /UseThumbs.

This guarantees that the resulting PDF opens seamlessly across all major reading platforms—including Adobe Acrobat, Apple Preview, Google Chrome, Microsoft Edge, and mobile viewer engines—without displaying phantom empty sidebars or confusing navigation panels.

A vital distinction in PDF architecture is the separation between structural outlines (/Outlines) and in-page interactive elements. Removing bookmarks does NOT remove in-text hyperlinks, URL link annotations (/Annots with /Subtype /Link), page numbers, form fields, or visual content streams.

Our tool exclusively targets the catalog-level outline tree. All vector paths, raster images, embedded typography, color profiles, and inline document annotations remain 100% bit-for-bit identical to the original file. You achieve a clean outline removal without risking visual degradation or unintended changes to the printable page content.

Under the Federal Rules of Civil Procedure (Rule 26) and international discovery protocols, attorneys and corporate litigants must strictly sanitize files prior to production. Outlines and bookmark nodes frequently store metadata fragments—such as the Windows username of the drafter, the internal network file share path, and pre-redaction section names—embedded in auxiliary action dictionaries (/A) or named destinations (/Dests).

Simply opening a PDF and deleting bookmarks one by one in commercial desktop tools often leaves ghost objects in the unallocated byte slack space of the file. Opposing forensic examiners can routinely extract these unreferenced strings using basic byte carving tools. Our client-side sanitizer performs full object graph serialization, guaranteeing that unreferenced outline nodes are physically expunged from the output binary.

Removing metadata and bookmarks is frequently a mandatory requirement during legal discovery, corporate mergers, and government redaction workflows. Submitting sensitive legal exhibits, proprietary IP documentation, or personal financial statements to cloud-based PDF conversion portals creates unacceptable compliance vulnerabilities under regulations such as GDPR, HIPAA, and corporate confidentiality covenants.

Because 2run.tools operates entirely within your browser's local JavaScript/WebAssembly runtime, your files are never transmitted across the network. The entire parsing, outline stripping, and serialization pipeline executes directly in your computer's RAM. You can even disconnect your internet connection after loading the page and perform the entire process in total air-gapped isolation.