Fix a PDF that prints blank pages

Find out which side is broken

Two tests split the problem in half, and each takes under a minute. First, print a different PDF on the same printer. If that page is blank too, stop suspecting your file: the printer, its driver, or the queue is at fault, and the sections below about drivers and the spooler apply to every document you print.

Second, print the problem file to Save as PDF (Windows: Microsoft Print to PDF, macOS: the PDF button in the print dialog) instead of to paper. If the saved copy is blank, the fault sits in the file or in how the viewer renders it, and the file sections below are the ones to read. If the saved copy looks fine, the paper path is the suspect: driver, settings, or hardware.

Try Print as Image first

Adobe's print troubleshooter lists this as the fix for a corrupt or problematic file. In Adobe Reader or Acrobat, open the Print dialog, choose Advanced, tick Print as Image, confirm, and print. Foxit Reader offers the same checkbox under Advanced, and wording varies by app.

It works because it skips the fragile part. Instead of sending fonts, layers, and transparency for the printer to interpret, the reader renders each page into a flat picture and sends that. A damaged font or a transparency effect the driver cannot parse never reaches the printer. The price is a slower job, a much larger spool file, and text that prints slightly softer than vector text, so treat it as both a fix and a diagnosis: if the raster version prints, the font and vector path was the block.

Update the driver and the reader

An obsolete driver misreads what the reader sends it, and an obsolete reader misbuilds what it sends. Both vendor pages checked for this guide name this pair among the top causes. Get the driver from the printer manufacturer's own support page, matched to your exact model and operating system, not from a driver aggregator. Update the PDF reader through its built-in updater (in Adobe software: Help, then Check for updates), then restart the computer and the printer before retrying, since a half-applied driver update prints exactly as badly as the old one.

On macOS, removing the printer from System Settings and adding it again forces a clean driver setup, which clears the same class of fault.

If you print from a browser

A browser prints PDFs with its own built-in renderer, which is weaker than a desktop reader's and fails on files that print fine elsewhere. If the browser's print preview is already blank, the renderer never got the content: download the file and open it in a desktop reader instead of printing from the tab.

Two browser-level steps are worth trying before giving up on the tab. First, use the system print dialog rather than the browser's own preview (in Chrome it sits at the bottom of the preview as Print using system dialog), which hands rendering to the operating system. Second, turn off hardware acceleration in the browser settings, relaunch the browser, and retry: the GPU render path is occasionally implicated in blank rendering, so treat this one as a long shot. If neither helps, printing the downloaded file from a desktop reader is the reliable route, not a workaround.

Adobe Protected Mode on Windows

Adobe Reader runs inside a sandbox called Protected Mode, and on some Windows setups the sandbox blocks the print path while everything else looks normal. Adobe documents print related modes for exactly this area. As a test, open Edit, then Preferences, then Security (Enhanced), untick Enable Protected Mode at startup, restart Reader, and print again. If the pages come out, the sandbox was the cause: turn the mode back on afterwards for everyday reading and switch it off only for printing, rather than leaving the reader unprotected.

When the file itself is damaged

A partly damaged file can display perfectly and still fail at print time, because display and printing walk different code paths through the same content. Damage often arrives during a download, an email transfer, or a save to a flaky drive. Adobe's troubleshooter suggests, among other steps: downloading or copying the file again straight to the hard drive rather than a USB stick or network share, opening it and saving a new copy under a plain name made of letters and numbers, and running a syntax check (in Acrobat: print production tools, then Preflight).

Two checks on this site cover the same ground without changing your file. Print preflight inspects fonts, transparency, page boxes, bleed, resolution and color, and tells you what is risky before you print again. Repair PDF rebuilds a damaged file. And PDF to images works as a raster test from the outside: convert the pages to images and print those. If the images print while the PDF does not, the fonts or vector content were the block, and Print as Image is your permanent answer for this file.

Files built in design tools deserve one extra suspicion. Documents exported from tools like InDesign or Canva can carry unusual fonts or layered effects that a given driver cannot process, so flattening transparency or replacing exotic fonts at export time fixes files that no driver update will ever print.

Clear the queue and the spooler

A stuck print job poisons the ones behind it, and the symptom can be blank pages rather than an honest error. Cancel every pending document in the queue, then restart the print system itself. On Windows that means opening services.msc, restarting the Print Spooler service, and rebooting. On macOS, right-clicking the printer list and resetting the printing system plays the same role. Print one copy of one page before sending the whole document again, so a still-broken setup wastes one sheet instead of fifty.

Check for print restrictions

Some documents arrive with permission settings that limit or silently alter printing. In Adobe software, open File, then Properties, then Security, and look at what printing is allowed to do. If the file forbids it, no setting on your side overrides that: ask the sender for a version with printing allowed.

Hardware comes last

Depleted toner, clogged nozzles, and tired mechanics can also output blank sheets, but they are the least likely cause when the file looks fine on screen, so check them last. Print the printer's own self-test or nozzle-check page from its menu: if that page is blank, the fault is in the machine and no software step will fix it. A USB cable test also settles the network question, since an unstable wireless link can corrupt a job on the way over: if USB prints and wireless does not, the file was never the problem.