Back to all articles
Tech

Understanding PDF Structures: Why Merging and Splitting is Hard

June 25, 2026
7 min read

We use PDF (Portable Document Format) files daily to share documents, invoices, and resumes. Developed by Adobe in 1993, the primary goal of the PDF was to ensure that a document would display identically on any device, regardless of operating system, screen size, or installed fonts.

But while PDFs are easy to read, they are notoriously difficult to edit or modify programmatically. Let's look inside a PDF to understand why.

The Internal Anatomy of a PDF

A PDF is not structured like a clean HTML document or a Word file. It does not contain a flow of text, paragraphs, or tables. Instead, a PDF is a collection of coordinates and rendering instructions.

A typical PDF file consists of four sections:

  1. Header: Identifies the PDF specification version (e.g. %PDF-1.7).
  2. Body: A collection of objects that define the page contents, including text strings, vector graphics, raster images, and font specifications.
  3. Cross-Reference Table: An index that lists the exact byte offset of each object in the body, allowing the reader app to access elements instantly.
  4. Trailer: Points to the main catalog structure and the cross-reference table location.

Why Merging and Splitting PDFs is Complex

Because PDFs are built on absolute page layouts and object coordinate maps, editing them requires parsing and modifying the raw object offsets:

  • Font Conflict Resolution: If you merge two PDFs that use different versions of the same font, the renderer must rename and keep the font resources separate to prevent text rendering errors.
  • Link and Coordinate Updates: Splitting a page out of a document requires extracting the page object, along with all associated image and vector resources, and rebuilding the cross-reference offset table from scratch.

Because programmatically manipulating PDFs is complex, most desktop apps require expensive licenses. We built our Split PDF and Merge PDF utilities to handle these calculations locally in your browser memory, keeping your documents fast, free, and secure.