🖨️ Print Test Page
📴 Offline cluster

Printer offline but connected to Wi-Fi

🔍
Different trigger? Offline after sleep · Offline after Windows update · Offline on one device only · Ping works but still offline. For stuck print jobs blocking after the printer comes back online, see the queue guide.
Quick answer
When Windows or macOS shows a printer as offline but the printer is powered on and connected, the operating system has lost the printer's network path. This happens most often because the router restarted and DHCP assigned the printer a new IP address — the old address saved in the computer's printer entry is now invalid. The two-minute fix: remove the printer and re-add it. The permanent fix: assign the printer a static IP in your router's DHCP reservation settings so the address never changes.
⚡ Quick checks
  • Power cycle the printer completely — hold Power off for 30 seconds, then power back on
  • Windows: Settings → Printers & Scanners → click printer → Open print queue → Printer menu → uncheck "Use Printer Offline" if it's checked
  • Print a network configuration page from the printer's own control panel to find its current IP address
  • Confirm the printer and computer are on the same Wi-Fi network — not guest vs main, not 2.4GHz vs 5GHz-only SSID
  • Remove the printer from Printers & Scanners and re-add it fresh

Why printers go offline on Wi-Fi networks

DHCP IP address change — the primary cause

Most home and office routers assign IP addresses dynamically via DHCP (Dynamic Host Configuration Protocol). Each device on the network gets a temporary address that may change when the lease expires or when the router restarts. When the printer's IP changes, the computer's saved printer entry still points to the old address — the printer is reachable at its new IP, but the computer is looking in the wrong place. The printer appears offline even though it's physically connected and visible to other devices.

💡
Quick test: Open your browser and type the printer's current IP address (from its network config page) into the address bar. If the printer's web interface loads — you can see the HP, Canon, Epson, or Brother configuration page — the printer is reachable. The offline status is entirely a stale entry on the computer, not a printer problem.
Sleep and wake reconnection failure

Many printers enter a deep sleep mode after a period of inactivity that disconnects the Wi-Fi radio to save power. When the printer wakes, it attempts to rejoin the network — but this reconnection sometimes fails silently, especially on dual-band routers or when the printer has to authenticate again. The printer's display shows connected, but the Wi-Fi association has actually dropped. See the sleep-specific guide for the fix.

Stale Windows printer port

Windows tracks each printer's network address as a "port" in the driver configuration. After an IP change, the port still contains the old address. Even if you add the printer fresh using auto-discovery, Windows may re-use the old port entry rather than creating a new one. Check: Printer properties → Ports tab — the active port's IP should match the printer's current IP.

Step-by-step fix

  • Find the printer's current IP: print a network configuration page from the printer's control panel (Setup → Reports → Network Configuration Page, or similar)
  • Type that IP into your browser — confirm the printer's web interface loads (this proves reachability)
  • On Windows: Settings → Bluetooth & devices → Printers & scanners → click the offline printer → Remove
  • Click Add device — if auto-discovery finds it, add it. If not, click "Add manually" → "Add using IP address" → enter the IP from step 1
  • Print a test page immediately after adding to confirm
  • Permanent fix: log into your router admin panel → find DHCP → create a reservation for the printer's MAC address (shown on the printer's network config page) → assign it a fixed IP outside the DHCP range

Fix by operating system

  • Settings → Bluetooth & devices → Printers & scanners → click the printer → Open print queue
  • Printer menu at top of queue window → confirm "Use Printer Offline" is NOT checked. If it is, uncheck it
  • If that doesn't fix it: remove the printer → Add device → add by IP address if discovery fails
  • Check the driver port: right-click printer in Printers & Scanners → Printer properties → Ports tab → the checked port's IP should match the printer's current IP
  • Windows 11 extra check: Settings → Bluetooth & devices → Printers & scanners → scroll down → turn off "Let Windows manage my default printer"
💡
Windows 11 built-in troubleshooter: Settings → System → Troubleshoot → Other troubleshooters → Printer → Run. It automatically checks for the "Use Printer Offline" flag, stale port entries, and Spooler issues — resolves most offline cases without manual steps.
  • System Settings → Printers & Scanners → click the printer — if it shows "Paused", click Resume
  • Open Print Queue → delete any stuck jobs
  • If still offline: click the minus (−) button to remove the printer → click plus (+) to re-add
  • If Bonjour/auto-discovery doesn't find it: click the IP tab → enter the printer's current IP address → select the correct driver (not Generic PostScript)
  • macOS note: "offline" in macOS usually means "paused" — check the queue first before removing the printer

