Start Logging Print History on a Shared Windows 11 PC

Who printed that on a shared or work PC, and when? Windows may not be able to say: the print queue lists only pending jobs, and the PrintService log generally starts switched off. Turn that log on once and it builds a searchable record from that moment on, which you read in Event Viewer by name, user or time.

Applies to: Windows 11, version 24H2 and later; wording varies by build and driver. On the older system, see print history in Windows 10.

What Windows already keeps, and what you must turn on

RecordWhat it holdsHow longGood for
Print queuePending jobs only (Microsoft’s queue page)Until each job finishesWhat’s stuck right now
PrintService logAn event per job, typically with document name, user, printer and pagesUntil the log fills and overwritesWho printed what, and when
Keep printed documentsFinished jobs in one printer’s queue, on drivers that offer itUntil the queue is clearedA quick list for one printer
The printer’s own logJobs from every computer, on models that have oneVaries by modelShared and office printers

Don’t count on Word or other Office apps for this. They aren’t a print log.

Start a lasting record in a few minutes

You’ll probably need an administrator account. On a work PC, ask IT before changing this log, and on a shared PC remember that it records document names.

  1. Right-click Start and select Event Viewer. If the panes are unfamiliar, checking event logs in Windows 11 explains them.
  2. Expand Applications and Services Logs > Microsoft > Windows > PrintService.
  3. Right-click Operational and select Enable Log. If the menu offers Disable Log, it’s already on.
  4. Print a test page, then select Operational and press F5.

You can do the same from an administrator Terminal with wevtutil: wevtutil sl Microsoft-Windows-PrintService/Operational /e:true

Find one specific print job

Printed documents are generally logged as Event ID 307, usually under the task category Printing a document.

  1. Select Operational, then Filter Current Log in the right pane.
  2. Type 307 in the <All Event IDs> box.
  3. Use Logged to narrow the time range, then select OK.
  4. Open an event and read the details: typically document, user account, printer and pages.

Say Jordan needs to know who printed a 40-page report on Tuesday. Filter to 307, set the range to that day, then use Find in the right pane to search for the report’s name.

The name may not be useful. Microsoft has documented cases where Event 307 showed a generic “Print Document” string, on older Windows versions, with the fix being the Allow job name in event logs policy under Computer Configuration\Administrative Templates\Printers (Event ID 307 article). If you see generic names on Windows 11, that policy may be worth checking, though Microsoft’s article doesn’t cover Windows 11 and Windows Home has no Local Group Policy Editor.

Keep history longer without filling the disk

The log’s size decides how far back it goes. Right-click Operational, select Properties, raise the maximum size, and choose what happens when it fills up. The wevtutil tool sets the same limit in bytes with /ms (minimum 1048576), for example wevtutil sl Microsoft-Windows-PrintService/Operational /ms:52428800 for about 50 MB.

For a permanent copy, select Save Filtered Log File As while filtered, or export to CSV from PowerShell using the FilterHashtable keys Microsoft documents:

Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-PrintService/Operational'; ID=307; StartTime=(Get-Date).AddDays(-30)} | Select-Object TimeCreated, Message | Export-Csv "$env:USERPROFILE\Documents\print-history.csv" -NoTypeInformation

If PowerShell reports that no events were found, the log was off or nothing matches the dates. If access is denied, run it as administrator. The CSV lists document names and users, so store it carefully.

Shared PCs, work PCs and network printers

  • Shared home PC: the log generally covers all accounts, and anyone with administrator rights can read the names. Consider that before turning it on for others. A PIN job through Secure Print in Windows 11 keeps a sensitive page from sitting in the tray, though it’s a separate feature from logging.
  • Network printers: a PC’s log generally covers only jobs sent from that PC. For everyone’s jobs, try the computer that shares the printer, if its own log is turned on, or the printer’s own web page. Find the printer’s IP address, open it in a browser and look for Job Log, Job History or Usage. Wording differs by maker, and home models may show only page counts.
  • Work PCs: IT may already collect print records, or may control this log by policy. Ask before changing it. The Print Management console (printmanagement.msc) can also list printers on Pro and higher, but may be missing on Home.

To record just one printer, select it in Bluetooth & devices > Printers & scanners, open Printer properties, and on Advanced check Keep printed documents. Finished jobs should then stay in Open print queue, on drivers that offer this. A shortcut helps if you check often: put a printer icon on the desktop. Be aware that this keeps job data on the PC. If there’s no Advanced tab, the driver may be simplified, and adding a printer in Windows 11 covers the maker’s full driver.

Mistakes that erase or hide history

  • Clearing the queue: kept jobs can disappear when you clear the printer queue, since they live in that queue.
  • Selecting Clear Log: this erases the events, so save a copy first.
  • Opening the wrong window: Printing preferences isn’t Printer properties, and Windows Logs > Application isn’t where these events go.
  • Sending to the wrong printer: a job can sit in another printer’s records, so set a default printer if that keeps happening.

Turn it off and clear it

Right-click Operational and select Disable Log to stop recording, and, only after saving any copy you need, Clear Log to erase what’s there for good. To stop retaining jobs, uncheck Keep printed documents, then delete the finished jobs from the queue.

Questions people ask about printed-job records

Why does the log show a document name but not where the file is saved?

For documents printed from a local disk, the log appears to record the name only, so don’t expect a folder path.

Will clearing the print queue erase what Event Viewer recorded?

It shouldn’t. The queue and the log are separate, so events normally stay until you clear them or they’re overwritten.

How far back will the log go before it overwrites itself?

There’s no fixed period. It depends on the maximum size and how much you print. A busy office fills it faster, so check the oldest entry after a few weeks and adjust.

Can an administrator see what I printed?

If logging is on, assume so. Administrators can read the log on that PC, and an organization may collect it centrally.