PDF

PDF Won't Print Correctly or Shows Errors When Printing

A PDF that displays correctly on screen but fails when you try to print is a different problem class from one that won’t open. The file is structurally fine; something in the print path — the printer driver, font handling, transparency rendering, or a specific page’s content — is failing during translation. Most cases resolve with one of three workarounds, in order of increasing intervention.

Quick fix

The single highest-success workaround for PDFs that won’t print correctly: print as image. This rasterizes each page before sending it to the printer, bypassing the font, transparency, and complex content stream handling that’s usually the failure point.

  1. Open the PDF in Adobe Acrobat or Acrobat Reader.
  2. File → Print, or Ctrl+P (Cmd+P on macOS).
  3. Click “Advanced” in the print dialog.
  4. Check “Print As Image”.
  5. Print.

The output is rasterized — text won’t be selectable on the printed page, file spool size will be larger, and printing may be slower — but it succeeds where the standard print path fails. For one-off documents this is the right answer; for regular print workflows the cost adds up and you’ll want to fix the underlying problem.

If you don’t have Acrobat, most PDF readers have an equivalent option. Foxit calls it “Print as image” in the print dialog. Chrome doesn’t expose it directly, but printing through Chrome often works without needing it.

If that didn’t work

If even Print As Image fails, the issue is at the operating system print system level rather than in the PDF rendering. Try these in order.

Update your printer driver. PDF printing problems specifically often resolve with a driver update — vendors release driver patches for compatibility issues. Get the current driver from the printer manufacturer’s site, not from the OS update mechanism.

Print through a different reader. Chrome’s print path uses its own rendering pipeline rather than relying on Adobe’s. Open the PDF in Chrome, print from there. Firefox is similarly self-contained. The success rates of different readers on print problems vary by file; if Acrobat fails, Chrome often succeeds.

Print to PDF first, then print the new PDF. This creates a clean intermediate file that strips out problematic constructs:

  1. Open the PDF in any reader.
  2. Print → choose “Microsoft Print to PDF” (Windows) or “Save as PDF” (macOS) as the destination.
  3. Open the resulting PDF.
  4. Print that file to your physical printer.

The intermediate Print to PDF step rebuilds the document with the operating system’s PDF generator, which often produces a more compatible file than the original. Transparency gets flattened, fonts get baked in, and complex constructs are simplified.

If the problem affects only specific pages, isolate which ones. Print page-by-page or in small ranges to identify the failing page. Once you know which page fails, you can extract the working pages, print them, and handle the failing page separately — print it as image individually, or recreate it from the source if available.

Advanced recovery

For files that resist all of the above, restructure the PDF before printing. Use qpdf to rebuild the file structure:

qpdf --linearize input.pdf clean.pdf

This rewrites the PDF with a clean cross-reference table and standard structure. Files that have accumulated damage from repeated edits, or that were generated by libraries producing technically-valid but unusual structures, often print correctly after this rebuild even when the original doesn’t. See the complete guide to qpdf for what --linearize actually does.

If qpdf rebuilding doesn’t help and Print As Image also fails, re-render the entire file through Ghostscript:

gs -sDEVICE=pdfwrite -dPDFSETTINGS=/printer -o output.pdf input.pdf

/printer settings produce a print-optimized output. Ghostscript re-rendering is destructive in the same way for all files: form fields, annotations, signatures, and tagged accessibility content are commonly lost. For print-only purposes this is usually acceptable.

Adobe Acrobat’s Protected Mode (sometimes called Protected View) can interfere with printing in some configurations, particularly on Windows with certain print drivers. It’s at Edit → Preferences → Security (Enhanced) → “Enable Protected Mode at startup”. Disabling it removes a security boundary that catches malicious PDFs from running scripts; only do this for trusted files, and re-enable when you’re done.

Why this happens

The print path for a PDF is more complex than the screen rendering path. When you display a PDF on screen, the reader’s rendering engine handles everything: it interprets the content stream, looks up fonts, decodes images, composites transparency, and produces pixels for the display. When you print, all of that has to be translated into something the printer driver can handle, then translated again by the driver into something the printer can actually do.

Printer drivers handle PDFs in two main ways. PostScript drivers translate the PDF into PostScript and send that to the printer; PCL and XPS drivers rasterize the PDF on the host computer and send raster data. Each path has its own failure modes.

PostScript drivers struggle most with transparency. The PDF specification allows arbitrary transparency effects (alpha blending, knockout groups, complex masks), but the original PostScript language doesn’t have native transparency primitives. The driver has to flatten transparent content — pre-compositing transparent areas into solid pixels before printing. Flattening is computationally expensive and error-prone. Failures here produce blank pages, missing graphics, or misregistered output.

PCL and XPS drivers avoid the transparency problem by rasterizing on the host, but they have their own issues: very large rasters can exhaust memory, color management can produce unexpected output, and they’re slower for text-heavy documents than PostScript would be.

Font handling adds another layer of failure. PDFs reference fonts by name; the reader has to either use the embedded font or substitute one. When the printer driver gets the data, font substitution may happen again — the printer might have its own fonts that the driver prefers to use over downloading the document’s fonts. Mismatches at this layer produce wrong-font output, missing text, or missing characters.

Print As Image bypasses all of this by rendering the page on the host as a single bitmap and sending that bitmap to the printer. The printer never sees the PDF’s content streams, fonts, or transparency. The cost — larger spool, slower print, no text-on-paper for searchable archive systems — is sometimes worth paying for the reliability gain.

Preventing this in future

When you generate PDFs that you’ll need to print reliably, flatten transparency at export time. Most design tools have a “high resolution” or “print ready” flattening preset that pre-composites transparent areas. Adobe products call this “Transparency Flattener Presets”; Affinity tools and others have equivalent settings.

Embed all fonts in PDFs intended for print. Font substitution at print time is a major source of font-on-paper problems; full embedding eliminates the variable.

For documents that absolutely must print correctly across many printers — invoices, legal documents, contracts — export as PDF/X (the print-production PDF subset) rather than standard PDF. PDF/X requires font embedding, prohibits transparency that hasn’t been flattened, and constrains color spaces. The result is bigger and more rigid, but vastly more printable.

Keep printer drivers current. Manufacturers release driver updates that fix specific PDF rendering bugs; check the manufacturer’s site once or twice a year for printers you depend on.

If the file also fails to open or displays incorrectly on screen, the underlying problem is broader than the print path — see PDFs that won’t open and the PDF repair complete guide. When the print failure specifically involves wrong fonts or substituted fonts on the printed output, the diagnosis path overlaps with PDF fonts missing or display incorrectly.

Last verified: April 2026