Why Does My PDF Open but Show Blank White Pages?
Your PDF opens fine, but the pages are blank white instead of showing text. Here's why that happens and how to get the content visible again, without uploading anything.
This one is different from a PDF that refuses to open. Here, the file opens without complaint. The viewer loads, the page count is correct, you can scroll through it — and every single page is a blank white rectangle. No error message, no warning, just nothing where the content should be. It’s an odd kind of broken, because everything about the file looks fine except the one thing you actually wanted to see.
Why this happens
A PDF page isn’t really “text on paper.” It’s a set of drawing instructions, and those instructions depend on resources bundled inside the file, mainly fonts. When the instructions or the resources they point to are missing or malformed, the viewer has nothing to draw, so it renders an empty page instead of guessing.
A few common causes:
Missing or broken embedded fonts. Most PDFs carry their own copies of the fonts they use, so the text looks identical on any device. If that embedding gets corrupted, say during a bad export, a rushed compression pass, or a buggy PDF generator, the viewer can’t find the glyphs it needs to draw and leaves the page empty rather than substituting something wrong-looking. You can read more about how this bundling works on our embedded fonts glossary entry.
A scanned document with no image layer rendering. Scanned PDFs are usually just a photo of each page. If the scan produced a page object without a properly linked image, or the image data got stripped out somewhere along the way (a lossy conversion, a bad OCR pass), you’re left with a page that has structure but no picture.
Content in the wrong layer. Some PDF tools separate what’s visible from what’s selectable. If a document has a searchable text layer sitting behind a scanned image, and the image layer fails to render, you can end up with a page that’s technically not empty, its text layer is right there if you try to select all, but visually looks blank because the thing meant to be on top never drew.
A viewer that’s struggling with a specific PDF feature. Occasionally the file is fine, but the particular viewer you’re using stumbles on an unusual color space, transparency group, or layer setup. Opening the same file in a different reader can rule this out fast.
How to check what’s actually happening
Before assuming the worst, try a quick diagnostic: select the blank page with Ctrl+A (or Cmd+A) and see if text highlights even though nothing is visible. If it does, there’s a working text layer under a broken rendering, which is a much easier problem than a truly empty page.
If nothing selects and nothing highlights, the page genuinely has no visible content baked in, which usually points to the fonts or image data being the casualty.
How to fix it
If the file is a scan and the text layer looks intact but the image doesn’t render, running it through OCR again can rebuild a clean, working version: it reads what’s actually on the page and produces a fresh searchable layer over a properly embedded image, which tends to fix rendering glitches from the original scan along the way.
If you mainly need the words rather than the visual layout, you can sidestep the blank-page problem entirely by pulling the content straight out with extract text. Since this reads the underlying text objects rather than rendering the page, it often works even when the visual layer is broken, so you get your content back even if the page itself refuses to look normal.
If you have access to the original source document (the Word file, the design file, whatever produced the PDF), re-exporting from there is usually faster and cleaner than trying to repair the broken copy. PDF generation bugs are common enough that a second export often just works.
Doing this without handing your document to a stranger
A blank-page PDF is often something you’d rather not upload to a random “fix my PDF” website, an invoice, a contract, a form with someone’s details on it. The whole point of running OCR or extracting text is to recover the content, not to send it somewhere else in the process.
Every tool on files.co runs inside your browser using WebAssembly. Your file is read into memory on your own device, processed there, and handed back to you. It never crosses the network, which you can confirm yourself by opening your browser’s DevTools, watching the network panel, and running the tool. So if a page insists on staying blank, you can dig into why without worrying about where the file ends up in the meantime.