How to batch convert Publisher files to PDF

"I have over 2000 pub files - what app is easiest to use to batch convert" — someone asked on Microsoft's own support forum in March 2026, and the thread carries Microsoft's own "Same question (50+)" marker: at least fifty other people clicked that button rather than write it out themselves. (learn.microsoft.com) This page is the answer that question deserves.

Microsoft's own script

Microsoft publishes a free script for exactly this, Convert-PubFileToPDF.ps1. Run from inside the folder you want converted:

Convert-PubFileToPDF.ps1 -Filter "*.pub" -Recurse

and it walks that folder and its subfolders, converting every .pub file it finds.

Here's the part that trips people up, and it's worth being exact about: the script doesn't parse.pub files itself. It drives an installed copy of Publisher through COM automation — opening and saving each file the way you would by hand, just automated. That means it needs:

• Windows. It has never run on a Mac.
• A working, licensed Publisher installation on that machine, for the entire run.

If you have both, this genuinely is free, and it batches a whole folder in one command. Do this first if it applies to you.

Where it breaks, in people's own words

One asker reports the script failing outright with a CommandNotFoundException, and says Microsoft's "easy" framing doesn't hold up for someone who isn't already comfortable with PowerShell; a commenter on the same thread hit "Office.dll not found" trying the same approach. The same person notes that third-party converters they tried capped uploads somewhere between 3 MB and 1 GB, which "would take weeks" at the volume they had. (learn.microsoft.com, Jul 2026)

On the March thread above, a tool vendor relays that someone at Arcata Presbyterian spent "6+ hours" in "serious battles" with the PowerShell approach — despite having coding experience. (same thread) If that's the outcome for someone who codes, be honest with yourself about how it will go if you don't.

The catch that matters more than any of that

Every one of those failure modes at least assumes Publisher is there to drive. See what happens to Microsoft Publisher in October 2026 for the full picture, but the short version: Microsoft 365 subscribers lose the app on 1 October 2026. The free script doesn't stop being free — it stops having anything left to automate, on any machine that only has Microsoft 365.

The actual options

What the report does that a pile of PDFs doesn't

Nobody checks 2,000 PDFs by eye. That's the actual problem with converting an archive: a converter hands the files back and says "done", the thumbnails look fine, and six months later someone needs page 4 of the 2014 newsletter and it isn't there. So every batch here comes back with a report, per file, in plain language, covering the things we know go wrong in a.pub-to-PDF conversion:

• Small caps are dropped, and condensed or expanded type comes out at its normal width.
• WordArt headings are rebuilt with their original curve, colour and font, but their outlines, shadows and gradient fills are not — so compare those headings with the original.
• Substituted fonts are rarely the same width, so lines re-wrap and headings can overflow.
• Publisher 97 and 98 files keep their pictures now, but their text still lands a few points out of place, with different line spacing than the original.

Measured against a corpus of real Publisher files whose authors also exported the same file from Publisher itself: 74% of laid-out text reproduced, over7 documents, and 50% of marks landing where Publisher put them, over 8 documents — last measured2026-09-12. Full detail, and the free preview that lets you judge your own files before paying, is on the converter.

And to be explicit about the number that matters if your archive really is 2,000 files: the cap here today is 200 files per batch. A 2,000-file archive is roughly 10 batches, not one. That's a limit of the machine this runs on — measured, not a line drawn to sell you more — not a licensing trick.