Why is my PDF blank when I open it but fine for someone else?

That difference points at the viewer rather than the file. The most common version is a dynamic XFA form, which renders normally in Adobe Acrobat or Reader and shows an empty page or a Please wait message in Chrome, Firefox and Safari. A colleague who opens it in Acrobat sees a filled form while you see nothing, and neither of you has a damaged file.

How do I check whether my blank PDF actually contains anything?

Run it through a text extractor and see whether words come back. If the extractor returns the text you expected, the content is inside the file and your viewer is failing to draw it, which is a rendering problem with a different fix. If it returns nothing, the page is either an image with no text layer, or it is empty.

What is an XFA PDF and why does it show Please wait?

XFA stands for XML Forms Architecture, a form format where the PDF describes fields and scripts rather than a fixed page layout. Because there is no drawn page to fall back on, a viewer that does not implement XFA has nothing to display, so the file ships a placeholder page carrying the Please wait text. Adobe's guidance is to download the file and open it in Acrobat or Reader rather than in a browser tab.

My scanned PDF opens blank. Is the scan lost?

Usually not, and it is worth separating two situations. A scan that shows a white page in every viewer is usually a blank sheet that went through the feeder, in which case there is nothing to recover and rescanning is the fix. A scan that shows white in one viewer but has a visible thumbnail elsewhere is a rendering failure, and the page image is still in the file.

Can hidden layers make a PDF look empty?

Yes, and this is common in files exported from CAD and design software. PDFs support optional content groups, which are layers that carry their own visibility state, and a file saved with every layer switched off opens to a white page. Acrobat exposes a layers panel where you can switch them back on; most browser viewers do not, which is why the same file can look empty in one place and complete in another.

Does PDF Mavericks offer OCR for a blank scanned page?

No, and it is better to say so than to send you round a loop. We do not ship OCR yet, so we cannot turn a page image into searchable text for you. If a text extractor returns nothing and you can see the page image, what you need is OCR from a desktop tool, not another browser converter.

Why does my PDF form show blank fields when I print it?

Form field values live in a layer separate from the page content, and some viewers print only the page beneath. The reliable fix is to flatten the form, which merges the entered values into the page itself so they are no longer optional to draw. After flattening the values cannot be edited any more, which is usually what you want for something being submitted or filed.

Is a blank PDF the same as a corrupt PDF?

No, and the distinction saves time. A corrupt file usually refuses to open at all, with an error about a damaged document or a failure to load. A file that opens and shows you a white page has already been parsed successfully by your viewer, which means its structure is intact and the problem is further along in the rendering chain.

Why Is My PDF Blank When I Open It? Six Real Causes

Why is my PDF blank when I open it? Start with the piece of good news buried in the question: the file opened. Your viewer read the header, parsed the structure, worked out how many pages there are and drew a page for you. All of that succeeded. A corrupt PDF does not get that far, it refuses to open and tells you the document is damaged. A white page means the file parsed and something later in the chain produced nothing to look at.

That narrows the problem usefully, because the remaining causes split into two groups with opposite fixes. Either the content is in the file and your viewer will not draw it, or the content is not in the file at all. One test separates them in under a minute, and everything below follows from the answer.

The 60-second test that splits the problem in half

Put the file through a text extractor and see whether words come back. Open PDF to Text, drop the file in, and read what appears.

The tool reads the PDF’s text layer directly rather than looking at the rendered page, which is precisely why it is a useful second opinion on a viewer that shows you nothing. Two outcomes, and they point in different directions:

Words come back. The content is inside the file. Your viewer is failing to draw something it can read. Go to causes 1, 3, 4 and 5.
Nothing comes back. There is no text layer. Either the page is an image, or it is empty. Go to cause 2.

One limit worth knowing before you trust the result: a text extractor reads text, so a perfectly good scan of a printed page returns nothing even though the page is covered in words. An empty result is not proof the page is empty. It means there is nothing machine-readable, which is a narrower and more useful statement.

With that answer in hand, work down this list rather than across it. The order is deliberate: the checks that cost nothing and settle the most cases come first, and nothing modifies your file until step five.

Read what the page actually says. If there is faint text about waiting for a message to be replaced, stop here and go to cause 1. That single sentence identifies the problem outright and saves every other step.
Open the file in a second viewer. Browser tab if you were in a desktop reader, desktop reader if you were in a tab. Ten seconds, and a file that renders in one and not the other is a software problem rather than a damaged document.
Look at the page thumbnail. Content in the thumbnail with a white main view means the page is being drawn somewhere and not everywhere, which points at layers or fonts rather than an empty file.
Run the text test above. Words back means the content is in there. Nothing back means there is no text layer, which sends you to the scan question rather than the rendering question.
Flatten a copy if it is a filled form. Values that show on screen and vanish on print are the classic sign, and flattening is the step that makes them permanent.
Ask the sender to re-export. If the file came from someone else and the causes below do not fit, a fresh export from the source application is faster than any repair. This is especially true for forms and design exports, where the original tool can simply save a flattened or layer-visible version.

