A Wi-Fi printer can show Ready but refuse to print because of a stuck queue, wrong printer entry, stale IP address, driver problem, offline mode, sleep state or blocked network path.
Start by proving whether the issue affects one app, one device, one printer path or the whole network. That comparison tells you whether to fix the app, the device, the router settings or the provider-side connection.
Start with the real scope of the problem
A printer that says Ready but will not print is especially frustrating because the status sounds final. Ready should mean ready. In practice, it may only mean the printer itself has no paper jam, door error or obvious hardware alert. The computer may still be sending jobs to an old printer entry, a stale IP address, a paused queue or a driver that no longer knows how to reach the printer over Wi-Fi. The printer can also scan or print its own status page while refusing jobs from Windows, macOS or a phone.
The fix order is simple: clear the queue, make sure you are using the correct printer entry, restart the printer and computer, confirm the printer's current IP address, then reinstall the driver only if the path is still broken. Do not buy ink, reset the router or remove every printer entry until the queue and address are checked.
Quick diagnosis table
Try these fixes in order
Use these steps in order. They move from the easiest proof to the deeper settings, so you do not erase useful setup before you know what failed.
- 01
Clear stuck print jobs
Open the print queue and cancel old jobs. One stuck job can block every new job behind it while the printer continues to say Ready.
- 02
Choose the correct printer entry
Windows and macOS may show several versions of the same printer. Pick the current network printer, not an old USB, offline or duplicate entry.
- 03
Restart printer and computer
Restart the computer first, then the printer. This refreshes the queue, spooler and printer network session without changing Wi-Fi settings.
- 04
Print a network status page
Use the printer menu to print network details. Compare the IP address with the one saved on the computer.
- 05
Remove and re-add the printer
If the saved entry points to an old address, remove it and add the printer again. This is cleaner than stacking duplicates.
- 06
Update or reinstall the driver
Use the printer maker's official driver or app. Drivers matter when basic discovery works but real print jobs never leave the computer.
- 07
Check offline and paused modes
Make sure the printer is not paused or set to Use Printer Offline. These settings can survive restarts.
- 08
Test USB or Ethernet if available
A cable test can prove whether the printer engine works. If it prints by cable but not Wi-Fi, the network path is the issue.
Detailed checks
Ready is a printer-side word
Ready often means the printer has no local error. It does not guarantee the computer is sending jobs to the right network address.
- That is why queue and printer-entry checks come before router resets.
Duplicate entries cause quiet confusion
A printer can appear several times after driver installs, router changes or Windows updates. One entry may be current while another points nowhere.
- Remove stale entries so future prints go to the right path.
Scanning and printing can fail differently
Scanning may work through one app while printing fails through a driver or queue. That does not mean the printer is lying.
- Treat scan success as proof of partial connectivity, then inspect the print queue and driver.
The repeat pattern matters
If the printer works after re-adding but fails every few days, the IP address may be changing or the printer may sleep too deeply.
- A DHCP reservation and firmware update can make the fix stick.
Mistakes to avoid
Do not treat connected as the same thing as working. Local connection and service access are different.
Do not reset the whole setup before checking queues, app scope, DNS, account state and router isolation.
Do not keep adding duplicate printer or app entries. Remove stale entries when the saved path is wrong.
FAQ
Why does my printer say Ready but not print?
Because Ready often describes the printer's own condition, not the full computer-to-printer path. The queue, driver or saved IP can still be wrong.
Start with the queue and printer entry before deeper network changes.
Should I clear the print queue?
Yes. A stuck job is one of the most common causes of Ready but not printing.
Cancel old jobs, restart the computer and send one fresh test page.
Why are there two copies of my printer?
Duplicate entries often appear after router changes, driver installs or reconnecting the printer.
Remove the stale one and keep the entry that prints a test page.
Can the printer IP address change?
Yes. Routers can assign a new local IP after restarts or long offline periods.
A DHCP reservation can keep the printer easier to find.
Should I reinstall the driver?
Do it after queue and entry checks. Driver reinstall helps when the computer sees the printer but jobs do not process correctly.
Use the official printer maker's driver or app.
Why can I scan but not print?
Scanning and printing may use different services or driver paths.
Scan success proves some connection exists, but the print queue or driver can still be broken.
Is this a Wi-Fi problem?
Sometimes, but not always. If the printer is online and only one computer cannot print, the computer path is more likely.
If no device can print, check printer Wi-Fi and router settings.
Should I factory reset the printer?
Not first. A reset erases Wi-Fi and setup without fixing a stuck queue or wrong entry.
Use it only after simpler checks fail.
When should I contact support?
Call support if the printer has current firmware, a clean queue, correct entry and still refuses print jobs from multiple devices.
Have the model, router, computer system and any error messages ready.
Outside references
- Microsoft Printer Help
Official Windows printer connection troubleshooting reference.
- HP Printer Support
Official printer diagnostics and model support reference.