Assigning a static IP — the permanent fix

The only reliable way to prevent recurring offline issues is to ensure the printer always gets the same IP address. There are two methods:

Method 1: DHCP reservation in your router (recommended)
  • Log into your router admin panel — usually at 192.168.1.1 or 192.168.0.1 in your browser
  • Find DHCP → DHCP Reservations (or Static DHCP, Address Reservation — terminology varies by router brand)
  • Add the printer's MAC address (shown on its network config page) and assign it a fixed IP address
  • Choose an IP outside the router's DHCP range — for example, if DHCP assigns .100–.200, use .50 for the printer
  • Save and restart the printer — it will request its new reserved address
Method 2: Static IP on the printer itself

Most printers allow you to assign a static IP directly in their network settings. Access via the printer's control panel (Network → TCP/IP → IP Address Mode → Manual) or via the printer's embedded web server (type the current IP in your browser → Network → TCP/IP settings → change from Automatic to Manual).

Official support

HP
Canon
Epson
Brother
😴 Offline after sleep

Printer offline after sleep or idle period

🔍
This covers offline status that appears consistently after the printer has been idle. If the printer is offline for other reasons, see all offline causes.
Quick answer
Printers go offline after sleep because the printer's Wi-Fi radio disconnects during deep power-save mode and doesn't successfully rejoin the network on wake. The printer's display may show it's connected, but the actual Wi-Fi association has dropped. The quickest fix is a full power cycle. The permanent fix is either to disable the printer's sleep mode or to disable the Wi-Fi sleep setting specifically in the printer's power management settings.
⚡ Quick checks
  • Power cycle the printer completely — don't just wake it. Hold power off for 30 seconds, then restart
  • After power cycle, confirm the printer shows a solid Wi-Fi connection indicator (not flashing)
  • Check the printer's control panel: Settings → Power Management → Sleep Mode or Auto-Off — set the sleep timeout to Never or extend it significantly
  • On the printer's network settings page: look for "Wi-Fi Sleep" or "Wireless Sleep" — disable it separately from the general sleep setting

Why sleep causes offline status

Inkjet and laser printers have sleep modes that reduce power consumption during idle periods. Different models implement sleep differently — some only dim the display while maintaining Wi-Fi, others cut power to the Wi-Fi radio entirely. The problem is with printers that cut Wi-Fi power: when they wake, they attempt to rejoin the network, but this reconnection process isn't always automatic. The printer shows "Connected" on its display (because it's trying to reconnect) but hasn't actually established a valid association yet.

Compounding this, Windows and macOS mark a printer as offline if a print job sent during the reconnection window fails to deliver. The OS doesn't automatically re-check and clear the offline status once the printer successfully reconnects — you have to intervene manually or remove and re-add the printer.

Permanent fix — disable Wi-Fi sleep

  • On the printer's control panel: navigate to Settings → Power Management (or Network Settings → Power Save)
  • Find Sleep Mode or Auto Power Off — set to disabled or maximum timeout (usually 4 hours)
  • Look separately for Wi-Fi Direct Sleep or Wireless LAN Sleep — some printers have this as a separate option. Disable it
  • Alternatively, access these settings via the printer's embedded web server: type its IP into your browser → Power Management or Network settings
  • Save and restart the printer — test by letting it sit idle for 30 minutes, then send a print job
💡
Trade-off: Disabling sleep mode increases power consumption. For most inkjet printers this is 5–15 watts during idle — roughly $5–$15 per year in electricity. For infrequently used printers, the convenience may be worth it. Alternatively, use a smart plug to turn the printer off completely between uses — a deliberate power cycle avoids the sleep/wake reconnection problem entirely.
Back to cluster
Printer offline — all causes and fixes
→
Advanced offline
Ping works but printer still shows offline
→
🔄 Offline after update

Printer offline after Windows update

