Chrome printing failing — the print dialog appears but nothing comes out, the printer isn’t listed, or a specific error appears — is one of those problems where the fix is completely different depending on what’s actually failing. The print dialog in Chrome is distinct from Windows’ print dialog, which adds a layer of complexity. You’ll find the complete rundown in our Google Chrome Errors.
First establish where the failure is. Click print in Chrome → the Chrome print preview appears. Is the printer listed in the Destination dropdown? If the printer appears but the job fails: the problem is between Chrome and the printer. If the printer doesn’t appear in the list: Chrome doesn’t see it at all.
Printer not in Chrome’s list
Chrome gets its printer list from Google Cloud Print (discontinued), Windows’ print system, or directly from the OS printer list. If a printer works in other applications (Notepad, Paint, Microsoft Office) but not in Chrome: Chrome’s connection to the OS printer list is broken.
Navigate to chrome://devices/ in Chrome. The page shows printers Chrome has discovered. If the printer appears here but not in the print dialog: try restarting Chrome (Ctrl+Shift+Q to fully quit, then reopen). If it doesn’t appear on the devices page either: delete the printer from Windows settings and re-add it — Chrome re-discovers printers when they’re freshly added.
The fastest fix: print from System Dialog
Chrome’s native print dialog has its own implementation. When it fails, Windows’ own print dialog usually works. In Chrome’s print dialog: click “More settings” → scroll to the bottom → “Print using system dialog.” This opens the classic Windows print dialog instead of Chrome’s. If this prints successfully: Chrome’s own print implementation has a bug or configuration issue, but you have a working path to print.
Chrome print background and rendering
Pages printing as blank — no content on the printed page — are usually a Chrome background printing or rendering issue. In Chrome’s print dialog: check “Background graphics” under “More settings.” Enable it for pages with heavy CSS styling or dark backgrounds. Also: check the scale — a very low scale (1%) would print content too small to see.
Also try: Ctrl+P → wait for Chrome’s print preview to render → if the preview shows the content correctly but the printed output is blank, the problem is the printer driver accepting the print job but failing to render it. Update the printer driver.
Printer driver and Windows print queue
A stuck print queue causes all subsequent print jobs to fail. Right-click Start → Apps and Features → Advanced startup settings → or: Win + R → services.msc → “Print Spooler” → right-click → Stop. Then navigate to C:WindowsSystem32spoolPRINTERS → delete all files in this folder (leave the folder itself). Return to services.msc → Print Spooler → Start. This clears any stuck jobs that are blocking new ones.
Also update the printer driver: Settings → Bluetooth and devices → Printers and scanners → your printer → Printer preferences → check for an update button. Or the manufacturer’s website for the latest driver — manufacturer drivers are consistently more stable than Windows Update’s generic versions.
Chrome PDF viewer and printing
Chrome has a built-in PDF viewer. Printing PDFs opened in Chrome uses Chrome’s own PDF rendering rather than a dedicated PDF application. Chrome’s PDF renderer occasionally produces incorrect output — missing fonts, wrong colors, blank pages — for complex PDFs.
Alternative: download the PDF → open in Adobe Reader or Microsoft Edge’s PDF viewer → print from there. If it prints correctly from another viewer: Chrome’s PDF rendering has a compatibility issue with that specific PDF. Reporting the issue via Chrome feedback (three-dot → Help → Report an issue) with the PDF attached helps Google fix it. For the immediate problem: use the alternative viewer.
Network printer and Chrome access
Network printers (on a local LAN or corporate network) require Chrome to communicate over the network. When a VPN changes routing, or when the machine moves between networks: Chrome may not be able to reach the network printer even if Windows still shows it as available. Windows caches the printer driver locally and shows the printer as “ready” even when unreachable.
Confirm the printer is reachable: open a Command Prompt → ping [printer-ip-address]. If it times out: the network path to the printer is unavailable. Resolve the network issue (reconnect to the correct network, disconnect VPN if it’s routing traffic away from the local network) and then try printing again.
Chrome extensions interfering with print
Extensions that modify page content — ad blockers in strict mode, page editing extensions, readability modes — can alter the page content that Chrome sends to the printer. An extension removing background elements also removes them from the print output. A content-modifying extension can break the DOM structure that Chrome’s print renderer uses.
Test: Ctrl+Shift+N → open the failing page in Incognito → print. If it prints correctly in Incognito: an extension is affecting the print output. Test extensions one at a time in regular mode to identify the culprit.
Our guide on Chrome performance and rendering covers the hardware acceleration and rendering issues that can also affect print output. For printer-specific issues that affect all applications equally (not just Chrome), our Windows printer diagnostics guide covers the driver reinstall and print queue clearing in depth. Google’s Chrome printing documentation covers the Chromebook printing differences, Chrome’s cloud print architecture, and the specific chrome://devices/ page for diagnosing printer discovery issues.
Printing web pages with complex CSS
Modern web pages use CSS that’s optimised for screens rather than print. Fixed-position elements (sticky headers, floating navigation), absolute positioning, and overflow-hidden containers frequently break when Chrome tries to render them for print — resulting in missing content, overlapping elements, or excessive blank pages.
Check whether the site has a “Print version” or “Printer friendly” link — many news sites and articles provide these. Also try Reader View in Chrome (click the book icon in the address bar if it appears) before printing — Reader View strips navigation and styling, leaving clean article text that prints reliably. For pages without these options: try selecting just the relevant content → right-click → Print (this sends only the selected content to the printer).
Page size and margin conflicts
Chrome’s print dialog allows setting paper size, margins, and orientation. If these settings don’t match the printer’s capabilities — attempting A4 on a US Letter-only printer, zero margins on a printer with physical margin limits — the job may print with cut-off content or fail entirely. Chrome’s print dialog: confirm paper size matches what’s loaded in the printer. Also try “Default” margins rather than custom values — Chrome’s margin calculation for specific printers occasionally miscalculates custom margin values.
Print jobs stuck in queue
A print job that appears to submit but never prints may be stuck in the Windows print queue, waiting behind a failed previous job. Windows Print queue: Settings → Bluetooth and devices → Printers and scanners → your printer → Open print queue. If there are stuck jobs with “Error” status: delete them all. After clearing: retry the Chrome print job. Jobs stuck in error state prevent any new jobs from printing on that printer.
Chrome and HTTPS/HTTP printing
Chrome’s security model treats HTTP and HTTPS pages differently. Some print-related features behave differently on non-secure (HTTP) pages. If printing fails specifically on HTTP sites while HTTPS sites print fine: Chrome may be applying stricter security restrictions to the print request from the insecure page. Checking whether the site has an HTTPS version available and using that for printing resolves this specific case.
Enterprise print management and Chrome
Corporate environments use enterprise print management (Windows Print Server, Papercut, Uniflow) that manages printer access through policy rather than direct connection. Chrome in a managed environment may only see printers approved by the print management system. If personal printers aren’t visible but corporate printers are: print management policy is filtering the printer list, not Chrome.
Managed Chrome (chrome://policy/ shows policies): IT controls which printers Chrome can see and use. Requesting the needed printer be added to the corporate print management system is the correct path, not local Chrome configuration changes.
Chrome profiles and print settings
Chrome print settings (default printer, default paper size, margins preference) are stored per-profile. If printing stopped working after Chrome changed profiles or synced new settings: the stored print settings for the current profile may have an invalid printer stored as the default. In the print dialog: manually select the correct printer in the Destination dropdown rather than relying on the default. Click “Save as default” after selecting to update the stored default for future prints.
Printing from Chrome to PDF when the physical printer fails
A useful workaround when Chrome can’t print to a physical printer but needs to print immediately: Chrome’s built-in “Save as PDF” destination. Print dialog → Destination → “Save as PDF” → Save. This creates a PDF of the page that can then be opened in Adobe Reader or Edge and printed to the physical printer from there. The additional step bypasses Chrome’s direct print pipeline and uses a different rendering path that often succeeds when Chrome’s direct print fails.
Print to XPS document as a diagnostic
In Chrome’s print dialog: select “Microsoft XPS Document Writer” as the destination. This creates an XPS document file rather than sending to a physical printer. If the XPS saves successfully: Chrome’s print pipeline is working — the problem is between Chrome and the specific physical printer. If XPS fails too: Chrome’s core print mechanism has a problem, pointing at hardware acceleration, Chrome profile corruption, or a Chrome bug.
This simple diagnostic separates “Chrome can’t print at all” from “Chrome can’t print to this specific printer” — two different problems with different fixes. The XPS test takes 30 seconds and immediately tells you which category the problem falls into.
Chrome OS-level print permissions
On some system configurations, Chrome’s access to the printing subsystem is restricted by User Account Control or group policy. Test: right-click Chrome’s shortcut → Run as administrator → attempt to print. If printing works as administrator but not as a regular user: there’s a permission issue affecting Chrome’s access to the print subsystem. Checking the printer’s security properties (Settings → Printers → right-click printer → Printer properties → Security tab) confirms whether the current user account has Print permissions. The user account should have at minimum “Print” and “Manage own documents” permissions.
The XPS diagnostic and “Print using system dialog” are the two most efficient troubleshooting shortcuts for Chrome printing problems. XPS tells you whether Chrome’s print pipeline works at all. System dialog tells you whether the printer works when Chrome’s own dialog is bypassed. Together, they immediately narrow the problem to one of three categories: Chrome’s pipeline, Chrome’s dialog, or the printer itself. Most Chrome printing problems can be diagnosed within these three categories in under two minutes.
Printing long documents and memory
Chrome generates the entire print document in memory before sending it to the print queue. Very long web pages (annual reports, comprehensive articles, documents with many high-resolution images) can exhaust Chrome’s memory allocation during print generation, causing the print job to fail or produce incomplete output.
For large documents: try printing in sections (select 10 pages at a time in the page range rather than the full document). Alternatively: Print to PDF first (which Chrome handles as a streaming operation rather than full in-memory generation), then print the PDF in smaller sections from a PDF viewer. This approach handles arbitrarily long documents that Chrome’s direct print fails on due to memory constraints.
When Chrome updates break printing
Chrome updates occasionally introduce regressions in printing — particularly for specific printer models or specific content types. If printing worked fine before a Chrome update and now fails: check the Chrome Help Community or Chromium bug tracker for the specific version alongside the error or symptom. Printing regressions are typically patched within one or two release cycles, and the community documentation often includes the specific settings workaround or the specific version that fixes it.
Downgrading Chrome is not straightforward (no built-in downgrade path), but the workaround of using “Print using system dialog” or printing via Save as PDF → Adobe Reader bridges the gap until the fix arrives in the next Chrome update. Most printing regressions are resolved quickly because they affect a large number of users and are highly visible in Chrome’s feedback system.
For the most stubborn Chrome printing failures: creating a new Chrome profile and testing printing there is a 5-minute test that definitively confirms whether the issue is profile-specific (corrupted print settings, bad extension configuration) or system-level (driver, Windows print queue, network printer unreachable). A fresh profile that prints successfully while the old profile doesn’t means migrating to the new profile — with a Google account, bookmarks, passwords, and extensions all sync back automatically. A fresh profile that also fails to print confirms the problem is below the Chrome profile level and the investigation should focus on the printer driver and Windows print queue instead. Our guide on Chrome Autofill Not Working covers an adjacent issue.
