← Blog 9 min read

Microsoft Publisher Retires in October 2026: How to Get Your Files Out

Somewhere on a shared drive there is a folder called Newsletters, and it contains eleven years of .pub files. Nobody has opened most of them since they were printed. That folder is now on a deadline.

Microsoft has confirmed that Publisher reaches end of life in October 2026. There are two dates worth writing down, because they apply to different people:

  • 1 October 2026 — Microsoft 365 subscribers can use Publisher normally until this date. After it, Publisher is no longer part of the subscription, cannot be installed, and cannot be used to open or edit .pub files.
  • 13 October 2026 — perpetual copies, meaning Publisher from Office LTSC 2021 or Consumer Office 2021, keep working past the first date but reach end of support here. The app still launches; it just receives no security updates, bug fixes or support.

Your files do not expire. That is worth being clear about, because the panic tends to outrun the facts. A .pub file on a disk in 2027 is the same bytes it was in 2019. What goes away is the only mainstream program that reads it.

Why .pub is a worse trap than .doc ever was

Legacy Office formats are usually survivable. Old .doc and .xls files open in Word, in LibreOffice, in Google Docs, in a dozen viewers, because those formats were reverse-engineered and documented decades ago and every office suite implemented them.

Publisher never got that treatment. It was the least technical product in the Office family — the tool for the church bulletin, the school newsletter, the village fete poster — and its users were not the kind of customers who generated pressure for interoperability. So support for the format outside Publisher is thin. There is no Publisher web app, no Publisher for Mac, and no Publisher import in Word.

The result is a format where the only reliable reader is a program being switched off. That is a narrower escape route than any other retiring Office format has had.

What Microsoft actually gives you to migrate with

Microsoft’s guidance is to convert your files to PDF or Word before the deadline. Reasonable advice. The tooling behind it is thinner than the advice suggests:

  • Save As, inside Publisher. Exports one file to PDF, or to Word to keep the text. Works well. Requires Publisher to still be running, and it is one file at a time.
  • Convert-PubFileToPDF.ps1. An official sample PowerShell script that walks a folder and converts in bulk. It also needs a working Publisher install, because it drives Publisher to do the conversion — and as the name says, it only produces PDF.

Put those together and the supported options are: editable, but one file at a time, or a whole folder, but frozen as PDF. There is no supported path to editable output in bulk. For anyone with a hundred files, that is the gap they fall into — and it is the complaint that shows up repeatedly on Microsoft’s own support forums from people with thousands of files and twenty years of work.

The second problem is the precondition. Both routes assume you still have Publisher. A great many people with .pub archives do not: they let a subscription lapse, or they moved to a Mac, or the person who owned the licence retired. If Publisher is already gone, Microsoft’s migration path is closed before you start.

Choosing a target format, and the mistake to avoid

The single decision that matters is whether each document is finished or living.

PDF for finished documents. A PDF reproduces the Publisher layout faithfully — fonts, positioning, graphics, all of it. For a poster from 2014 that you might one day want to look at or reprint, this is exactly right. It is also the better archival choice, because PDF will still open in fifty years and nothing about it depends on a vendor.

Word for living documents. The annual fixture list, the price sheet, the membership form — anything you will edit again needs to arrive as editable text. Converting these to PDF only feels like it worked, and the bill arrives later, when someone needs to change a phone number and finds the document is a picture of itself.

If you cannot tell which category a file belongs to without opening it, the pragmatic answer is to do both. Storage is cheaper than judgement at this scale, and a mistake in the PDF-only direction is not recoverable without redoing the work by hand.

What survives a conversion to Word, and what does not

Being straight about this saves disappointment. Publisher is a page-layout program: everything sits in a free-floating frame that can be anywhere on the page, overlapping anything else. Word is a word processor, built around a flowing column of text. There is no faithful translation between those two models, and no tool of any price fully bridges it.

In practice, converting to Word:

  • Keeps the text, the headings, embedded images, and reading order — including multi-column layouts, where the columns are read one after the other rather than being interleaved line by line.
  • Loses exact frame positions, overlaps and precise typographic spacing. Elements land in a sensible document order rather than at their original coordinates.

So a text-heavy newsletter or a report usually arrives ready to edit with light tidying. A dense brochure with images tucked between angled text boxes will need those images repositioned. That is a real limitation, and it is still far better than retyping.

A migration that fits in an afternoon

  1. Find the files. Search for *.pub everywhere, not just the obvious place: local disks, OneDrive, SharePoint, external drives, old machine backups. Archives of this kind are almost always spread across more locations than anyone remembers.
  2. Sort finished from living. You do not need to open every file. Folder names and dates usually tell you: 2015 Flyers is finished, Membership Form is living.
  3. Convert the finished ones to PDF. Fast, faithful, and done.
  4. Convert the living ones to Word, then actually open a few and check them. Fidelity varies with layout complexity, and you want to know that now rather than in 2027.
  5. Keep the original .pub files. Do not delete them once converted. They cost nothing to store, and if a better converter appears later it will need the originals to work from. The deadline removes your ability to open them, not your right to keep them.

Converting without Publisher, and without uploading to strangers

If Publisher is already unavailable to you, conversion has to come from software that reads the format independently. That is what our tools do — there is no Microsoft software involved anywhere in the chain:

One thing worth saying plainly about the privacy side, because the files people are migrating are often not neutral. A membership form has names and addresses in it. A parish newsletter has phone numbers. A school bulletin has children in it. Feeding that through a random conversion site means handing over the contents and the filename to be stored, logged, or trained on.

Ours are processed in memory inside a network-free sandbox, on a server with swap disabled so nothing can be paged out to disk. The file is never written to storage, never logged, and neither is its name — which means there is nothing to delete afterwards, because nothing was kept. If you would rather not take that on trust, the honest alternative is to install LibreOffice locally: it reads .pub too, and nothing leaves your machine at all. We would rather tell you that than pretend we are the only option.

Do it before September

Not because anything breaks early, but because the second step in the list above — opening a few converted files and checking they are usable — is the one people skip when they are rushed. Discovering that a layout needs manual work is a small problem in August, when Publisher still runs and you can go back to the original. In November it is a much larger one.

The files are not going anywhere. The program that reads them is.