When this tool is useful
Cleaning routine scanner batches that contain obvious empty separator or back-side pages when a person can compare the downloaded result with the unchanged source before using it.
How local processing works
PDF.js renders each page to a bounded internal analysis canvas and measures how much differs from near-white. The workbench lists the candidate page numbers; no PDF is generated until the user checks specific candidates. The processor detects again and removes only confirmed pages that still match.
How to use it
- Prepare Remove likely blank PDF pages: Work from a copy and confirm analysis scale, near-white and ink thresholds, faint content, scanner dust or shadows, candidate page numbers, explicit per-page confirmation, no-empty-output protection, and physical order in the downloaded result. Keep every source unchanged.
- Run Remove likely blank PDF pages: Process only in this browser. PDF.js renders each page to a bounded internal analysis canvas and measures how much differs from near-white. The workbench lists the candidate page numbers; no PDF is generated until the user checks specific candidates. The processor detects again and removes only confirmed pages that still match.
- Download and verify: Save under a new name. Compare the downloaded PDF page by page with the unchanged source at high zoom, verify every gap is an actually blank source page, search for faint expected content, and keep the original because a removed page cannot be recovered from the output.
Important limitations
Blank detection is a visual heuristic, not certainty. Faint pencil, pale watermarks, tiny marks, transparency, unusual backgrounds, or render differences can cause false removal candidates, while dust, shadows, crop marks, and noise can keep an otherwise blank page.
Verify the downloaded result
Compare the downloaded PDF page by page with the unchanged source at high zoom, verify every gap is an actually blank source page, search for faint expected content, and keep the original because a removed page cannot be recovered from the output.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
When is Remove likely blank PDF pages useful?
Cleaning routine scanner batches that contain obvious empty separator or back-side pages when a person can compare the downloaded result with the unchanged source before using it.
How does Remove likely blank PDF pages work?
PDF.js renders each page to a bounded internal analysis canvas and measures how much differs from near-white. The workbench lists the candidate page numbers; no PDF is generated until the user checks specific candidates. The processor detects again and removes only confirmed pages that still match.
Which limits require attention?
analysis scale, near-white and ink thresholds, faint content, scanner dust or shadows, candidate page numbers, explicit per-page confirmation, no-empty-output protection, and physical order in the downloaded result. Blank detection is a visual heuristic, not certainty. Faint pencil, pale watermarks, tiny marks, transparency, unusual backgrounds, or render differences can cause false removal candidates, while dust, shadows, crop marks, and noise can keep an otherwise blank page.
How should I verify the result?
Compare the downloaded PDF page by page with the unchanged source at high zoom, verify every gap is an actually blank source page, search for faint expected content, and keep the original because a removed page cannot be recovered from the output.