A printer showing as connected — Wi-Fi lit, USB seated, status reading "online" or "ready" — but still producing no printed page is its own distinct problem, separate from a printer that's genuinely offline or unresponsive. It means the connection itself is fine, but something between the queue and the print head isn't finishing the job. This guide covers what's actually happening when this occurs, how it differs from similar-sounding statuses, and the exact steps to get pages coming out again on Windows, Mac, network, and USB-connected printers.
These three statuses look similar but point to different underlying problems, and correctly identifying which one you're actually seeing saves significant troubleshooting time. "Connected" simply means the operating system can see the printer and it's reachable over Wi-Fi or USB — nothing more. "Printing" means a job has been accepted and the printer is actively producing output. "Queued" means a job has been accepted but is sitting waiting, whether because of a stuck earlier job, the wrong default printer, or the print head not yet engaging — which is the specific state behind most connected-but-not-printing cases.
Fig. 1 — Each status describes a different stage of the printing process, which is why "connected" alone tells you nothing about whether a job will actually print.
Because the connection itself is confirmed working in these cases, the causes cluster around whatever happens after the job leaves the computer — the queue and driver, the printer's own settings, or occasionally the printer's internal state.
Fig. 2 — Most connected-but-not-printing cases trace back to the queue/driver layer, a setting on the computer side, or the printer's own internal state.
A previous job that failed to fully clear can sit at the front of the queue, silently blocking every job sent after it from ever reaching the printer.
Jobs can be sending successfully to a printer other than the one you're looking at, especially on setups with more than one installed printer or driver.
This Windows setting can be toggled on unintentionally, causing the computer to hold every job locally instead of sending it, even while the printer itself is fully connected.
The background service responsible for managing print jobs can freeze silently, leaving jobs sitting in the queue with no error shown at all.
A driver that's partially corrupted or mismatched to the printer's current firmware can accept a job without ever properly relaying it for printing.
A printer can be manually or accidentally paused from within its settings menu, which accepts new jobs into the queue without ever releasing them to print.
Some printers silently hold a job rather than surfacing a clear low-supply or empty-tray error, which looks identical to a stuck queue from the computer's side.
Reinstalling a printer without fully removing an older entry can leave a conflicting duplicate that intercepts jobs without properly relaying them to the actual device.
Some printers take longer than expected to fully wake from a deep power-saving state, causing the first job after idle time to sit queued rather than print immediately.
On shared or managed computers, a permissions setting can allow a printer to appear connected while quietly blocking a specific user or job type from printing.
An update can reset a driver association, re-enable an offline toggle, or restart print-related services mid-update, leaving jobs stuck in the queue afterward.
A connected printer that won't print on Windows most often traces back to a stuck job in the queue, "Use Printer Offline" being enabled, or the Print Spooler service hanging. Clearing the queue, disabling the offline toggle, and restarting the spooler through Services.msc resolves the large majority of Windows-specific cases.
On Mac, this typically points to a paused queue in Printers & Scanners, or the underlying CUPS printing system holding a stuck job. Resuming the queue if paused, or removing the printer entirely and re-adding it, resets this more reliably than waiting for it to clear on its own.
When every indicator suggests the printer is properly connected — Wi-Fi signal lit, USB cable seated, printer display showing ready — but jobs still won't print, the fault sits specifically in the queue, driver, or a setting rather than the connection itself. On network printers, this often shows up as one device on the network printing fine while another can't, which points to a setting or driver issue specific to the affected computer. On USB printers, it more often traces back to a stuck queue or the offline toggle on that single connected machine, since there's no shared network to isolate the problem to.
A printer that stops printing specifically after a computer restart, Windows update, or driver update usually means one of those events reset the default printer, re-enabled the offline toggle, or restarted a print-related service mid-process. Reinstalling the printer driver fresh, rather than assuming the existing installation survived the update intact, is the most direct fix for this specific pattern.
Connected but not printing means the printer accepts the connection and often the job itself, but never produces output, while not responding means no acknowledgment came back for the command at all — the fault usually sits further along in the queue or settings rather than the communication layer itself.
This most often traces back to a stuck job blocking the queue, the "Use Printer Offline" setting being enabled, or the Print Spooler service hanging; clearing the queue and restarting the spooler resolves the large majority of cases.
This typically points to a paused print queue in System Settings, or the underlying CUPS printing system holding a stuck job; resuming the queue or re-adding the printer resets the connection reliably.
An online, ready status only confirms the connection is working — the actual block usually sits in the queue, the default printer setting, or a driver that's accepting jobs without properly relaying them.
Updates can reset the default printer, re-enable the offline toggle, or restart print-related services mid-process; reinstalling the printer driver fresh usually resolves this specific pattern.
Yes — a job that failed to fully clear can sit at the front of the queue and silently block every job sent after it from ever reaching the printer.
This points to a setting or driver issue specific to the affected computer — a stuck queue, wrong default printer, or corrupted driver — rather than a problem with the printer or network as a whole.
Yes — some printers silently hold a job rather than surfacing a clear low-supply error, which looks identical to a stuck queue from the computer's side.
This Windows setting tells the computer to hold jobs locally rather than send them to the printer; it can be enabled accidentally and is worth checking any time a connected printer won't take a job.
Checking and clearing the queue is quicker and resolves many cases on its own; a full driver reinstall is worth doing next if the issue persists or recurs regularly.
Some printers take longer than expected to fully wake from a deep sleep or power-saving state, which can make the first job after idle time sit in the queue briefly before it starts.
If the queue is clear, the correct printer is set as default, the driver is freshly reinstalled, supplies are confirmed adequate, and the printer still won't produce output consistently across more than one computer, an internal hardware or firmware fault becomes more likely.
Still not printing? Check the related guides above for offline status, slow printing, or connection issues.
A printer that's connected but not printing is communicating something specific — the connection is fine, but a job isn't clearing the queue or reaching the print head — which almost always points to a stuck queue, a settings issue, or the driver rather than a genuinely broken connection. Clearing the queue, confirming the right default printer, disabling any offline toggle, and restarting the spooler and printer itself resolves the overwhelming majority of cases, whether it's happening on Windows, Mac, over Wi-Fi, or by USB. If a printer still won't print across multiple computers after all of this, that's the point to start considering an internal hardware fault.