{{ summaryHeading }}
{{ summaryMetric }}
{{ summaryLine }}
Disabled {{ engineBadge }} {{ pageCountLabel }} {{ deleteCountLabel }}
PDF page deletion inputs
{{ message }}
Drop or browse one unencrypted PDF, then choose the page numbers to remove.
{{ sourceTitle }}
{{ sourceHint }}
Ignored {{ ignoredFileCount }} extra file(s). This tool processes one PDF at a time.
Examples: 2, 5-7, 10-, odd, or even. At least one page must remain.
Name the cleaned copy that will be downloaded after local processing.
{{ actionStatusLabel }}
{{ actionHint }}
Field Value Copy
{{ row.field }} {{ row.value }}
Source page Action Output page Page box Note Copy
Load a PDF to build a page deletion map.
{{ row.sourcePage }} {{ row.action }} {{ row.outputPage }} {{ row.pageBox }} {{ row.note }}
Check Status Detail Copy
{{ row.check }} {{ row.status }} {{ row.detail }}
Customize
Advanced
:

Introduction

Deleting pages from a PDF is a document-cleanup step for removing covers, blank scans, duplicate inserts, obsolete attachments, or pages that should not be shared with the final packet. The decision is usually small in count but high in consequence because the output is a rewritten copy with different page positions.

PDF page numbers are easiest to discuss as one-based source pages: page 1 is the first page in the file, page 2 is the next, and ranges such as 5-7 include both ends. That simple numbering can differ from printed labels in the document, such as roman-numeral front matter or exhibit labels, so the source page view should be checked before deletion.

PDF page sequence showing source pages, deleted pages, and renumbered output pages

A page deletion pass should leave a separate cleaned copy rather than becoming the only copy of record. Deleted pages change downstream page references, can invalidate a signed document, and may leave bookmarks, form navigation, named destinations, or tagged PDF reading order in need of review. For accessible or legally sensitive files, the cleaned copy needs visual and structural checking after the pages are removed.

For ordinary packets, the safest habit is to decide both the pages to remove and the pages that must remain. A deletion request that selects every page is not a usable PDF cleanup task. At least one page has to survive so the result can be opened, checked, and sent forward.

Technical Details:

A PDF stores pages as an ordered sequence. Removing pages changes that sequence, then the remaining pages become the output pages in their original order. Source page 4 can become output page 2 after pages 2 and 3 are removed, which is why a keep/delete map is more reliable than a quick mental count.

Range parsing is based on one-based source page numbers. Single numbers, closed ranges, open-ended ranges, odd and even selections, and all-page selections are different ways to build one sorted set of pages to remove. Duplicates do not remove a page twice; the duplicate is reported and the page stays in the deletion set once.

The page-removal pass should remove higher source pages before lower source pages. That avoids index shifting while pages are taken out of the sequence. After removal, the cleaned copy contains only the kept pages, and those pages are numbered from 1 in the new output order.

Supported PDF page deletion range rules
Range entry Selection rule Review point
5 Selects source page 5 only. The page must exist and must be 1 or higher.
5-7 Selects pages 5, 6, and 7. The range is inclusive. The end must be greater than or equal to the start.
10- Selects source page 10 through the final source page. The start page must not be after the last page.
odd or even Selects odd-numbered or even-numbered source pages. Check duplex scans carefully because blank backsheets are often even pages.
all or * Selects every source page. The deletion is blocked because a valid output must keep at least one page.

Validation protects the main failure cases before the output is built. The source has to be a PDF file, the document must load without encryption blocking access, the page count has to stay within the browser-side cap, and the deletion set must leave at least one kept page.

PDF page deletion validation and warning rules
Condition Result Reason
No source file Source required A page count is needed before range entries can be interpreted.
File is not recognized as a PDF Choose a PDF file. The rewrite expects PDF bytes, not an image, document, or archive.
File is larger than 75 MB Blocked before loading Large browser memory rewrites can become unstable.
More than 700 pages Loaded with a blocking warning The document can be inspected, but processing is stopped above the page cap.
Range end is past the last page Clipped to the final source page The warning should be checked because the typed range did not match the file length.
Every page is selected At least one page must remain in the output PDF. A cleaned PDF must contain at least one page.

The page box is recorded for each source page so the deletion map can show width, height, and rotation. That does not prove the cleaned copy preserved every document relationship. PDF bookmarks can jump to destinations, form fields can carry page-based navigation, and tagged PDF structure supports reading order and reuse. A page rewrite can require manual review of those features even when the visible pages look correct.

Page deletion output fields and their meaning
Output field Meaning Use
Deleted pages Sorted, compact list of source pages removed from the copy. Compare against the requested page list before download.
Kept pages Source pages that remain, still in their original order. Confirm that required pages did not get selected by a broad range.
Output page The new one-based position for each kept source page. Use it to update references after the cleaned copy is created.
Page box Source page width, height, and rotation in points. Spot mixed-size or rotated pages that deserve a visual check.
Processing location Browser processing with no upload request from this tool. Use for privacy review when the source file contains sensitive pages.

Everyday Use & Decision Guide:

Start by opening the PDF in a viewer that shows page thumbnails or source page positions, then decide the exact source pages to remove. Use a narrow entry such as 2, 5-7 for known pages. Use odd or even only when the PDF came from a predictable scan pattern and the retained pages are easy to confirm.

The current draft processes one PDF at a time in the browser and keeps the disabled review state visible. The file-size and page-count caps are practical limits, not document-quality scores. A small PDF can still be risky if it is signed, fillable, tagged for accessibility, or full of bookmarks that point to exact pages.

