NearPDF

2026-08-02

Why your scanned PDF has blank pages — and how to actually delete them

Scan a stack of ordinary single-sided paper — an invoice, a signed lease, a set of receipts — and open the resulting PDF, and a lot of people find a document twice as long as it should be, with a blank, all-white page sitting behind every real one. This isn't a broken scanner and it isn't random: it's the direct, well-documented result of scanning single-sided originals in duplex mode, and every major scanner vendor has had to build a feature specifically to deal with it. The trouble is that the feature meant to fix it lives at the wrong stage of the process to help you once the PDF already exists on your drive — which is exactly where a plain, manual delete tool earns its keep.

Why duplex scanning turns one page into two

A duplex scanner captures both sides of every sheet fed through it in a single pass, because that's what "duplex" means — it has no way to know in advance which of your originals are printed on one side only and which are printed on both. Feed it a stack of single-sided pages with duplex mode switched on, and it dutifully scans the back of every sheet too; the back of a single-sided page is, almost by definition, blank paper. Fujitsu's own ScanSnap documentation describes exactly this scenario as the reason its scanners include a dedicated "blank page removal" setting in the first place, built specifically so a mixed batch of single- and double-sided originals, run through the feeder together in duplex mode, comes out without the blank backs. HP's own scan software ships the same idea under a different name — a "Delete blank pages" option inside its Adjust Documents settings, complete with its own sensitivity slider controlling how blank a page has to look before it gets flagged. Two competing scanner vendors independently building near-identical features is a reasonable sign this isn't a rare edge case; it's routine enough that "handle the blank backs left by duplex-scanning single-sided paper" earned a dedicated checkbox in both companies' software.

Why "just turn on auto-remove" doesn't fully solve it

Two problems sit behind that checkbox. First, it has to be switched on and set correctly before you scan — it's a capture-time setting, not something that can reach back into a PDF you already have sitting on disk. If you scanned last month without it enabled, or someone emailed you an already-scanned PDF, there's no "detect blank pages now" button waiting inside the finished file. Second, even when it is switched on, the vendors' own documentation is candid that it gets the call wrong in both directions. Fujitsu's ScanSnap help center has a page titled plainly "Some Pages Are Deleted Even Though They Are Not Blank," which explains: "When the setting is to delete blank pages automatically, the pages which are almost blank may be detected as blank pages and deleted" — a page carrying only a signature, a page number, or a faint letterhead can look "almost blank" to the detector and disappear right along with the genuinely empty ones. The same help center runs a companion page for the opposite failure, "All the Pages Are Recognized as Blank," and separately notes that turning on a "Reduce bleed-through" setting makes false positives more likely, not less. HP maintains its own dedicated support article about scanners failing to detect and delete blank pages correctly. None of this is a knock on either vendor — it's an honest acknowledgment that "is this page blank" is a judgment call a heuristic can get wrong either way, which is exactly why looking at each page yourself before deleting it is the safer default, not a poor substitute for automation.

Why a blank-looking page isn't "empty" to a detector A page built in a PDF editor No text objects on the page No image objects either → genuinely empty; safe to auto-remove A page that came out of a scanner One embedded raster image Image is a photo of blank paper → not "empty"; needs a look, not a guess
A scanned page is always an image, even when the sheet it shows was blank — which is exactly why a blind "remove empty pages" pass can't reliably separate it from a page with faint real content.

Why even Adobe Acrobat doesn't just do this for you

It's worth being honest that this isn't a gap unique to a free browser tool: Acrobat, the dominant paid PDF editor, doesn't ship a one-click "remove blank pages" command either. Acrobat's own user community gives the same answer whenever the question comes up: "Acrobat doesn't have the option to remove blank pages. You can do it manually from Organize pages" — select each blank page and click the trash icon, one at a time. Part of the reason is structural, and it's the same reason illustrated above: a scanned "blank" page isn't an empty page in the PDF sense at all. It's a full-resolution photograph of a blank sheet of paper, no different in kind from a photograph of a page full of text. A tool built to strip pages with literally nothing on them has nothing to grab onto there, because a scan always has something on it — pixels. Reliably telling "a photo of a blank sheet" apart from "a photo of a sheet with faint content" is exactly the judgment call the scanner vendors' own detectors sometimes get wrong; it isn't a solved problem that a PDF editor is simply failing to ship.

How to actually go through and delete them in NearPDF

NearPDF's delete tool is deliberately the plain version of this: no auto-detect, no bulk "select all blanks," no sensitivity slider — because none of those exist in an app that processes files entirely inside your browser with no image-analysis step, and a false-positive delete quietly loses a real page in a way you might not notice until later. What it does have is a fast way to look at every page yourself before deciding: click any page in the workspace grid, or press Enter on it, to open a full-resolution zoom view, arrow through the document page by page, and then click the ✕ button — or just press Delete or Backspace — on any page that turns out to actually be blank. Nothing is selected in bulk and nothing is guessed at; every removal is a page you looked at and a page you chose, the same manual process Acrobat's own support documentation recommends, just without needing a paid license to do it.

Blank pages aren't the only reason to delete a page

The same click-to-review, click-to-delete workflow covers a handful of other page-removal tasks that tend to show up around the same time as a blank-page cleanup: a duplicate page from a sheet that jammed and got re-fed, a scanner-added divider or cover sheet you don't want in the final file, or a page you're intentionally leaving out before sharing a document with someone who shouldn't see it — a personal ID page stapled to a form, for instance. Combine it with NearPDF's rotate tool for any page a scanner captured sideways — covered in detail in this post — and a stack fresh out of a duplex scanner can be cleaned up in one pass through the same workspace, blanks gone and sideways pages fixed, before a single save.

A practical workflow

A realistic sequence, entirely inside NearPDF, with nothing uploaded anywhere: add the scanned file to the workspace, then go through it page by page rather than trusting the page count or a quick thumbnail glance — click or Enter each page to open the zoom view, since a thumbnail small enough to fit a grid can hide the same faint content a "blank" detector sometimes misses. Delete anything that's genuinely empty with the ✕ button, rotate anything the scanner captured sideways, and reorder anything that landed out of sequence — all before you save once. For a long document, that page-by-page pass takes longer than trusting an automatic checkbox, but it's the same trade a paid editor's own users are pointed toward, and it means the file you save is the one you actually looked at, not one an algorithm guessed at on your behalf.

The honest limits, restated

NearPDF's delete tool doesn't scan pixels, doesn't guess at what "blank" means, and doesn't touch a page until you tell it to — it removes exactly the pages you click, one at a time, entirely inside your browser, with nothing uploaded anywhere to look for blanks on someone else's server. If you're scanning regularly and want blanks stripped out automatically before the PDF is even created, that's a setting to look for in your own scanner's software — the same "delete blank pages" checkbox Fujitsu and HP both document — and it's worth giving that automation's own output the same quick page-by-page glance recommended above, since the vendors' own troubleshooting pages describe it getting the call wrong in both directions. For a PDF that already exists, with blank pages already baked in, looking at each page once and clicking the ones that don't belong isn't a workaround NearPDF settles for — it's the same process the industry's own leading paid editor points its users toward too.

Sponsored
← NearPDF

This page shows ads only if you consent.