🖨️ Print Test Page
✅ Test page paradox cluster

Printer prints test page but not documents

🔍
Haven't printed a test page yet? Print one now from FixMyPrinter.org — it confirms within 60 seconds whether the issue is hardware or software. If the test page also comes out blank, the problem is ink or nozzles, not the software layer.
Quick answer
A working test page proves the printer hardware, connection, and basic driver communication are all fine. The test page is generated by the printer's own internal firmware — it never touches the operating system, driver port, or application layer. When the test page prints but documents don't, the failure is happening in the software stack: a corrupted print queue, an app-specific print setting, a document that fails to render, or the wrong printer port in the driver. Start by clearing the queue and printing a plain text file from Notepad — not from Word or a PDF viewer.
The key diagnostic insight
The printer's test page bypasses every software layer — it doesn't use your operating system's print queue, your driver's port settings, or the application sending the job. If the test page prints, all hardware is confirmed working. Everything between your application and the printer's input is the problem space. This narrows the diagnosis significantly: queue → port → driver → application → file.
⚡ Quick checks — the software-layer triage
  • Clear the print queue completely: open Printers & Scanners → click printer → Open print queue → delete all jobs
  • Print a plain text file from Notepad (Windows) or TextEdit (Mac) — type one word and print it. If this works, the problem is the original app or file
  • Confirm the correct printer is set as default: Settings → Printers & Scanners → check which printer shows as default
  • On Windows: Win+R → services.msc → find Print Spooler → right-click → Restart
  • Try printing from a completely different application — if Word fails but Notepad succeeds, the problem is Word's print settings

The software failure layers — in order of likelihood

1. Corrupted print queue (most common)

The Windows Print Spooler queues print jobs as files in a spool folder before sending them to the printer. A corrupted or partially transferred job can block the queue — the Spooler holds a lock on the job file, new jobs queue up behind it, and nothing prints. The Cancel button in the queue window doesn't work because the Spooler is still running. The reliable fix requires stopping the Spooler service, deleting the spool files manually, and restarting. See the full stuck queue guide for the complete steps.

2. App-specific print failure

Word, Adobe Reader, Chrome, and other applications each have their own print rendering path. Word uses the Windows GDI printing system. Adobe Reader uses its own PDF rendering engine. Chrome has its own print compositor. Each of these can fail independently while the printer itself — and even other apps — work fine. If Notepad prints but Word doesn't, the problem is Word's interaction with the driver, not the printer or the driver itself.

This cluster has dedicated guides for each app: Word, PDF/Adobe, browsers.

3. Wrong printer selected or stale printer entry

If a previous printer is still listed as the default — or if a ghost printer entry from a previous installation is capturing jobs — print jobs go to the wrong destination. The job leaves the application successfully but never reaches the correct printer. Check Printers & Scanners and confirm the intended printer is both listed and set as default.

4. Wrong or stale driver port

The driver's port setting tells Windows how to communicate with the printer: USB, network IP, WSD, or a named port. After a Windows Update, a network change, or a USB cable swap, the port can silently change or become stale. The printer's test page still works (it doesn't use the driver's port) but documents fail to deliver. Check the port: Printers & Scanners → click printer → Printer properties → Ports tab — the checked port should match how the printer is connected.

5. Document rendering failure

Some documents appear to print — the job enters the queue, the printer activates — but the rendered output is blank or incomplete. A document with white text on white background, empty PDF layers, or an unsupported embedded font will render to blank print data. The test page never has this issue because it's generated by the printer's own firmware with no third-party content.

Step-by-step fix — software layer triage

  • Open Printers & Scanners → click your printer → Open print queue → delete every pending job
  • Press Win+R → type services.msc → find Print Spooler → right-click → Restart
  • Open Notepad → type any word → Ctrl+P → select your printer → Print
  • If Notepad prints successfully: the problem is the specific application or file you were trying to print — see the app-specific guides in the cluster nav above
  • If Notepad also fails: check the driver port — Printer properties → Ports tab → confirm the correct port is checked. If it shows WSD and you're on USB, that's the problem
  • If the port looks correct but Notepad still fails: download and reinstall the OEM driver from the brand's official support page using your exact model number
  • After reinstalling the driver: print the test page from Windows first (Printer properties → Print Test Page), then try the original document