Use the result tabs as a short review route before trusting the cleaned copy.

  • Check Cleaned PDF for Status, Source pages, Deleted pages, Kept pages, Output filename, and Processing location.
  • Open Deletion Map when the range is broad, such as 10-, odd, or even. The map shows every source page as Keep or Delete.
  • Use Readiness Ledger to catch disabled state, missing runtime, source-file issues, deletion-range errors, browser limits, and PDF fidelity risk.
  • Use JSON when another reviewer needs the exact page list, warnings, settings, and readiness details.

A Cleaned PDF generated status means the browser created a new PDF. It does not mean bookmarks, forms, tagged PDF structure, digital signatures, or external references are still suitable. Open the downloaded copy and check the first kept page, the last kept page, at least one page around every deleted range, and any rotated or mixed-size pages.

Step-by-Step Guide:

Use the source file, deletion range, filename, and result tabs as a controlled cleanup path.

  1. Choose Source PDF with Browse PDF or drop one PDF into the file area. The summary should move from Choose a PDF to a selected-page count after the document loads.
  2. Enter Pages to delete with one-based source pages. Supported entries include 2, 5-7, 10-, odd, even, all, and *.
  3. Set Output filename if the default name is not enough. If the field is blank, the output name is based on the source name with a pages-removed suffix.
  4. Read the summary badges and warnings. If the range starts after the final page, counts downward, uses a text token, or selects every page, the action is blocked with a range message.
  5. Click Delete selected pages when the action label says Ready to delete locally. During processing, the button changes to Deleting....
  6. Open Cleaned PDF and confirm Status reads Cleaned PDF generated. Compare Deleted pages and Kept pages with the plan before using Download PDF.
  7. Open Deletion Map and scan the Action, Output page, Page box, and Note columns. If a page is unexpectedly marked Delete, fix Pages to delete and run again.
  8. Use Readiness Ledger to resolve any Blocked, Unavailable, or Review status before relying on the cleaned copy.

The best handoff is a downloaded PDF whose deleted-page list, kept-page list, filename, and map rows match the intended document cleanup.

Interpreting Results:

Deleted pages is the first result to check because it records the exact source pages removed. Kept pages is the countercheck. If either list surprises you, fix the page range before downloading or sharing the output.

Output page in the Deletion Map shows how kept pages are renumbered in the cleaned copy. A dash means the source page was removed. Use that map when page references in email, review notes, exhibits, or bookmarks need to be updated after cleanup.

  • Range needs review means the typed range has an error or would leave no usable PDF.
  • Clipped warnings mean a range extended beyond the document and was shortened to the last source page.
  • Duplicate page ignored means the same source page appeared more than once in the range.
  • PDF fidelity risk means visual pages may be present while signatures, bookmarks, forms, named destinations, or tagged PDF structure still need checking.
  • Output ready means bytes were generated, not that the document is ready for legal, accessibility, or publication use.

Worked Examples:

A 14-page board packet has a duplicate agenda on source page 2 and outdated attachments on pages 11 through 13. Enter 2, 11-13. Deleted pages should read 2, 11-13, Kept pages should list 10 source pages, and Status should change to Cleaned PDF generated after processing.

A duplex scan has blank backsheets on every even source page in an 18-page file. Enter even only after checking that the visible content is on odd pages. The Deletion Map should mark pages 2, 4, 6, and the remaining even pages as Delete, while output pages 1 through 9 come from the odd source pages.

A 9-page form packet needs pages 7 through the end removed. Entering 7-12 produces a warning that the range was clipped to page 9. The expected Deleted pages value is 7-9, and Kept pages should be 1-6. Keep the warning in the review notes because the typed request did not match the file length.

A reviewer types all for a 3-page sample while testing the control. The summary changes to Deletion Needs Review, and the action hint reports that at least one page must remain. The corrective path is to enter a narrower range such as 1-2, confirm Kept pages includes page 3, and run Delete selected pages again.

An encrypted contract PDF fails to load or process because the browser rewrite cannot access its pages. The useful result is the displayed error, not a partial output. Request an unlocked working copy from the document owner, then retry and check Processing location, Deleted pages, and PDF fidelity risk before using the cleaned copy.

FAQ:

Which page numbers should I enter?

Enter source page numbers counted from the first page in the PDF. Printed labels inside the document may differ, so check thumbnails or a PDF viewer page position before entering Pages to delete.

Why is Delete selected pages disabled?

The action needs a loaded PDF, a ready PDF runtime, no more than 700 source pages, at least one page selected for deletion, and at least one kept page. The action hint shows the range or source-file issue to fix.

Can I delete every page?

No. Entries such as all, *, or a range that covers the full document are blocked because the output PDF must keep at least one page.

Does the PDF leave my browser?

The selected PDF is read and rewritten in the browser. The output table reports Processing location as browser-only processing with no upload request from this tool.

What happens to signatures and bookmarks?

Page deletion rewrites the PDF and can invalidate digital signatures. Bookmarks, form links, named destinations, and tagged PDF structure may also need manual review after the cleaned copy is created.

What should I check after download?

Open the cleaned PDF and inspect the first kept page, the last kept page, every range boundary, and any rotated or mixed-size pages. Compare those pages with Deleted pages, Kept pages, and the Deletion Map.

Glossary:

Source page
The original one-based page position in the loaded PDF.
Page range
A typed selection such as 2, 5-7, 10-, odd, or even that identifies source pages to remove.
Output page
The new page position assigned to a kept source page in the cleaned copy.
Page box
The measured page area, shown as width and height in points with rotation when available.
Digital signature
A certificate-backed PDF signature that can show document integrity problems after content changes.
Tagged PDF
A PDF with structural information used for reading order, extraction, reflow, and accessibility support.

References: