PDF Blank Page Remover
Upload a PDF and every page gets checked for real content - text, a drawing, or an embedded image - so any page with nothing on it, including a blank scanned page, gets flagged for removal. Review the list, uncheck anything you'd rather keep, then download the cleaned-up file.
Frequently asked questions
How does this actually detect a blank page?
In three tiers, cheapest and most certain first. A page with real text, or an actual drawn shape/line, is immediately known to not be blank - no further checking needed. A page with no text, no drawing, and no embedded image at all is immediately known to be blank - also no further checking needed. The one genuinely ambiguous case is a page whose only content is an embedded image: that's exactly what a blank scanned page looks like, but it's also exactly what a scanned page full of real content looks like, so only that case gets rendered at a small scale and checked for how much of it is actually close to white.
Why does it need to render some pages instead of just checking for text?
Because a blank page that came from a scanner isn't "empty" in the PDF's own terms - it's a full-page image, the same as a scanned page with real content on it. There's no text layer to check on either kind, so the only reliable way to tell a blank scan apart from a scan with real content is to actually look at the pixels. Rendering is only ever used for that one ambiguous case, not for every page, which keeps it fast on long documents where most pages are decided instantly from their text and drawing content alone.
Will it accidentally remove a page with faint content, like a light watermark or a stray mark?
The pixel check tolerates a small amount of non-white content - about 0.5% of the page - specifically so realistic scanner sensor noise, a faint dust speck, or a barely-visible artifact doesn't stop a genuinely blank page from being recognized as blank. A watermark or header that's actually visible to a reader is generally well above that tolerance and won't be flagged. Either way, nothing is ever removed automatically - every detected page appears in a checklist first, so you can review and uncheck anything before downloading.
What happens with a page that has just a page number or a tiny header?
It's correctly kept. Any real, extractable text at all - even a single page number - is enough for the structural check to immediately classify the page as not blank, without ever rendering it or doing any pixel analysis. Only pages with zero text reach the more careful image-based check.
Can this misidentify a photo that happens to be mostly white, like snow or a blank whiteboard?
Yes, honestly - this is a real limitation of pixel-based detection, not something this tool can fully rule out. A photo that's genuinely dominated by white or near-white content (snow, an overexposed shot, a mostly-empty whiteboard) can register the same way a blank scan does. That's exactly why the results are a reviewable checklist rather than an automatic delete - check the page thumbnails against your own document before downloading if you have any pages like that in it.
Does this work on documents that were never scanned, just created digitally?
Yes. A page intentionally left empty in a digitally-authored document - a chapter-break page meant to be blank in a printed book, for instance - has no text, no drawing, and no image at all, so it's caught immediately by the structural check with no rendering needed, exactly the same as it would be handled in a scanned document.
Is my PDF uploaded to a server?
No. The file is opened, every page is analyzed, and any rendering needed for the pixel check happens entirely in your browser using pdf.js and the Canvas API. Nothing is uploaded anywhere.
Can I choose which blank pages to actually remove?
Yes - every detected blank page appears in a checklist with its page number and the reason it was flagged (completely empty, or a blank scanned page). Every page starts checked (meaning it will be removed), but you can uncheck any of them before downloading if you'd rather keep that specific page in the final file.
Does removing pages affect the rest of the PDF, like bookmarks or forms?
The content of every page you keep is left untouched. What can be affected is anything that specifically pointed at a removed page - a bookmark or internal link that targeted a now-gone page, or a form field that lived on that page, won't have anywhere to point to anymore. For a document where that matters, it's worth a quick check of the result before relying on it, the same as with any tool that deletes pages from a PDF.
How many pages can this handle?
The whole document is scanned in one pass, page by page, so it works the same way on a 5-page document or a 500-page one. Since only the ambiguous image-only pages actually get rendered, a long text-heavy document is checked quickly even though every single page is examined.
Will the pages I keep lose any quality?
No. Removing a page just drops it from the document - the pages that stay keep their exact original content, fonts and embedded images untouched, since nothing about them is re-rendered or re-compressed in the process. Only the rendering used to check the ambiguous image-only pages for blankness is a lossy, low-scale preview used purely for that decision; it's discarded afterward and never becomes part of the downloaded file.