How to Clear a Print Queue (And What to Do When It Won't Clear)
A stuck print queue is one of those frustratingly common tech problems — your printer stops responding, jobs pile up, and nothing moves no matter how many times you hit "Print." Here's exactly how the print queue works, why it gets stuck, and how to clear it across different setups.
What Is a Print Queue?
The print queue (also called the print spooler queue) is a temporary holding area managed by your operating system. When you send a document to print, it doesn't go directly to the printer — it gets converted into a print job and placed in a queue. The Print Spooler service (on Windows) or the equivalent background process (on macOS/Linux) then feeds those jobs to the printer in order.
This system exists for good reason: it lets you queue multiple documents, print in the background while you keep working, and manage job order. The problem is that if a job becomes corrupted, the printer disconnects mid-job, or the spooler service stalls, the entire queue can freeze — and new jobs stack up behind the broken one.
How to Clear a Print Queue on Windows 🖨️
Method 1: Cancel Jobs Through the Taskbar
The simplest first step:
- Double-click the printer icon in the system tray (bottom-right corner), or go to Settings → Bluetooth & devices → Printers & scanners, select your printer, and choose Open print queue.
- Right-click each job and select Cancel.
- Wait 30–60 seconds and check whether the queue clears.
This works for jobs that are pending but not yet processing. It often fails for jobs that are actively stuck or marked as "Deleting" — those require a deeper fix.
Method 2: Restart the Print Spooler Service
This is the most reliable fix for a frozen queue on Windows:
- Press Windows + R, type
services.msc, and hit Enter. - Scroll to Print Spooler, right-click it, and select Stop.
- Open File Explorer and navigate to:
C:WindowsSystem32spoolPRINTERS - Delete all files inside that folder (not the folder itself — just the contents).
- Return to Services, right-click Print Spooler, and select Start.
Those files in the PRINTERS folder are the spooled job data. Deleting them while the service is stopped wipes the queue completely. Once the spooler restarts, the queue will be empty.
Method 3: Use the Command Prompt
For users comfortable with the command line, this does the same thing faster:
net stop spooler del /Q /F /S "%systemroot%System32spoolPRINTERS*.*" net start spooler Run these three lines in Command Prompt as Administrator (right-click → Run as administrator).
How to Clear a Print Queue on macOS
- Go to System Settings (or System Preferences) → Printers & Scanners.
- Select your printer and click Open Print Queue.
- Click the X next to any job to cancel it, or select a job and press Delete.
If jobs won't cancel, the equivalent of the Windows spooler on macOS is the CUPS (Common Unix Printing System) service. You can reset it via Terminal:
sudo launchctl stop org.cups.cupsd sudo launchctl start org.cups.cupsd Alternatively, removing and re-adding the printer in Printer & Scanners clears all associated queued jobs.
Why Print Queues Get Stuck — The Real Variables
Understanding the cause helps you pick the right fix and avoid repeat problems. The most common culprits:
| Cause | What's Happening | Typical Fix |
|---|---|---|
| Corrupted print job | Bad file or unsupported format sent to printer | Delete job files + restart spooler |
| Printer went offline mid-job | Job is "locked" waiting for a printer that disappeared | Restart spooler, check connection |
| Driver mismatch | Wrong or outdated driver sending bad data | Update or reinstall printer driver |
| Network printer issues | IP address changed or printer dropped off network | Reconnect printer, update port settings |
| Spooler service crashed | Windows service stopped unexpectedly | Restart spooler service |
Printer drivers are a significant variable here. A driver mismatch — especially after a Windows Update or a printer firmware update — can cause jobs to corrupt before they even reach the printer. If your queue clears but keeps getting stuck with new jobs, the driver is worth investigating before anything else.
Shared and Network Printers Add Complexity 🔧
On a home or office network, clearing the queue on your own machine may not be enough. If the printer is shared through another computer (a print server), the queue lives on that machine — not yours. You'd need access to the host computer to clear it.
For printers connected directly to a network (via ethernet or Wi-Fi, not through a PC), most have a built-in web interface accessible through a browser using the printer's IP address. Many network printers let you cancel jobs directly from that interface, bypassing the OS entirely.
Managed office environments may lock down spooler access — in those cases, your IT department controls the print server, and clearing stuck jobs may require submitting a support ticket rather than doing it yourself.
When Clearing the Queue Doesn't Solve the Problem
If the queue clears but the printer still doesn't respond, the queue itself wasn't the root issue. At that point, the diagnostic path shifts: checking the physical connection, verifying the printer shows as online (not offline) in your OS, confirming the correct printer is set as default, and checking for driver or firmware issues.
Whether you're on a personal laptop, a shared office machine, a Windows domain, or a Mac — the core steps are the same, but the access level, network setup, and driver environment you're working within will shape exactly how straightforward each step turns out to be.