🔍
This covers offline status triggered specifically by a Windows update. For offline after sleep, see offline after sleep. For all causes, see the complete offline guide.
Quick answer
Windows updates cause printer offline status for one of three reasons: the update replaced the OEM driver with a generic one that uses a different port configuration, the update changed the printer's port entry silently, or Windows 11's "Let Windows manage my default printer" setting switched the default to a different printer. Run the built-in printer troubleshooter first — it catches most update-related offline causes automatically.
⚡ Quick checks
  • Windows 11: Settings → System → Troubleshoot → Other troubleshooters → Printer → Run
  • Windows 10: Settings → Update & Security → Troubleshoot → Printer → Run
  • Check driver: Printers & Scanners → click printer → Printer properties → Advanced tab → Driver field. If it says "Microsoft IPP Class Driver" — reinstall the OEM driver
  • Check port: Printer properties → Ports tab → confirm the checked port matches how the printer is connected (USB00X for USB, printer IP for network)
  • Windows 11 only: Settings → Bluetooth & devices → Printers & scanners → scroll down → turn off "Let Windows manage my default printer"

What Windows updates change that causes offline

  • Windows Update silently replaces the OEM driver (HP Full Feature, Canon PRINT, etc.) with a generic Microsoft IPP Class Driver — this driver uses different port settings
  • Windows Update changes the printer port from a static IP port to a WSD (Web Services for Devices) port — WSD is discovery-dependent and fails when the printer's IP changes
  • Windows 11 cumulative updates sometimes reset the "Let Windows manage my default printer" setting to enabled, causing jobs to route to a previously used printer
  • Windows Security updates change firewall rules that block the printer's communication ports (9100, 5353)

Fix sequence after a Windows update

  • Run the built-in printer troubleshooter (locations above) — it handles most update-related offline causes automatically
  • If troubleshooter doesn't fix it: check the driver via Printer properties → Advanced tab
  • If driver is generic/Microsoft: remove from Printers & Scanners AND Device Manager → download OEM driver from the brand's support page → reinstall as Administrator
  • If driver looks correct: check the port via Printer properties → Ports tab → ensure the IP shown matches the printer's current IP
  • If port IP is wrong: click "Configure Port" → update the IP address to the printer's current IP
  • After any driver or port change: print a test page from Printer properties → Print Test Page to confirm
Full Windows context
Windows 11 printer troubleshooting — update issues
→
Back to cluster
Printer offline — all causes and fixes
→
💻 Offline on one device

Printer offline on one device but works on others

🔍
If the printer works on your phone but this specific computer shows it offline, you may be looking at the works on phone not laptop issue instead. This guide covers computers where the printer is offline on one Windows PC or Mac but accessible from other computers.
Quick answer
When a printer is offline on one device but works on others, the problem is entirely on the device that shows offline — not the printer. The printer is reachable, which the other devices confirm. The cause is almost always a stale printer entry, a wrong port setting, a user account permission issue on that specific device, or the device being on a different network segment than the others.
⚡ Quick checks
  • On the problem device: confirm it's connected to the exact same Wi-Fi network as the working devices
  • Check for a VPN running on the problem device — VPN routes traffic away from the local network
  • On the problem device: remove the printer and re-add it fresh
  • Check the user account: log out and log in as a different user — if the printer works for another user, it's a per-account permission issue
  • Confirm network discovery is enabled on this device: Windows → Network & Sharing settings → Turn on network discovery

Device-specific offline causes

  • The device's printer entry has a stale IP from before the printer's address changed — other devices added the printer more recently and have the current IP
  • VPN active on this device — VPN tunnels all traffic through a remote server, making local network devices (including the printer) unreachable
  • The device is connected to a different network — same SSID but different band (2.4GHz vs 5GHz) can place devices on different subnets on some routers
  • User account lacks printer permissions — common in corporate environments or after switching between local and domain accounts
  • Network discovery disabled on this device specifically — Windows sometimes disables this after a security update
  • A Windows user account with "Printer Offline" mode saved from a previous session — the flag persists per-user

Fix on the specific device

  • Disable any VPN on this device — test printing immediately after
  • Check network: Settings → Network & Internet → confirm the same SSID as working devices
  • Enable network discovery: Settings → Network & Internet → Advanced network settings → Advanced sharing settings → Private networks → turn on Network discovery
  • Remove the printer from Printers & Scanners on this device only → add it fresh
  • If a different user account on this device can print: the issue is per-user. In the problem user's account, remove and re-add the printer to refresh the per-user settings
  • If printer was added by an admin account and you're using a standard account: the admin may need to share the printer for standard users