# PowerShell: stop spooler, clear all spool files, restart
Stop-Service -Name Spooler -Force
Remove-Item "$env:SystemRoot\System32\spool\PRINTERS\*" -Recurse -Force
Start-Service -Name Spooler

Fix by operating system

Windows — test page works but documents don't
  • Win+R → services.msc → Print Spooler → Restart → try printing again immediately
  • Check the default printer: Settings → Bluetooth & devices → Printers & scanners → confirm your printer shows "(Default)"
  • Check "Let Windows manage my default printer" — if enabled on Windows 11, it may have switched to a different printer. Disable it and manually set your printer as default
  • Check the port: right-click printer → Printer properties → Ports tab → the active port should match the connection (USB00X for USB, or the printer's IP for network)
  • If the port is wrong: click Add Port → Standard TCP/IP Port → enter the printer's IP address, or reconnect via USB and run the driver setup again
💡
Windows 11 "Let Windows manage my default printer": This setting automatically changes your default printer to the most recently used one — which may not be your main printer. It's the cause of more "wrong printer selected" issues than any driver problem. Disable it at Settings → Bluetooth & devices → Printers & scanners → scroll down.
macOS — test page works but documents don't
  • System Settings → Printers & Scanners → confirm the correct printer is set as default (Default Printer dropdown at bottom)
  • Open the print queue for the printer → clear any stuck jobs → click Resume if the queue is paused
  • Try printing from TextEdit → Format → Make Plain Text → print one word. If this works, the original app has a rendering issue
  • If TextEdit also fails: remove the printer (minus button) and re-add it, choosing the full manufacturer driver instead of AirPrint
  • If re-adding with the full driver works: the issue was that AirPrint doesn't support the specific feature or document type you were printing

Find the specific app that's failing

If you've confirmed Notepad prints but a specific app doesn't, use the dedicated guides below. Each covers the app's unique rendering path and the specific settings that cause silent print failures.

Microsoft Word / Excel / Office
Test page works but Word document won't print
→
Adobe Reader / PDF files
Test page works but PDF won't print
→
Chrome / Edge / Firefox
Test page works but browser won't print
→
Color documents
Test page works but color documents fail
→
Large files / images
Test page works but large files won't print
→

Official support and drivers

If reinstalling the driver is needed, always download it from the brand's official support page using your exact model number — not through Windows Update.

HP
Canon
Epson
Brother
📝 Word print failure

Test page prints but Word document won't

🔍
This guide is for Microsoft Word and Excel specifically. For PDF-specific failures, see PDF won't print. For all test-page-paradox causes, see the complete guide.
Quick answer
When Word fails to print but the test page and Notepad both succeed, the problem is in Word's own print rendering path or the specific document's content. Word uses the Windows GDI printing system and applies its own page settings, margin definitions, and color modes before sending data to the driver. The fastest diagnostic: open a brand new blank Word document, type one word, and try printing it. If a new document prints but the original doesn't, the original document has a content problem.
⚡ Quick checks
  • Create a new blank Word document → type one word → try printing it. If this works, the original document is the problem
  • In the original document: Select All (Ctrl+A) → change font color to Automatic (black) — white text is the most common hidden cause
  • Check Word's print settings: File → Print → confirm the correct printer is selected in Word's own print dialog (not just the system default)
  • Close and reopen Word completely before printing — a session-level print renderer issue clears on restart
  • Try Save As → PDF → then print that PDF — this tests whether the document content is the issue

Why Word fails when other apps succeed

White text or white content

The most common cause of a Word document printing blank or near-blank is white text on a white background. This usually happens when text was formatted with a white font color — visible on screen if the document uses a colored background, but invisible when printed on white paper. Select All → change font color to Automatic to force all text to the default print color.

Word print renderer crash

Word maintains its own internal print renderer that can enter a failed state during a session. Symptoms: printing appears to work (progress bar shows, job enters queue) but nothing comes out. Closing and reopening Word completely — not just the document — resets the renderer.

Document-level printer settings

Word documents can embed printer settings (paper size, tray selection, printer name) from when the document was originally created. If the original printer no longer exists, Word may silently fail to print rather than falling back to the current default printer. Go to File → Print → confirm the current printer is selected — Word sometimes defaults to an embedded "remembered" printer.

Print background colors and images setting

Word has a setting called "Print background colors and images" that controls whether page background colors and shading are printed. If the document uses a white page background applied as a fill (not the default paper color), this setting interacts with some drivers to produce blank output. Check File → Options → Display → uncheck "Print background colors and images" and try again.

Fix for Word not printing

  • Open a brand new blank Word document → type one word → File → Print → confirm the printer → Print. This isolates whether the problem is Word itself or the original document
  • If the blank document prints: open the original → Select All (Ctrl+A) → Home → Font Color → Automatic. Then try printing
  • If the problem persists: File → Print → check that the printer shown is your actual current printer, not a previous printer or PDF writer
  • File → Options → Display → uncheck "Print background colors and images" → OK → try printing again
  • Try File → Export → Create PDF/XPS → save as PDF → open that PDF and print it. If the PDF prints fine, the issue is Word's direct print path, not the document content
  • If nothing works: close Word → restart → open the document → print immediately without making any changes
💡
Excel printing blank: Excel has its own common blank-print cause — the print area may be set to an empty range. Check Page Layout → Print Area → Clear Print Area, then set it correctly. Also check that the sheet isn't in "Page Break Preview" mode, which sometimes causes confusing print output.
Back to cluster
Test page works but documents don't — all causes
→
Related
Test page works but PDF won't print
→
If queue is stuck
Print job stuck in queue and won't delete
→
📄 PDF print failure

Test page works but PDF won't print

🔍
This guide covers PDF-specific print failures where the test page and other documents print correctly. For Word-specific failures, see Word won't print. For all blank output causes, see printer prints blank pages.
Quick answer
When a PDF fails to print but the test page and plain text files succeed, the issue is in Adobe Reader's rendering engine or the PDF file's structure — not the printer hardware. The fastest fix: in Adobe Reader's Print dialog, click Advanced and check "Print as Image". This bypasses Adobe's rendering engine and rasterizes the PDF, resolving the vast majority of PDF-specific print failures in under 30 seconds.
⚡ Quick checks
  • Adobe Reader: File → Print → Advanced → check "Print as Image" → OK → Print
  • Try opening the same PDF in Chrome, Edge, or Firefox and printing from there — different rendering engine
  • On Windows: right-click the PDF → Open with → Microsoft Edge → print
  • On Mac: open in Preview → File → Print
  • Update Adobe Reader/Acrobat — outdated versions have known print rendering bugs

Why PDFs fail when other documents print fine

Adobe Reader rendering engine failure

Adobe Reader uses its own complex rendering pipeline to translate PDF structure into printer commands. For PDFs with transparency layers, complex vector graphics, embedded subsetted fonts, or unusual color spaces, this rendering can fail silently — the printer receives valid print commands but the content data is blank or corrupted. "Print as Image" completely bypasses this pipeline by converting the PDF to a raster image before sending it to the printer.

PDF color space incompatibility

PDFs created for professional printing often use CMYK color profiles, Lab color spaces, or ICC profiles that differ from the printer driver's expected color space. The driver receives color data it can't interpret and substitutes white or nothing. Using a browser to print (which converts to sRGB automatically) usually bypasses this issue.

Protected or print-restricted PDFs

PDFs can have printing permissions disabled by their creator. Adobe Reader respects these restrictions and may appear to print while sending blank content. The document properties dialog (File → Properties → Security) shows whether printing is permitted. Third-party PDF viewers may ignore these restrictions.

Corrupted PDF file

A partially downloaded or corrupted PDF may display correctly on screen (because the display renderer is more forgiving) but fail when sent to a printer (which requires more complete data). Try re-downloading the PDF from its source, or ask the sender to re-export it.

Fix for PDF not printing

  • Adobe Reader / Acrobat: File → Print → click Advanced (bottom left of dialog) → check "Print as Image" → OK → Print
  • If Print as Image works: the PDF has a rendering issue that Adobe's engine can't handle natively — consider re-exporting the PDF at standard settings
  • If Print as Image doesn't fix it: open the PDF in Google Chrome → File → Print → select your printer → Print
  • On Windows: right-click PDF → Open with → Microsoft Edge → print from Edge's print dialog
  • On Mac: open in Preview → File → Print → confirm printer selection → Print
  • If all viewers produce blank output: the PDF is likely corrupted or heavily restricted — re-download or request a fresh export from the source
  • Update Adobe Reader/Acrobat: Help → Check for Updates — outdated versions have specific known bugs with certain PDF versions
Back to cluster
Test page works but documents don't — all causes
→
Related blank pages
Printer prints blank PDF only — ink and rendering causes
→
🌐 Browser print failure

Test page works but browser won't print

🔍
This covers Chrome, Edge, Firefox, and Safari print failures. For the general test-page-paradox, see all causes.
Quick answer
Browser print failures are almost always caused by the browser's own print compositor failing to communicate with the print driver, or by a browser update changing how it sends jobs to the spooler. The fastest fix: try a different browser. If Chrome fails but Edge works, Chrome's print compositor has an issue with your driver — clear Chrome's print cache and reinstall the printer within Chrome's settings.
⚡ Quick checks
  • Try printing the same page from a different browser — if Edge works but Chrome doesn't, the problem is Chrome-specific
  • In Chrome: Settings → Advanced → Privacy → Clear browsing data → check Cached images and files → Clear data → try printing again
  • Try printing to PDF first (select "Save as PDF" as the printer) — if that works, the issue is driver communication, not the page content
  • Disable browser extensions temporarily — some ad blockers and extensions interfere with the print compositor
  • Use Ctrl+P (not the browser's File menu) — sometimes the keyboard shortcut uses a different print path

Browser-specific fixes

Chrome
  • Chrome Settings → Advanced → System → uncheck "Use hardware acceleration when available" → restart Chrome → try printing
  • Navigate to chrome://settings/printers → remove and re-add your printer in Chrome
  • Right-click the page → Print → in Chrome's print preview, try switching between "More settings → Color" options
  • If Chrome consistently fails: update Chrome (Help → About) or try Canary/Beta to see if it's a version-specific bug
Edge
  • Edge Settings → System and performance → uncheck hardware acceleration → restart → try printing
  • Edge uses Windows' built-in print system more directly than Chrome — if Edge fails, check the Windows Print Spooler (services.msc → Print Spooler → Restart)
Firefox
  • Firefox: File → Print → check that the correct printer is selected in Firefox's own print dialog
  • Firefox Settings → General → scroll to Applications → look for how Firefox handles print jobs
  • Try Help → More troubleshooting info → Refresh Firefox — this resets Firefox's print settings without losing bookmarks
Back to cluster
Test page works but documents don't — all causes
→
OS context
Windows 11 printer troubleshooting
→
🎨 Color print failure

Test page works but color documents fail to print

🔍
This covers color-specific print failures where the B&W test page works but color documents don't. For missing colors in the output, see printer missing one color. For all test-page-paradox causes, see the complete guide.
Quick answer
When the B&W test page prints correctly but color documents fail, the color printing pathway has a different failure from the black pathway. The most common causes: the driver is set to Grayscale or Black-only mode (overriding your document's color content), a color cartridge is at zero so the driver refuses to print in color, or the document uses a color profile the driver can't interpret. Check the driver's color settings first — this resolves the majority of cases.
⚡ Quick checks
  • In the app's print dialog: click Printer Properties → look for Color settings → confirm "Color" is selected, not "Grayscale" or "Black only"
  • Check all ink cartridge levels — a color cartridge at zero may prevent all color printing even if black is full
  • Print the FixMyPrinter color test page to confirm which color channels are actually working
  • Try printing from a different application to rule out an app-level color mode override

Why color documents fail when the test page works

Driver or app forced to Grayscale mode

The printer driver has a Grayscale or Black-only mode that, when enabled, converts all print jobs to black regardless of the document's color content. This can be set at the driver level (affecting all apps) or within a specific application's print settings. A Windows Update or new driver installation sometimes enables this inadvertently. Check both the driver properties AND the application's print dialog — they have independent color settings.

Empty color cartridge blocking color printing

Some printers refuse to print color jobs when any color cartridge is empty — even if you're willing to print without perfect color accuracy. Canon printers are particularly strict about this. Check all cartridge levels from the printer's control panel or its utility software.

Color profile mismatch

Documents created with a specific ICC color profile (common in design, photography, and office environments) may not translate correctly through the driver's color management. The driver receives color data in a format it can't process and either drops the color or produces wrong output. Setting color management to "Printer manages colors" in the print dialog usually resolves this.

Fix for color documents not printing

  • In the app (Word, Acrobat, etc.): File → Print → click Printer Properties → find Color or Quality settings → set to Color (not Grayscale)
  • Check the driver-level color setting: Printers & Scanners → click printer → Printing preferences → Color tab → confirm Color is selected
  • Check all cartridge levels from the printer's control panel — replace any empty color cartridges
  • In the print dialog, look for Color Management options → set to "Printer manages colors"
  • Print the FixMyPrinter color test page — if color channels are missing in the test page output, the problem is ink, not settings
  • If color test page is fine but color documents still fail: the app or document has a color profile issue — try printing to PDF first, then print that PDF
Back to cluster
Test page works but documents don't — all causes
→
Related issue
Printer missing one color — nozzle check guide
→
Diagnose color channels
Print a color test page — see which channels are working
→
📦 Large file print failure

Test page works but large files or images won't print

🔍
This covers print failures specific to large files — high-resolution images, multi-page documents, and complex graphics. For all test-page-paradox causes, see the complete guide.
Quick answer
Large files fail to print when the print job exceeds the printer's available memory or the driver's rendering capacity. The print job enters the queue, the printer activates, then times out or stalls. The fix is either to reduce the file's print resolution, split the document into smaller sections, or send the job in a more compressed format — printing to PDF first and then printing that PDF is often the fastest solution.
⚡ Quick checks
  • Try printing just page 1 — if one page works, the full document's total size is the issue
  • Reduce print quality: in Print dialog → Properties → Quality → switch from High to Standard or Draft
  • Print to PDF first (select "Microsoft Print to PDF" or "Save as PDF") → then print that PDF — compression often makes the file manageable
  • For high-resolution photos: resize the image to 150–300 DPI before printing — most printers can't use more than 300 DPI anyway

Why large files fail when the test page succeeds

Printer memory limits

Printers have onboard memory (RAM) that temporarily stores print jobs before processing them. A small test page requires only a few KB. A high-resolution photo or multi-page document may require 50–500 MB. When the print job exceeds the printer's memory, the printer stalls, timeouts, or resets — often without producing any error message. Consumer inkjet printers typically have 16–64 MB of memory; laser printers range from 32 MB to several GB.

Driver rendering timeout

Before a job reaches the printer, the driver renders it into printer-specific commands. For very large or complex documents, this rendering can take long enough that Windows' print timeout triggers, cancelling the job before it completes. Increasing the print timeout in driver settings or reducing the document complexity resolves this.

Network bandwidth limitation

Wi-Fi printers receiving very large jobs over a slow or congested network may timeout during transfer. A job that works over USB may fail over Wi-Fi simply because the transfer takes too long. Try connecting via USB cable for large jobs if this is a recurring issue.

Fix for large files not printing

  • Reduce quality: Print dialog → Printer Properties → Quality or Resolution → switch to Standard or 300 DPI (most printers can't use more than 300 DPI for standard documents)
  • Print to PDF first: File → Print → select "Microsoft Print to PDF" or "Save as PDF" → open that PDF → print it. PDF compression usually reduces file size dramatically
  • Split the document: print pages 1–10, then 11–20, etc. — sending smaller chunks prevents memory overflow
  • For photos: resize to 150–200 DPI at the actual print size using any image editor before printing. A photo that needs to print at 4×6 inches only needs about 600×900 pixels at 150 DPI
  • Use USB instead of Wi-Fi for large jobs — eliminates network timeout as a variable
  • Increase driver timeout: Printers & Scanners → click printer → Printer properties → Advanced tab → increase "Transmission Retry" from 90 to 300 seconds
Back to cluster
Test page works but documents don't — all causes
→
If job is stuck
Print job stuck in queue and won't delete
→

Related problems

Printer prints blank pages with ink
Nozzle, cartridge, refill, and PDF rendering causes — complete guide.
Print job stuck in queue and won't delete
Stop the Spooler, delete spool files, restart — the reliable queue fix.
Printer driver installed but not printing
Wrong driver, wrong port, or stale device entry — full reinstall guide.
Works on phone but not laptop
Hardware is fine — the laptop has a driver, network, or permission problem.
Windows 11 printer troubleshooting
Spooler commands, driver recovery, and the Windows 11-specific default printer trap.
macOS printer troubleshooting
AirPrint vs full driver, Reset Printing System, and macOS queue management.
Get printer help
1
🖨️