Long PDFs collect clutter. A report that started as twenty tight pages comes back from a shared drive at thirty-four, with a blank page after every section break, a scanned page that appears twice, and an appendix nobody has read in two years. The document still works, but everyone who opens it pays for the clutter: they scroll past empty pages, wonder whether the duplicate is a different version, and lose track of where the real content ends.

Removing pages is the simplest cure for that kind of clutter, because it is a subtraction, not a rebuild. You name the pages that go, and everything else stays exactly where it was, in the same order, with the same content. That is what Remove Pages does. It drops the pages you specify and keeps the rest. It does not reorder anything, it does not split the file into pieces, and it does not keep only the pages you name — that last job belongs to a different kind of tool, and confusing the two is the easiest way to lose pages you meant to keep.

Where the extra pages come from

Blank pages are the most common culprit, and they usually have an innocent cause. A chapter that ends mid-page in a word processor can push a section break onto a fresh page. A scanned document can include the blank back of a form. A print-to-PDF export can add a trailing page that contains nothing but a footer. None of these is a mistake worth investigating; they are just by-products of how documents are assembled.

Duplicates are sneakier. They happen when a page is scanned twice because the feeder jammed, when two people append the same attachment to a report, or when a revised section is inserted without deleting the old one. A duplicate is worse than a blank page, because a reader cannot tell at a glance whether the second copy is identical or quietly different. If it is identical, it is pure waste. If it differs by a single figure, keeping both is actively misleading, and the right fix is to decide which version is current before you delete anything.

Outdated appendices are the third category. A price list from last year, a terms sheet superseded by a newer one, a draft chapter that was never meant to leave the office — all of them sit at the back of a document long after their useful life ends. Removing them is not destroying information; the original file stays untouched on your own device, and you can always go back to it. What you send onward is simply the version a reader needs now.

A one-pass cleanup routine

Start by reading the document once, end to end, with a pen in hand — or, more realistically, by paging through it and noting page numbers. Write down three lists: blanks, duplicates, and outdated material. Do not delete as you go. The reason is that page numbers shift after every deletion in most editors, and a list made on the fly quickly points at the wrong pages. A single list made against the original numbering is far more reliable.

Next, check the duplicates before you trust them. Open both copies side by side and compare the text that matters: dates, figures, names. If they match, either copy can go. If they differ, stop and decide which one is authoritative — ask the document owner if you are not sure — because deleting the wrong copy is a content decision, not a cleanup task.

Then group your deletions into ranges where you can. Pages 2 and 4 to 6, for example, can be expressed as a single selection rather than five separate deletions, which reduces the chance of a typing slip. But do not force ranges where they do not fit. A scattered list typed carefully beats a tidy range that accidentally swallows a good page.

Finally, keep a copy of the original before you produce the cleaned version. Browser tools leave your original file unchanged on your device — the output is a new file — but the habit still matters. If a reader later asks where an appendix went, you want to be able to answer from the original, not from memory.

Worked example: cleaning a fictional community report

Imagine a fictional neighbourhood association report, prepared by a fictional volunteer named Sam Carter for a fictional group at example.org. The report is 28 pages long, and Sam's page-by-page notes read like this:

  • Page 3: blank, left by a section break.
  • Pages 9 and 10: the same scanned minutes, twice, after a feeder jam.
  • Pages 24 to 28: last year's event calendar, superseded by a new one.
  • Everything else: current and needed.

Sam checks pages 9 and 10 against each other first. Both show the same meeting date, the same attendance list, and the same three action items, so one copy can safely go. Sam decides to remove page 10 and keep page 9, so that the surrounding pages keep their familiar flow.

The removal list is therefore: 3, 10, 24-28. That is seven pages in total, leaving a 21-page document. Sam enters that selection into Remove Pages, downloads the result, and then — this step matters — opens the result and spot-checks the pages either side of each deletion. Page 2 should still flow into the old page 4, now renumbered in the output, and the final page should be the old page 23, the last current page. A two-minute check catches the kind of slip that a page-count alone would miss: the count can be right while the wrong page is missing.

If the same report later needed reordering rather than trimming, that would be a different job. Organize PDF handles reordering visually, and Split PDF cuts a document into parts. Neither is a substitute for a straight deletion, and neither should be reached for when the task is simply "these pages go, the rest stays."

What removal does not do

Removing pages does not compress the file in any meaningful sense, beyond the size of the pages themselves. If the cleaned document is still too large to email, that is a separate problem, and Compress PDF addresses it with its own trade-offs. Removal also does not renumber printed page numbers inside the document body — if the original pages carry printed folios, those numbers will now skip where pages were taken out. For most internal reports that is harmless, but for a formal submission it is worth checking whether the recipient expects continuous printed numbering, and renumbering afterwards if they do. The guide to merging and splitting PDFs covers the neighbouring jobs of joining and dividing documents, which often come up in the same cleanup session.

Honest limitations

Remove Pages refuses to remove every page: at least one page must remain, which is a sensible guard against an empty result, but it also means a document you want to empty entirely needs a different approach. More importantly, removal is permanent in the output file — the deleted pages are not hidden, they are gone from that copy — so work from a list you have checked, and keep the original. Removal also cannot judge whether a page is a true duplicate or a near-duplicate with a changed figure; that judgement is yours, and it should be made before you delete, not discovered afterwards. Finally, if the pages you want to remove are not whole pages — a paragraph on an otherwise good page, a single line in a table — this is the wrong tool entirely. Page removal works at page granularity, and nothing finer.

FAQs

How do I delete specific pages from a PDF?

List the pages by number, using ranges where they run together — for example, 2, 4-6 — enter that selection in Remove Pages, and download the result. Then open the result and check the pages either side of each deletion, rather than trusting the page count alone.

Can I remove a range of pages at once?

Yes. A range such as 4-6 removes those pages together, and you can combine ranges and single pages in one selection. Grouping ranges reduces typing slips, but only use a range where every page in it genuinely needs to go.

Will removing pages affect the remaining pages?

No. The pages you keep stay in their original order with their original content. Printed page numbers inside the document will skip where pages were removed, and the file will be smaller by roughly the size of the removed pages, but nothing else changes.

What happens if I try to remove every page?

The tool refuses: at least one page must remain. If you genuinely need an empty result, that is a sign the task is not a page removal — reconsider what you are trying to produce before proceeding.

human review pending client designation