Related issue
Works on phone but not laptop — full device-specific guide
→
Back to cluster
Printer offline — all causes
→
🌐 Ping works, still offline

Printer offline but ping works — and web UI loads

🔍
This advanced guide covers cases where the printer is clearly reachable on the network (ping responds, browser loads the printer's web interface) but Windows still shows it as offline. For basic offline fixes, start with the main offline guide.
Quick answer
If ping works and the printer's embedded web server loads in your browser, the printer is definitely reachable on the network. The offline status is a Windows driver problem, not a connectivity problem. Specifically: the driver's port configuration is pointing to the wrong IP or using WSD discovery instead of a static TCP/IP port. The fix is to delete the printer, then re-add it using a static TCP/IP port that points to the printer's current IP.
⚡ Quick checks
  • Open cmd.exe → type ping [printer IP] → confirm it responds (this proves network connectivity)
  • Open a browser → navigate to the printer's IP → confirm the printer's configuration page loads
  • Both of the above working confirms: the problem is 100% on the Windows side, not the printer
  • Check the port: Printer properties → Ports tab → the active port should show the printer's IP. If it shows "WSD-" followed by a long string — that's the problem

WSD ports vs TCP/IP ports — the technical cause

Windows can connect to network printers in two ways: via a static TCP/IP port (which uses a fixed IP address) or via a WSD (Web Services for Devices) port (which uses discovery to find the printer dynamically). WSD ports are convenient but fragile — they lose track of the printer when the IP changes, and they can enter a failed state where Windows shows the printer offline even though it's reachable by IP. A static TCP/IP port doesn't have this problem because it goes directly to the IP address every time.

Fix — switch from WSD to TCP/IP port

  • Settings → Printers & Scanners → click the printer → Printer properties → Ports tab
  • Note which port is currently checked — if it starts with "WSD-", that's the issue
  • Click Add Port → select Standard TCP/IP Port → New Port
  • Enter the printer's IP address → complete the wizard → the new port appears in the list
  • Check the new TCP/IP port → click Close → Apply
  • Send a print job to confirm the printer is now reachable through the TCP/IP port
# PowerShell: check current printer port
Get-Printer -Name "Your Printer Name" | Select-Object PortName

# List all printer ports
Get-PrinterPort | Format-Table Name, PrinterHostAddress
Back to cluster
Printer offline — all causes
→
OS context
Windows 11 printer troubleshooting
→
👻 Phantom offline

Windows shows printer offline but it prints anyway

🔍
This covers the specific case where Windows reports the printer as offline but jobs still go through. For standard offline issues, see the main offline guide.
Quick answer
When Windows shows a printer as offline but print jobs still complete, Windows has cached the printer's status as offline from a previous failed attempt and hasn't refreshed it — even though communication has since been restored. This is a display bug, not a functional issue. The fix: open the print queue, go to Printer menu, uncheck "Use Printer Offline" — the status icon updates to reflect the actual connected state.
⚡ Quick checks
  • Settings → Printers & Scanners → click printer → Open print queue → Printer menu → uncheck "Use Printer Offline"
  • If you can't find the Printer menu: in the queue window, click Printer in the menu bar at the top
  • After unchecking, the status icon in Printers & Scanners should update to show the printer as ready
  • If the option keeps re-enabling itself: a queued job that failed is triggering the offline mode — clear the queue first, then uncheck offline mode

Why this happens

Windows sets a printer to "offline" mode when a print job fails to communicate with the printer. This is meant to prevent a flood of repeated failed attempts. Once the printer recovers (after a power cycle or reconnection), Windows doesn't automatically detect the recovery and clear the offline flag — it waits for user confirmation via the "Use Printer Offline" checkbox. Meanwhile, some print jobs may succeed because the underlying connection actually works — Windows' offline status is stale and inaccurate.

This is most common after a brief network interruption (router reboot, printer sleep/wake cycle) where the printer reconnects before Windows retries the communication check.

If "Use Printer Offline" keeps re-enabling

If the offline flag keeps reappearing, a failing or stuck print job is triggering it repeatedly. Clear the print queue completely first:

  • Win+R → services.msc → Print Spooler → Stop
  • Navigate to C:\Windows\System32\spool\PRINTERS → delete all files inside
  • Restart Print Spooler → open the print queue → confirm it's empty
  • Now uncheck "Use Printer Offline" — with no failing jobs, the flag should stay cleared
Related
Print job stuck in queue — Spooler reset guide
→
Next cluster
Print job stuck in queue
🗂️ All queue causes ⚙️ Spooler keeps stopping ❌ Stuck after cancel 🍎 Mac queue 📦 Large file stuck
🗂️ Queue cluster

Print job stuck in queue and won't delete

🔍
Specific trigger? Print Spooler keeps stopping · Job reappears after deleting · Mac queue stuck · Large file or PDF stuck. The printer going offline after clearing the queue is a separate offline issue.
Quick answer
When a print job is stuck and the Cancel button does nothing, the Windows Print Spooler service is holding a file lock on the corrupted job. Clicking Cancel in the queue window sends a message to the Spooler, but the Spooler ignores it while the lock is active. The only reliable fix: stop the Print Spooler service, delete the spool files from disk, then restart the Spooler. This takes about 60 seconds and clears even the most stubborn stuck jobs.
⚡ Quick checks
  • Try cancelling from the queue window first — right-click the job → Cancel. Wait 30 seconds
  • Restart the printer and computer — this clears the Spooler state in most cases without manual steps
  • If jobs won't delete after restart: use the Spooler reset method below
  • On Mac: open Print Queue → Pause the queue first → then delete the job → then Resume

The Spooler reset — the reliable fix

  • Press Win+R → type services.msc → press Enter
  • Scroll to Print Spooler → right-click → Stop
  • Open File Explorer → navigate to C:\Windows\System32\spool\PRINTERS
  • Delete all files inside the PRINTERS folder — do NOT delete the folder itself
  • Return to services.msc → Print Spooler → right-click → Start
  • Send a small test print (one word in Notepad) to confirm the queue is clear
# PowerShell — run as Administrator
Stop-Service -Name Spooler -Force
Remove-Item "$env:SystemRoot\System32\spool\PRINTERS\*" -Recurse -Force
Start-Service -Name Spooler
Write-Host "Spooler reset complete"
💡
Why Cancel doesn't work: The Print Spooler maintains a file lock on each spool file (.SPL and .SHD files) while processing it. When a job becomes corrupted or stalled, the Spooler keeps the lock open indefinitely. The Cancel button in the queue window sends a cancellation request to the Spooler, but the Spooler can't act on it because it can't release the lock on the file it's stuck on. Stopping the Spooler service releases all locks simultaneously, allowing the files to be deleted.

Why print jobs get stuck

  • Corrupted spool file — the job data was damaged during creation or transfer, creating a file the Spooler can't process or release
  • Large file partially transferred — a large PDF or photo was partially sent to the spool folder before the connection dropped, creating an incomplete file the Spooler loops on indefinitely
  • Network printer went offline mid-job — the Spooler holds the job in a "sending" state waiting for the printer to come back, but it never clears automatically
  • Driver crash — a printer driver crashing mid-job can corrupt the spool file it was processing, leaving it locked
  • Shared printer sending duplicate jobs — if the printer is shared on a network, multiple computers may be retrying the same failed job

macOS queue fix

  • System Settings → Printers & Scanners → click the printer → Open Print Queue
  • Click the Pause button at the top of the queue window
  • Select stuck jobs → click the X button to delete
  • If X button doesn't work: hold Option while clicking X to force-delete
  • Click Resume — send a small test print to confirm
# macOS Terminal — cancel all queued jobs
cancel -a

# Restart the CUPS printing system
sudo launchctl stop org.cups.cupsd && sudo launchctl start org.cups.cupsd

Official support

Windows
HP
Canon
Epson
⚙️ Spooler crash

Print Spooler keeps stopping automatically

🔍
This covers cases where Print Spooler crashes repeatedly, not just a one-time stuck job. For a single stuck job, see the main queue guide.
Quick answer
When the Print Spooler service crashes repeatedly and automatically — stopping itself moments after you restart it — a corrupted or incompatible printer driver is almost always the cause. The Spooler loads each installed printer's driver into memory when it starts; a bad driver crashes the Spooler process. The fix is to identify the problem driver and remove it, or reinstall it from the brand's official support page.
⚡ Quick checks
  • Check Event Viewer: Win+R → eventvwr.msc → Windows Logs → System → look for Print Spooler errors (Event ID 7031 or 7034) — they often name the driver that crashed it
  • If you recently installed a new printer or driver, that driver is the most likely culprit — remove it first
  • Run sfc /scannow in an elevated Command Prompt — corrupted system files can cause Spooler instability

Finding the problem driver

  • Press Win+R → type eventvwr.msc → Windows Logs → System → filter for Source: "Service Control Manager" and Level: Error
  • Look for entries about "Print Spooler" — the error message often names the specific driver file (.dll) that caused the crash
  • Note the driver filename → open Device Manager → Printers → find which printer uses that driver
  • Remove that printer from Printers & Scanners AND from Device Manager → check if Spooler stays stable
  • Reinstall the driver from the brand's official support page — download the latest version for your OS
# Check Spooler event log from PowerShell (run as Admin)
Get-EventLog -LogName System -Source "Service Control Manager" -Newest 20 | Where-Object {$_.Message -like "*spooler*"} | Format-List TimeGenerated, Message
💡
Multiple printers installed: If you have several printers installed, isolate the problem by temporarily removing all non-essential printers. Restart Spooler after each removal — when it stops crashing, the last removed printer had the bad driver.

Set Spooler to auto-restart after crash

As a temporary measure while troubleshooting, you can configure the Spooler to restart automatically if it crashes:

  • Win+R → services.msc → double-click Print Spooler
  • Click the Recovery tab
  • Set First failure, Second failure, and Subsequent failures to Restart the Service
  • Set "Reset fail count after" to 1 day → Apply → OK
Back to cluster
Print job stuck in queue — all causes
→
Related
Printer driver installed but not printing
→
❌ Queue stuck after cancel

Print job keeps coming back after deleting — queue won't stay clear

🔍
This covers jobs that are deleted from the queue but immediately reappear. For a job that won't delete at all, see the main queue guide.
Quick answer
When a deleted job immediately reappears in the queue, another device on the network is re-sending it. This most commonly happens with shared printers — another computer that has the printer shared is retrying the failed job, or a print server is re-queuing it. The fix: identify which device is re-sending and cancel the job from that device. If it's a network-shared printer, clear the queue on the host computer, not the client.
⚡ Quick checks
  • Check if the printer is shared — Settings → Printers & Scanners → click printer → Printer properties → Sharing tab
  • If shared: log into the host computer (the one sharing the printer) and clear the queue there
  • Check if another user or device on the network has the same document queued
  • Use the Spooler reset method — stop Spooler, delete spool files, restart — even reappearing jobs are cleared by this method

Why jobs reappear after deletion

  • A shared printer — the host computer's Spooler holds the authoritative queue; deleting from a client computer doesn't clear the host's queue, which re-sends the job
  • A print server (hardware or software) is managing the queue and automatically retries failed jobs
  • The same document is open in an application that re-sends the print job when it detects the queue cleared
  • A network printer management system (common in offices) is re-queuing the job from a central server
  • Rarely: a corrupted Spooler state where the job deletion isn't being written to disk — the Spooler loads the cached version on restart

Fix — stop the job at the source

  • Identify whether the printer is shared: Printer properties → Sharing tab. If it's shared, go to the host computer
  • On the host computer (or your own computer if not shared): use the full Spooler reset — stop service, delete files, restart service
  • Close the application that sent the original print job before restarting the Spooler — some apps auto-retry when they detect the queue cleared
  • If in an office with a print server: contact your IT administrator — the server needs to clear its own queue
  • If the job reappears even after Spooler reset: disconnect from the network temporarily → clear the queue → then reconnect. This prevents any network device from re-sending during the clear
Back to cluster
Stuck queue — all causes and fixes
→
🍎 Mac queue stuck

Print queue stuck on Mac — jobs won't delete or print

🔍
This is macOS-specific. For Windows queue fixes, see the main queue guide.
Quick answer
macOS uses CUPS (Common Unix Printing System) rather than Windows' Print Spooler. Stuck jobs on Mac are usually cleared by pausing the queue first, deleting the jobs, then resuming. If that fails, the CUPS backend can be restarted via Terminal, or the entire printing system can be reset from the Printers & Scanners right-click menu. The Mac approach is simpler than Windows and rarely requires deleting files manually.
⚡ Quick checks
  • System Settings → Printers & Scanners → click printer → Open Print Queue → click Pause
  • With the queue paused: select stuck jobs → click the X button to delete
  • If X doesn't delete: hold Option while clicking X to force-delete
  • Click Resume — send a test print

macOS queue fix — step by step

  • System Settings → Printers & Scanners → click your printer → Open Print Queue
  • Click the Pause button (pause icon at top of queue window) to stop the queue from processing
  • Select each stuck job → click the X to delete. Hold ⌥ Option while clicking X if the job won't delete normally
  • Click Resume to restart the queue
  • If jobs still won't delete: open Terminal → type cancel -a → press Enter. This cancels all jobs for all printers system-wide
  • If the queue remains frozen after cancelling: restart CUPS — Terminal → sudo launchctl stop org.cups.cupsd → wait 5 seconds → sudo launchctl start org.cups.cupsd

Nuclear option — Reset Printing System

If nothing clears the queue: System Settings → Printers & Scanners → right-click anywhere in the printer list → Reset printing system… → enter your admin password. This removes all printers, all drivers, and all queued jobs. You'll need to re-add your printers afterward.

💡
macOS vs Windows queue management: macOS's Reset Printing System is more thorough than Windows' Spooler reset — it completely removes all printer configurations. Use it only when simpler methods fail, and be prepared to re-add all printers afterward.
Full macOS context
macOS printer troubleshooting — queue, AirPrint, Reset Printing System
→
Back to cluster
Stuck queue — all causes
→
📦 Large file stuck

Large file, PDF, or photo stuck in print queue

🔍
This covers queue failures specific to large documents, high-resolution images, and complex PDFs. For general queue fixes, see the main queue guide. For PDFs that print blank rather than getting stuck, see test page works but PDF won't print.
Quick answer
Large files get stuck in the queue because the print job exceeds either the printer's memory capacity or the driver's rendering time limit, causing the job to stall mid-transfer. Unlike smaller stuck jobs, large file stalls often can't be cleared by simply cancelling — the spool file is partially written and the Spooler can't cleanly abort it. Use the full Spooler reset, then resend the job with reduced quality or as a print-to-PDF first.
⚡ Quick checks
  • Use the Spooler reset to clear the stuck job (see the main queue guide for steps)
  • Before resending: reduce print quality to Standard or Draft in the print dialog → Properties → Quality
  • Try printing to PDF first (File → Print → Microsoft Print to PDF) → then print that PDF — compression often makes the job manageable
  • Split the document: print pages 1–10, then 11–20 — smaller chunks avoid memory overflow

Why large files stall differently

When a large file is sent to the printer, the Spooler writes it to the spool folder as a .SPL file before processing. For very large jobs (high-resolution photos, complex PDFs, multi-page documents), this writing process itself can take minutes. If the job stalls during writing — due to low disk space, a rendering timeout, or a memory overrun — the .SPL file is incomplete and the Spooler loops on it indefinitely, unable to complete or abort cleanly.

The result is a stuck job that won't delete because the Spooler still has a write lock on the incomplete file. Only stopping the Spooler service releases this lock.

Fix — clear and resend at lower size

  • Use the full Spooler reset: stop service → delete spool files → restart service (from the main queue guide)
  • Check available disk space on C: — the spool folder needs room equal to the print job size. Low disk space causes large job failures
  • Resend with reduced quality: Print dialog → Printer Properties → Quality → switch from High to Standard or 300 DPI
  • For photos: resize to 150–200 DPI at the actual print dimensions using any image editor first
  • For multi-page PDFs: split into sections and print 10–20 pages at a time
  • Alternatively: File → Print → select "Microsoft Print to PDF" → create a compressed PDF → print that compressed PDF as the new job
  • For network printers: try connecting via USB cable for the large job — eliminates network timeout as a variable
Back to cluster
Stuck queue — all causes and the Spooler reset
→
Related
Test page works but large files won't print
→

Related problems

Printer prints blank pages
Nozzle, cartridge, and document rendering causes — complete guide.
Test page works but documents don't
Queue, driver, port, and app-specific fix guide.
Printer not found on network
IP address changed — add manually and assign static IP.
Works on phone but not laptop
Driver, network path, or permission issue on the laptop specifically.
Windows 11 printer troubleshooting
Spooler, offline, driver, and update-specific fixes for Windows 11.
macOS printer troubleshooting
CUPS queue, Reset Printing System, and AirPrint vs full driver.
Get printer help
1
🖨️