A stuck print job keeps its files on your Mac until you cancel it properly
macOS keeps print job data in /var/spool/cups until a job finishes or is cancelled. How to see stuck jobs, cancel them with their files, and restart printing.
When you print, macOS writes the job's data to /var/spool/cups and keeps it until the printer has taken it. A large PDF sent to a printer that is offline, out of paper or long gone can sit there indefinitely, and the queue keeps trying.
The folder is only readable as an administrator. Listing it without sudo returns Permission denied (checked on macOS 26, October 2026), which is why it never shows up when you look around in Finder.
lpstat -o # jobs waiting, per printer
sudo du -sh /var/spool/cupsCancel jobs and their files
cancel -a -x-a cancels every job on every printer and -x also deletes the job data files. That is the clean way to empty the spool, and it avoids deleting files from under the print system by hand. If printing still seems stuck, restart the print service:
sudo launchctl kickstart -k system/org.cups.cupsdNormally this folder is nearly empty, so if it is not, a stuck job is almost always the reason. Old printer drivers are a separate and usually larger cost: see printer drivers. For the other hidden system folder people ask about, see /private/var/folders.
Common questions
Where does a Mac store print jobs?
In /var/spool/cups, which only an administrator can read. Each waiting job has a control file and one or more data files there.
How do I cancel all print jobs from Terminal on a Mac?
Run cancel -a to cancel every job on every printer. Adding -x also deletes the jobs' data files, which frees the space they held.
Is it safe to delete files in /var/spool/cups?
Cancelling with cancel -a -x is the safe route, because the print system removes its own files. Deleting them by hand while jobs are queued can leave the queue in a confused state.