You double-click the PDF, it opens, and stares back at you with bright white nothing. The thumbnails look empty. The page count is right, but every page is a blank sheet.
Good news: the content is almost always still in the file. The viewer just can't draw it. Let's figure out why.
What's actually going wrong
Most blank PDFs fall into one of four buckets. Broken render layer — a font or image stream is malformed and the viewer skips the whole page rather than drawing partial content. Hidden content — the page has white text on white, or an invisible overlay covering everything. Stripped page tree — a botched save or sync truncated the file so pages exist in the index but point to nothing. Bad scanner output — the originating scanner produced empty image frames.
The fix depends on which one you've got. Open the file in a second viewer first — if it renders there, the file is fine and your viewer is the issue.
The quick fix: re-flatten the file
Run the PDF through a tool that re-renders every page from scratch. Drop it into Flint and use compress PDF — even at the lightest setting, the compressor rebuilds the page stream, which evicts most invisible-overlay and broken-render-layer problems. Save the result, reopen it, and the content usually reappears.
If compression alone doesn't do it, try convert PDF to JPG then convert image to PDF — that rasterises each page and rebuilds the document from the visual output. You lose searchable text, but you recover the visible content.
If that didn't work
Open the original source if you still have it — Word, Pages, the scanner — and re-export. A fresh export from source is faster than forensics on a broken file.
If the original is gone and rebuild didn't help, the page tree is likely truncated. Try splitting the PDF into single pages; the splitter will surface which pages have real content and which are genuinely empty in the file structure. You can then merge the salvageable pages back together.
Prevent it next time
Three habits help. Always export from source to PDF rather than printing-to-PDF when the source app supports it. Don't move PDFs out of cloud sync folders while they're still uploading. And when you receive a PDF that matters, open it once to confirm it renders before filing it away.
FAQ
Why does my PDF look blank in the browser but fine in Acrobat?
Browser viewers (Chrome, Edge, Safari) use lightweight renderers that skip pages with unusual font embedding or unrecognised filters. Acrobat is more forgiving. Re-flattening the file via Flint's compressor makes it render reliably in every viewer.
Can I recover text from a blank-looking PDF?
Often yes. If the text is hidden behind a white overlay, compressing the file in Flint typically strips the overlay. If the text was never embedded (white-on-white from a bad export), only re-exporting from source recovers it cleanly.
Why are only some pages blank?
Per-page blanks point to corrupted streams on those specific pages, not a whole-file problem. Split the PDF, identify the broken pages, regenerate them from source if possible, and merge the document back together.
Is the file corrupted if it shows blank?
Not necessarily. Truly corrupted PDFs fail to open at all. A file that opens to blank pages is structurally valid but has render issues — which is much easier to recover from.
A blank PDF feels terminal but rarely is. Drop the file into Flint, run it through the compressor, and most of the time the content walks back onto the page.