Delete pages from a PDF — keep only what you need

Step-by-step: delete specific pages from a PDF

The ScoutMyTool tool lives at scoutmytool.com/pdf/delete-pages. Runs client-side via pdf-lib — no upload, no signup, no quota.

1. Drop your PDF. One file at a time. The file loads into a sandboxed memory buffer; nothing is uploaded. Confirm in DevTools Network for sensitive documents.
2. Pick pages by clicking thumbnails OR typing a range. The tool shows a thumbnail for every page. Click a thumbnail to mark it for deletion (it goes red). Or type the range directly into the "Pages to delete" field if you already know which pages to remove — useful when the deletion list comes from a colleague or a checklist.
3. Range syntax cheat-sheet. 3 = page 3. 3-7 = pages 3 through 7. 3, 8, 12-15 = pages 3, 8, 12, 13, 14, 15. 1, 30- = page 1 and everything from page 30 onwards. Same syntax as Extract Pages and Split PDF.
4. Preview what survives. A second panel labelled "Kept pages" shows the pages that will remain, in their new numbering. Use this to sanity-check that you have not accidentally selected the wrong range (e.g. deleted pages 1–5 when you meant 5–1).
5. Click Delete & Download. The tool builds a new PDF whose page tree references only the kept pages and writes it out. The deleted page objects are not included in the output file. Output is delivered as a download.
6. Verify the deletion. Open the output in any PDF reader. Page count should equal (original count − deleted count). The kept pages should appear in the same order they had originally — delete is order-preserving by definition.
7. If pages had digital signatures. Deleting a page invalidates any signature that signed the whole document. Re-sign the trimmed PDF if signed integrity is needed downstream.
8. If the source is password-protected. Unlock first via Unlock PDF.

How ScoutMyTool compares to Smallpdf, iLovePDF and PDF2Go

All four offer some way to delete pages. The meaningful differences are around range-syntax flexibility and whether the file leaves your device.

Delete vs Redact — different tools for different jobs

Delete and redact answer two related-but-different requests. The difference matters when sharing sensitive documents:

• Delete removes whole pages from the document entirely. The output has fewer pages than the input. Use when the page itself should not be in the recipient's copy at all — a previous redline, an internal-only appendix, a draft cover.
• Redact via PDF Redact keeps the page but permanently blacks out specific regions on it (names, account numbers, addresses). The output has the same page count as the input; the redacted regions are replaced with opaque black shapes and the underlying text is removed from the content stream. Use when the recipient should see the page but not the redacted regions.
• Picking the wrong one usually leaks information. Deleting a page when you should have redacted hides metadata that the recipient now cannot see at all (which may itself reveal that something was hidden). Redacting a whole page when you should have deleted produces an obviously-redacted "ghost page" that draws attention to whatever it covered.

The PDF specification (ISO 32000-1) defines both operations structurally; delete operates on the page tree, redact operates on the page content stream¹. The U.S. National Archives PDF redaction guidance explicitly notes that "deletion of pages and redaction of regions are distinct operations and the choice between them is a sensitivity judgement, not a tool limitation"².

Related PDF tools on ScoutMyTool

• Delete Pages — the tool this guide is about.
• Extract Pages — the inverse operation; produces a PDF of only the pages you keep.
• PDF Redact — redact regions within pages instead of deleting whole pages.
• Split PDF — split into separate files along page-range boundaries.
• Reorder PDF — common before delete: shuffle pages so the deletable ones are contiguous.
• Merge PDF — combine PDFs after deletion to assemble a final document.
• Unlock PDF — required first if the source is password-protected.

Frequently asked questions

What's the page-range syntax — can I delete multiple non-contiguous pages in one go?

Yes. The "Pages to delete" field accepts a comma-separated list of single pages and ranges. Examples: "3" deletes only page 3; "3-7" deletes pages 3 through 7 inclusive; "3, 8, 12-15" deletes pages 3, 8, 12, 13, 14, 15; "1, 30-" deletes page 1 and pages 30 through the end. Spaces are ignored. The same syntax is used by Extract Pages and Split PDF, so once you know it, it transfers across the suite. Pages outside any range are kept; the output is a new PDF containing only the kept pages.

Are deleted pages really removed, or just hidden?

Really removed. The tool builds a new PDF whose page tree contains only the kept page objects; the deleted page objects are not referenced anywhere in the output. A determined attacker cannot recover deleted page content from the output file because the bytes that encoded those pages are not present in it. This matters when you are removing a confidential page from a PDF before sharing — "the page is gone from the file" is a stronger guarantee than "the page is hidden from the viewer".

Do bookmarks and the table of contents update automatically?

Bookmarks (the document outline) are kept where they still make sense and dropped where they no longer do. A bookmark whose target page is in the kept set continues to point at the same content; the page-number it displays is recomputed to match the new physical position. A bookmark whose target page is in the deleted set is removed from the outline, since the destination no longer exists. The table of contents drawn into the body of the document (the actual page that lists "Chapter 1 ... 5") is not modified — that is body content, and the tool does not edit body content. Re-export from the source application if you need the TOC body updated.

What happens to form fields, signatures, and annotations on the deleted pages?

They go with the page. Form fields, digital signatures, and annotations are all anchored to specific page objects in the PDF spec. Deleting the page removes its annotations and any form fields exclusive to it. A digital signature that signed the whole document (rather than a specific page) is broken — by design, because the document has changed; a re-sign is required if you need to preserve signed integrity.

Is my PDF uploaded to your servers?

No. The delete-pages operation runs entirely in your browser using pdf-lib. Your file is loaded into a sandboxed memory buffer, the page tree is rewritten to exclude the deleted pages, and a new PDF is serialised and delivered as a download. Verify in DevTools Network — no outbound requests during the operation. Important for documents you need to redact before sharing.

Can I delete by content (e.g. all blank pages) instead of by page number?

Not from the delete-pages tool itself — it works only with explicit page numbers. For automatic blank-page detection, run the PDF through Compress PDF or PDF Editor first (both flag low-ink-coverage pages), then come back to delete-pages with the flagged page list. The two-tool workflow keeps the heuristic ("is this page blank?") separate from the deterministic delete operation, which is easier to audit.

How big can the PDF be?

No hard cap — the operation runs client-side. Memory cost is dominated by holding the source PDF in a JS ArrayBuffer; modern browsers handle PDFs up to several hundred MB without trouble. The delete itself is fast because no page content is re-rendered: the tool just rewrites the page tree (pointers) to exclude the deleted pages. A 1,000-page PDF with 50 pages deleted writes its output in under a second once loaded.