Delete PDF Pages

Deleting pages from a PDF is the inverse of extraction: instead of selecting pages to keep, you select pages to remove. Under the hood, both operations construct a new PDF from a subset of the original's pages, but the user intent and interface differ. Understanding the technical process reveals why deletion produces a clean result without leftover artifacts.

The PDF file format does not natively support page deletion as an atomic operation. When a PDF is saved with incremental updates (the standard mode for most editors), "deleted" pages are merely hidden by removing them from the page tree — the actual page objects and their content streams remain in the file as orphaned data. This is why simply opening a PDF in Acrobat, deleting a page, and saving can result in a file that is barely smaller than the original: the bytes are still there, just unreferenced. A full "Save As" (as opposed to "Save") rewrites the file and can reclaim that space, but not all tools offer this distinction.

This tool avoids the orphan problem entirely by constructing a brand-new PDF from scratch. Only the page objects for retained pages are copied to the output, along with their required resources. The resulting file contains no orphaned objects, no incremental update sections, and no residual data from deleted pages. This is particularly important for security-sensitive documents: if you are deleting pages because they contain confidential information, you need assurance that the data is truly absent from the output file, not merely unreferenced.

Resource garbage collection is the process of identifying which objects in the original PDF are still needed after page deletion. A font object referenced by both page 3 (deleted) and page 7 (kept) must be included in the output because page 7 still needs it. An image object referenced only by page 3 can be safely excluded. The tool performs a reachability analysis starting from each retained page's resource dictionary, building a set of all transitively referenced objects. Only objects in this set are copied to the output, ensuring minimal file size.

The document catalog — the root object that defines the document's overall structure — contains references to the page tree, outline tree, names dictionary, AcroForm dictionary, and other document-level constructs. When pages are deleted, catalog entries that reference page-specific objects must be updated. The outline (bookmarks) tree is pruned to remove entries pointing to deleted pages. The AcroForm field list is filtered to exclude form fields whose widgets existed only on deleted pages. Named destinations targeting deleted pages are removed from the names dictionary. The table of contents metadata, if present in XMP, may reference page numbers that are no longer valid after deletion — though this metadata is rarely updated by any tool.

Thread articles — a lesser-known PDF feature that defines reading order across articles spanning multiple pages — are also affected by page deletion. Article threads that reference deleted pages have their bead sequences shortened, and threads whose beads all fall on deleted pages are removed entirely. While article threads are uncommon in modern PDFs, proper handling ensures compatibility with older documents that use this feature for magazine-style layouts.

Removing pages from a PDF is a common need in document preparation workflows:

• Removing blank pages — Duplex scanning frequently produces blank pages between documents. A 50-page scan of single-sided originals on a duplex scanner contains 25 blank pages that add no value and double the page count.
• Cleaning up exports — Software exports (CAD drawings, ERP reports, analytics dashboards) sometimes include cover sheets, disclaimers, or appendices that are irrelevant to the intended recipient. Deleting these pages streamlines the document.
• Redacting entire pages — When an entire page contains confidential information (salary tables, personal data, classified content), deleting the page is simpler and more secure than redacting individual elements. The page data is completely absent from the output file.
• Fixing scanning errors — Batch scanning sessions sometimes capture test pages, repeated scans, or pages from the wrong document. Deleting these erroneous pages cleans up the final PDF without requiring a rescan.
• Meeting preparation — Removing outdated or irrelevant slides from a PDF presentation deck before distributing it to meeting attendees ensures participants focus on current, relevant content.
• Submission compliance — Government forms, grant applications, and academic submissions often have strict page limits. Deleting supplementary pages that exceed the limit ensures the submission meets requirements without reformatting the entire document.

Processing files locally in your browser is essential when deleting pages that contain sensitive content. Cloud-based tools require uploading the full document — including the pages you want removed — to their servers. Even after processing, copies may persist in server logs, backup systems, or CDN caches. This tool guarantees that confidential content on deleted pages never leaves your device.