In October 2026 Microsoft Publisher reaches end of life. It will be removed from Microsoft 365, and subscribers will no longer be able to open or edit Publisher files in the app. Perpetual Publisher 2021 copies keep running without support. Microsoft recommends rebuilding layouts in Word or PowerPoint, and converting .pub files to PDF before the deadline.
Microsoft announced the retirement back in February 2024, so this is not a sudden change, but the deadline is now inside the current financial year. Publisher first shipped in 1991 and has outlasted nearly every desktop publishing rival of its era. Plenty of Australian small businesses still run their monthly newsletter or their shelf tickets through it, which is why the change deserves attention now rather than in late September.
What exactly happens to Publisher in October 2026?
For Microsoft 365 subscribers, Publisher is being removed from the product, not merely frozen. Microsoft's guidance states that subscribers will no longer be able to open or edit Publisher files in Publisher after the retirement date, and the app will no longer be available for installation or download. That is stronger than an ordinary end of support. The software does not simply stop receiving updates; access to it goes away.
Perpetual-licence copies behave differently. A business that bought Publisher 2021 outright, or runs it inside Office 2021, can keep installing and using the app beyond the deadline. Microsoft confirms this in its own FAQ. The app simply becomes unsupported software, with no further security updates or fixes from Microsoft, which makes it a poor long-term home for anything a business depends on.
What does Microsoft recommend instead?
There is no single successor app. Microsoft's guidance instead maps each common Publisher job onto software the business already licenses. Word inherits the document-shaped work and PowerPoint inherits the free-form visual layouts.
- Word: labels, envelopes, letterhead, newsletters, invoices and forms, and folded programs.
- Word or PowerPoint: flyers, brochures, certificates, business cards, calendars and greeting cards.
- PowerPoint: banners, signs and posters, where free placement of text and images matters most.
- Microsoft Designer: quick graphics and social images, generated from a prompt rather than laid out by hand.
- Microsoft Create (create.microsoft.com): a free template library for Word and PowerPoint that covers most of the old Publisher template catalogue.
The honest trade-off is print precision. Publisher's controls for commercial printing had no equal elsewhere in Office, and a business that sends complex artwork to a print shop will notice the difference. For everyday office output, the position is arguably better than before. Word and PowerPoint are under constant active development and co-author properly in the browser. Both sit inside the Microsoft 365 licence the business already pays for, so there is nothing new to buy.
What happens to existing .pub files?
This is the part that catches people out. The .pub format is proprietary, and no mainstream application opens it natively apart from Publisher itself. There is no import path into Word or PowerPoint. Once a Microsoft 365 tenant loses Publisher, every .pub file on the file server turns into a sealed box. The conversion window is open now and closes in October 2026.
Microsoft's supported route runs through PDF. Open each file in Publisher, choose File, then Save As, and select PDF as the file type. A PDF can then be opened directly in Word, which converts it into an editable document, though Microsoft notes the layout may shift, particularly where the original leans heavily on graphics. For a business sitting on hundreds of files, Microsoft publishes a sample PowerShell script, Convert-PubFileToPDF.ps1, that bulk-exports every .pub file in a folder tree to PDF while Publisher is still installed. Third-party tools that convert .pub directly do exist, though Microsoft does not support them.
The migration checklist
- 1Find every .pub file now. Microsoft's own suggestion is a simple search for .pub across the PC fleet, OneDrive and SharePoint, plus the desktop of whoever produces the newsletter.
- 2Sort the results into two piles: live templates the team still reuses, and archive documents nobody will ever edit again.
- 3Rebuild the five to ten templates that actually matter in Word or PowerPoint, starting from a Microsoft Create template where one fits.
- 4Bulk-export the archive pile to PDF using Microsoft's sample script, so old editions stay readable long after Publisher is gone.
- 5Remove Publisher from the standard operating environment once nothing depends on it, rather than letting the deadline do it unannounced.
Who actually feels this change?
Not graphic designers, who moved on years ago. The people affected are admin staff and office managers whose working week quietly includes a handful of ancient templates. The school newsletter that has looked the same since 2015. The sporting club's fixture flyer. The real estate agency's window cards. The retail shelf tickets run off every Monday from a file someone's predecessor built. Each of these keeps working right up until the day it does not, and the person responsible usually finds out from an error message rather than a memo.
Where should the rebuilt templates live?
The retirement is a nuisance, but it carries a genuine opportunity. Publisher templates typically live on one PC, or in a forgotten corner of the file server, and only one person knows which copy is current. Rebuilding them in Word and PowerPoint is the natural moment to move them into a SharePoint document library instead. The whole team then works from a single current version with tracked changes, and a new starter can find the newsletter template on day one without asking anyone.
Stored that way, the rebuilt templates also become proper shared assets: co-authored in the browser, backed up with the rest of the tenant, and visible to Microsoft 365 search. None of that was ever true of a .pub file sitting on the office manager's C: drive.
Publisher has earned a respectful send-off. A thirty-five year run is remarkable for any desktop application, and it served small offices well for most of that time. Its replacements are under active development and already covered by the business's existing licence, so the migration costs time rather than money. Frontrow rebuilds template libraries in SharePoint as part of its Modern Work engagements, and a Publisher migration is a small, well-bounded version of that job. A 30-minute call is enough to scope how many .pub files a business is sitting on and what the tidy-up would take.