Quick answer
Check that the printer is powered on and error-free, then confirm the USB or network connection, clear the queue, disable Use Printer Offline, and only then move to spooler, IP, and driver checks.
Windows device troubleshooting
"Printer offline" in Windows does not always mean the printer is dead or disconnected. Sometimes the printer is ready, but Windows is holding stuck jobs, talking to the wrong port, or trying the old IP address after the router handed the printer a new one.
Quick answer
Check that the printer is powered on and error-free, then confirm the USB or network connection, clear the queue, disable Use Printer Offline, and only then move to spooler, IP, and driver checks.
Safe order
USB vs network
A USB printer offline error is often about the cable, port, spooler, or driver. A network printer offline error is often about Wi-Fi, Ethernet, IP addressing, or the printer not being on the same network path as the computer.
If the whole network has been acting up, the Wi-Fi Connected But No Internet guide and the Ethernet Connected But No Internet guide are the better places to confirm the PC really has stable local connectivity first.
Queue and settings
An old stuck print job can make the printer appear offline even when the device is available. Open the queue and look for jobs that never cleared, especially after a canceled print or a paper jam. Also check whether Pause Printing or Use Printer Offline was turned on.
These settings sound basic, but they explain a surprising number of "connected but not printing" cases.
Print Spooler
If the queue is stuck and jobs will not clear, restarting the Print Spooler is a reasonable next step. This is especially useful when Windows keeps showing jobs that should be gone already. Just remember that the spooler helps Windows manage print jobs; it will not fix a printer that is actually off the network or sitting at an error screen.
IP changes
One of the most common real-world causes is an IP address change. The printer comes back online after a router reboot, but it gets a new address from DHCP. Windows is still trying to reach the old one, so the printer looks offline even though it is visible on the network. If DNS or local network name resolution has also been unreliable, the DNS Server Not Responding guide may help confirm a broader networking problem.
Drivers
If status reporting, duplex options, trays, or scanning features are acting strangely, the full manufacturer driver or software package can matter. Generic Windows drivers are fine for many simple cases, but they do not always handle device status cleanly. If you need to refresh the driver safely, use the How To Update Drivers Windows 11 guide as your baseline.
Hardware warning
If every computer sees the printer as offline, if the printer keeps dropping from Wi-Fi, or if the printer itself shows hardware errors, stop treating it as a Windows-only issue. At that point the printer hardware, router, access point placement, or Ethernet path is more likely to be the root cause.
A printer can show offline even while powered on if Windows is pointed at the wrong printer port, the print queue is stuck, the network connection changed, Use Printer Offline is enabled, or the printer's IP address changed.
First check whether the printer itself shows any error lights, paper jams, low-ink warnings, or connection warnings. If the printer is not ready locally, Windows cannot bring it online.
Yes. After a router or DHCP restart, a network printer can receive a different IP address, which leaves Windows trying to talk to the old address.
Yes, if the queue is stuck or jobs are not clearing. Restarting the Print Spooler is a sensible middle step after checking the printer, connection, and queue settings.
Yes. A bad or outdated printer driver can cause queue problems, missing status updates, or port confusion, especially after a Windows update or printer replacement.
If the printer drops off the network repeatedly, fails from every computer, or shows its own local error messages, the printer hardware or the network environment is more likely than a Windows-only problem.