If it opens correctly in a desktop reader, the file is fine and the browser viewer hit something it cannot draw. The usual culprits are XFA forms, unusual transparency and very complex vector artwork.
If it is blank everywhere, the download was incomplete or the file is damaged, which is a different problem with a different fix.
The first useful step is deciding which of those two you have, and it is quick: download the file and open it in a proper reader. Everything after that follows from the answer.
Browsers have their own engines
Chrome and Edge use one PDF engine, Firefox uses another written in JavaScript, and Safari uses Apple's system renderer. None of them is Acrobat, and none implements the full specification, which is enormous and full of features almost nobody uses.
Edge is the exception: Microsoft moved its built-in viewer to Adobe's PDF engine, so a file that fails in Chrome can still open in Edge.
Browser viewers are built for the common case: view a document, print it, fill in a simple form. They handle that extremely well and quickly run out of road on anything unusual.
- XFA formsPlaceholder page only
- Document-level JavaScriptMostly ignored
- Unusual transparency groupsCan render blank
- Very complex vector artMay time out
- Embedded multimediaNot played
- Some optional content layersMay stay hidden
Narrowing it down
Download and open in a desktop reader
This single test splits the problem in two. Correct there means the browser viewer is the issue. Blank there too means the file is.
Try a different browser
Chrome and Firefox use different engines with different gaps. A document that is blank in one and fine in the other confirms a viewer limitation rather than a file problem.
Check the file size against the source
A truncated download is a common cause of pages that are blank in every reader. If the file is noticeably smaller than advertised, download it again before investigating anything else.
Incomplete downloads
A PDF keeps its index of objects at the end of the file. A download that stops early therefore loses the map to everything, and readers either show nothing or attempt a reconstruction that partially works.
This is worth checking early because it is common and trivially fixed. Interrupted connections, a tab closed too soon, or a server that ended the response early all produce it, and downloading again usually resolves it.
When the browser is the problem
If the file opens correctly elsewhere, you have already solved it practically: use the desktop reader. A few browser-side things are still worth trying if you need it to work in the browser.
Extensions are a frequent cause. Ad blockers, privacy tools and PDF-related add-ons all interfere with the built-in viewer, and testing in a private window with extensions disabled isolates that quickly. Beyond that, browsers cache PDFs aggressively, so a hard reload sometimes clears a viewer that failed on a partial copy.
Convenience
- Opens instantly with no download
- Fine for ordinary documents
- Limited feature support
- Fails silently rather than reporting
Completeness
- Implements far more of the specification
- Handles XFA forms and document scripts
- Reports errors rather than hiding them
- Requires downloading the file first
When the file itself is damaged
If every reader shows a blank document and the download is complete, the file has structural problems. Repair tools rebuild the object index from whatever valid objects they can find; Repair PDF rebuilds the header, cross-reference table and catalog in the browser, which often recovers a working document.
Success depends on how much survived. A file missing only its index usually recovers completely, since the content is all still there. A file with damage running through the page objects themselves may recover partially or not at all, and what repair can and cannot recover sets out where that line falls.
Repair a PDF that will not render
Rebuilds the structure the viewer choked on, in your browser with nothing uploaded.
Common questions
Working out which side the problem is on.
01Why is my PDF blank in Chrome but fine in Acrobat?
Chrome's built-in viewer is a different implementation that does not support everything Acrobat does. XFA forms, unusual transparency and very complex vector artwork can all render as nothing, and the viewer does not report a problem when it gives up.
02What is an XFA form?
An Adobe format that stores the real document inside an XML payload rather than in the PDF page layer. ISO dropped it from the PDF 2.0 standard, but tax, immigration and bank forms still use it. Chrome and Safari show only the placeholder page, which is often a message asking you to open the file in Acrobat; Firefox renders many of them, and Acrobat and Reader are built to open them.
03How do I tell whether the file or the browser is at fault?
Download it and open it in a desktop reader. If it displays correctly there, the browser viewer is the limitation. If it is blank there too, the file is incomplete or damaged.
04Why would a downloaded PDF be blank?
Most often an incomplete download. A PDF stores its index of objects at the end of the file, so a transfer that stops early loses the map to all the content. Compare the file size against the source and download it again.
05Can browser extensions cause this?
Yes. Ad blockers, privacy extensions and PDF add-ons all interfere with built-in viewers. Opening the file in a private window with extensions disabled is a quick way to rule it in or out.
06The first pages show but later ones are blank. What does that mean?
Usually a truncated file that a reader has partially reconstructed. It recovered the objects that arrived and has nothing for the rest. Downloading a fresh copy normally fixes it.