Cause 1: a dynamic XFA form your browser cannot draw

This is the cause most people never find, and in India it is the one most likely to be biting you, because a lot of government and tax forms are built this way.

XFA stands for XML Forms Architecture. In an XFA form the PDF does not contain a fixed drawn page at all. It describes fields, properties and scripts, and leaves the rendering to software that understands the format. Adobe Acrobat and Adobe Reader do. Chrome, Firefox and Safari do not, which is why a dynamic XFA document cannot be opened in a browser tab (Adobe community).

Because a blank page would be baffling, XFA files ship a fallback page underneath, and that page carries the message you have probably seen: “Please wait… if this message is not eventually replaced…”. You are not looking at a broken file. You are looking at the placeholder, because the real form was never drawn.

The tell is simple. If a text extractor returns that Please wait sentence and nothing else, you have an XFA form. The fix is to download the file and open it in Adobe Reader on a desktop, which is Adobe’s own recommendation. No browser tool can substitute, ours included, and anyone claiming to convert an XFA form in a browser tab is selling you a flattened shell without the form logic.

Cause 2: an image-only page

If nothing came back from the extractor, the next question is whether there is a picture on the page. Scanned documents contain no text at all, just an image of a page, so a scanner that fed a blank sheet produces a PDF that is correctly and permanently empty.

Check the page thumbnail in your file manager or viewer sidebar. A thumbnail showing content means the image is in the file and something in the main view is failing. A white thumbnail on a scan usually means a blank sheet went through the feeder, and rescanning is the only fix.

We do not ship OCR, so we will not send you round a loop

If the page has a visible image and you need the words out of it, what you need is OCR, and we have not built it. Our /ocr-pdf page says the same thing rather than pretending otherwise. Use a desktop tool for that job.

Cause 3: every layer switched off

PDFs support optional content groups, better known as layers. Each layer carries its own visibility state, saved into the file. A drawing exported from CAD software, or an artwork proof from a design tool, can arrive with every layer set to hidden, and it opens to a white page that is technically rendering exactly as instructed.

A text extractor gives this one away immediately: the words come back even though you can see nothing, because the text is present and merely marked invisible. Acrobat exposes a layers panel where visibility can be switched back on. Most browser viewers do not show one at all, which is why the same file looks empty in a tab and complete on a colleague’s desktop.

Cause 4: form values that were never flattened

Filled-in form values do not live in the page content. They live in field objects layered over it, and drawing them is a separate step some viewers skip, particularly when printing. The result is a form that looks complete on screen and prints with every box empty, or one that looks complete to you and arrives blank at the other end.

Flattening merges those values into the page itself so they stop being optional. Flatten PDF does that in the browser. The trade is permanent: once flattened the fields are no longer editable, which is normally what you want for a form you are filing or emailing, and not what you want for a template you plan to reuse. Keep the editable original and flatten a copy.

Cause 5: one viewer failing where others succeed

Before assuming the file is at fault, open it somewhere else. Drag it into a browser tab if you were using a desktop reader, or into a desktop reader if you were using a tab. This costs ten seconds and settles the question, because a file that renders in one viewer and not another is a software problem by definition.

The usual mechanism is fonts. A PDF can reference a font instead of embedding it, and a viewer that cannot find or substitute it may draw nothing rather than draw the wrong glyphs. Regional-language documents are hit hardest, because the fonts they reference are the least likely to be installed on an arbitrary machine.

Cause 6: locked or structurally damaged

Two smaller cases round out the list, and both have clear signals.

If the file is password-protected, most tools will say so rather than show you a blank page, but not all of them are that clear. Unlock PDF removes the password when you know it, and gives you a file the rest of the chain can read properly.

If the file is structurally damaged in a specific way, its cross-reference table can point at the wrong byte offsets while the page objects underneath are perfectly intact. Repair PDF scans for surviving objects and rebuilds that index. Be clear about the limit, though: rebuilding an index only works when the index is the damaged part. If the content streams themselves are corrupted, or the file has no PDF header at all, in-browser repair cannot recover it and the tool reports that instead of handing you a file that fails later.

Why this runs in your browser

A blank PDF is often something you were already worried about: a bank statement, a filed return, an ID document, a signed contract that has to reach someone today. Uploading it to an anonymous web service to find out why it will not display is a poor trade for a diagnosis.

Every tool linked here runs inside your own browser tab. The file is read by JavaScript on your device, the work happens in local memory, and any result is written straight back to your downloads folder. Nothing is uploaded, so there is no server copy to leak or to forget about. For a file you are only touching because it would not open, that is the right default.