How to print several Word files from the File > Open dialog
Word can print files it never opens, straight from its own Open dialog. Pick File, then Open, then Browse, select several files inside the dialog, right-click and choose Print. It is fast, and it gives you no chance to set anything first.
The trick is documented by university IT departments as much as by software vendors, which is a decent sign it works the same everywhere. UCLA's IT knowledge base spells out both the steps and the catch in one line: "This sends the files straight to the printer without allowing you to adjust your printer settings."
The trade is right there in that sentence. You skip the walk to the folder, and you take whatever the driver has set for the tray. The UCLA page names no file-count limit, and we found no source that puts one there, so treat the count as untested and keep the selections modest. One practical difference from Explorer is worth knowing: the dialog filters to document types by default, which makes it harder to poison the selection with a stray spreadsheet.
How to print Word files by dropping them on the printer queue
Drag the selected files onto the open printer queue window and Windows prints them. The 15-item rule is about context menu entries, so it has nothing to say about drag and drop. This is the shortest way around the wall when you do not want to touch the registry.
How to print every Word document in a folder with a VBA macro
Word's object model can print a file by name without opening a window for it. A Dir loop over the folder plus Application.PrintOut is the closest thing to a supported batch print inside Word itself, and it is the only built-in route that does not care how many files the folder holds.
Microsoft describes the PrintOut method as printing "all or part of the specified document", and the same reference page carries an official example that loops a folder with Dir("*.DOC") and calls Application.PrintOut FileName:=adoc on each hit. That example is the backbone of nearly every batch print macro on the web. Ours keeps the shape of the loop and changes three small things.
Sub PrintFolderOfWordFiles()
Dim folderPath As StringDo While adoc <> ""
Application.PrintOut FileName:=folderPath & adoc, Background:=FalseEnd Sub
To run it, press Alt+F11 in Word, choose Insert then Module, paste the code, change the folder path to yours, and press F5.What each line of the macro does:
Background:=False is the parameter that keeps the order straight, for the same reason the add-in above disables background printing. The PrintOut reference page documents it beside PrintZoomColumn and PrintZoomRow for pages per sheet, and ManualDuplexPrint for double-sided output on printers with no duplex unit. If you are already writing a macro, those three save you a second pass.
Why does the macro stop on a locked or read-only file?
Because something else is holding the file. Word cannot get the access it needs on a document already open elsewhere, and a file or template flagged read-only-recommended can come back read-only even when the macro opens it cleanly. Both failures look identical from the outside: one document, no page.
The Word MVP FAQ keeps a whole page on locked-file errors, and the cause it names is duller than people expect. Word writes an owner file next to every open document, ~$Name.docx, and that hidden file is what produces the "file in use" message. A crash leaves it behind, and the document stays locked with nobody holding it. A file can also arrive read-only without anyone locking it at all. A document or template saved with the read-only-recommended flag opens that way every time, and it comes back read-only to a macro too.
The third failure is quieter. Macros written around Documents.Open have to close each document explicitly, and when something goes wrong before the close line runs, the window stays. Come back an hour later and there are eleven Word windows waiting for you, which is also the honest answer to why multiple Word documents seem to open by themselves after a batch job. The macro above sidesteps that particular mess, since printing by file name never opens a window in the first place.
What breaks when you send 100+ Word documents at once?
Nothing new breaks at volume. The same small failures simply arrive often enough to matter. One file is open on somebody else's PC, another wants a password from the bank, and the spooler reorders what is left. The built-in routes neither handle that nor mention it, so you find out at the printer.
Picture a month of invoices. 140 files, one of them still open in Word on the accountant's second monitor, two of them password protected from the bank, and the rest fine. The Explorer route prints 137 documents, says nothing about the other three, and leaves you to count sheets and work out what is missing. Speed is not what breaks here. Those three files are.
Volume also multiplies the small stuff. Every stray Word window from a failed file stays in memory. Saved email attachments in the same folder, the kind you would normally push through an EML to PDF converter to read them, break the shared Print verb the moment they join the selection. And a wrong default tray costs you 140 sheets instead of one.
Before a large run, print three files as a sample and check the tray, the duplex setting and the order they land in. A wrong printer default across 140 documents is a paper problem, not a software problem, and nothing undoes it once the sheets are out.
Which method should you use?
Three answers pick the route for you. Count the files, look at how many file types are mixed in, then check whether Microsoft Word is on the PC. Only one branch needs a macro, and only one needs anything installed at all.
| Your situation | Route | What it costs you |
|---|---|---|
| Up to 15 files, all Word, driver defaults are fine | Right-click Print in File Explorer | No settings, no report, order not guaranteed |
| More than 15 files, all Word, one-off job | Drop them on the printer queue | Same lack of settings, but no registry edit |
| More than 15 files and you want the menu back | MultipleInvokePromptMinimum above your file count | A registry edit plus a sign-out or explorer.exe restart |
| A whole folder, same job every month | VBA macro with Background:=False | You maintain the macro; it stops on locked files |
| Folder mixes Word, PDF, spreadsheets, images | A dedicated batch printer | An install, and settings you have to look at once |
| No Microsoft Office on the PC | BatchPrint's own DOCX reader | Headers and footers do not print on that path |
The last two rows are where batch print software for Windows earns its place, when you print multiple Word documents at once every month. Everything above them is a job which Windows already does one way or another. For eleven letters going to the same tray, the right-click menu is still the correct answer, and nobody needs to install a thing.
Sources
The Microsoft troubleshooting article behind the 15-item menu limit, the reference for the PrintOut method and the two Microsoft Q&A threads, one on mixed file types and one on print order, are all linked in place next to the facts they back.