Publisher opens the file but shows a blank canvas. What happened?

The file's global metadata is intact enough to open, but the page structure is damaged. The content is often still recoverable via Open and Repair, or by opening the file on a different Publisher version, or by extracting it with a converter that reads the raw layout.

What causes a .pub file to become corrupted?

Three usual suspects: a save interrupted by a Publisher crash or a Windows freeze, a sync conflict on OneDrive or SharePoint that overwrote half the file, and a transfer through a broken pipe (email, cloud drive, USB stick) that truncated the bytes. The .pub format has no built-in redundancy, so a single bad byte in the header wing can break the whole file.

Can I repair a .pub file without installing Publisher?

For simple corruption, LibreOffice Draw opens many .pub files and lets you re-save them to a cleaner state. For deeper damage, a server-side batch tool like PublisherRescue reads the raw structure outside Publisher and extracts what is still usable to a PDF plus editable format.

Guide · updated 2026-08-25

Publisher repair: how to fix a corrupted .pub file in 5 steps

Q: How do I repair a corrupted Publisher file?

Open Publisher, File then Open, browse to the file, click the arrow next to Open and pick Open and Repair. If that fails, try a different Publisher version, then recover the auto-save, then copy content into a fresh .pub, then a batch extractor.

Q: Is there a Microsoft Publisher repair tool?

No standalone Microsoft tool. Repair is bundled into Publisher itself as the Open and Repair option in the File then Open dialog. There is no scanpub.exe equivalent to scanpst.exe for Outlook.

Q: How is repair different from recovery?

Repair fixes a .pub that sits on disk but opens broken. Recovery brings back a .pub that is missing (deleted, wiped by a crash, lost with the disk). If your file is on disk, you need repair. If it is gone, you need recovery.

Publisher launches, you double-click the .pub, and something goes wrong: an error dialog, a blank canvas, a hang that ends with the app closing itself. The file is still on disk, but broken. Five repair methods work in practice, in the order below. The first one fixes about four files in ten. By the fifth, almost everything left comes back at least partially.

Try this order

Open and Repair from Publisher's File dialog. Two clicks.
A different Publisher version on another PC.
Recover the auto-save copy if a crash was involved.
Copy page-by-page into a fresh .pub when metadata is broken.
Server-side batch extract when Publisher itself refuses.

How do I repair a Publisher file?

In Publisher, go to File then Open, browse to the corrupted .pub without double-clicking, select it once, then click the small arrow next to the Open button and pick Open and Repair. Publisher scans the file structure, rebuilds the directory of streams, and reopens what survives. This fixes roughly 40 percent of "cannot open" cases. If it fails, the next steps below cover every other reasonable path: a different Publisher version, the auto-save copy, a page-by-page rebuild, and finally a server-side extractor that reads .pub outside Publisher itself.

Before you start: what "corrupted" actually means

Publisher does not tell you which part of the file is damaged. It just refuses to open it, or opens it wrong. Under the hood, a .pub file is a compound document: a header, a directory of streams (pages, images, styles, fonts, metadata), and the streams themselves. A single broken byte in the header or the directory takes the whole file down. A broken byte inside one stream usually lets the rest open, minus that one page.

The five methods below attack the problem from different angles: repair what is broken, work around it with a different reader, recover from a saved copy, salvage page by page, or read the raw streams outside Publisher. Almost every case that has a fix responds to one of the five.

Method 1: Open and Repair (fixes about 40 percent of cases)

The shortest path, and the first one to try. It is a real repair pass, not just a re-open attempt: Publisher scans the file's structure, rebuilds the directory of streams, and tries to reopen the document from what survives.

Open Publisher on the machine where the file is.
Go to File then Open. Do not double-click the file.
Browse to the .pub, select it with a single click.
Click the small arrow next to the Open button in the dialog.
Pick Open and Repair.

Wait. On a small file it takes seconds; on a large or heavily damaged one, up to a minute. Publisher either reopens the document with a warning listing what it fixed, or reports the file cannot be repaired. If it reopens: save immediately with a new name (document_repaired.pub). Do not overwrite the original. You will want it around if the repair loses something you notice only later.

Method 2: try a different Publisher version

Publisher versions share the .pub format but read it with slightly different parsers. A file saved from Publisher 2019 that hits an edge case in Publisher 2010 sometimes opens fine on 2016 or 2021. This is not a bug worth filing (nobody at Microsoft is fixing Publisher parser bugs in 2026), it is a workaround.

Two practical setups:

A colleague with a different Publisher. Send the .pub, ask them to open it and re-save. The fresh save often opens cleanly on your original install too.
A second Publisher on another PC or a VM. Office 2016 and Office 2019 boxes still surface on eBay and refurbished-software sellers. Install on a spare machine, open the file, re-save.

Same rule as method 1: after the file opens on the other version, Save As to a new filename. Never overwrite the broken original in place.

Method 3: recover the auto-save copy

If Publisher crashed on you while the file was open, or the machine lost power mid-edit, an auto-save copy probably exists. Publisher keeps them for a limited time and shows them the next time you launch the app.

Open Publisher. If the "Document Recovery" pane appears on the left, click the file there and save it under a new name. Done.
If it did not appear: File then Info, Manage Document, Recover Unsaved Publications.
If the menu shows nothing: open File Explorer, paste %LOCALAPPDATA%\Microsoft\Office\UnsavedFiles in the address bar, press Enter. Look for a .pub with a date near your crash.

Auto-saves are per-user and per-machine. They will not help if the crash happened on a colleague's PC and you are trying to recover on yours. They also age out (Office cleans them after roughly four days for most editions), so the sooner you look, the better.

Method 4: copy content into a fresh .pub

When the file opens but is still misbehaving (rendering wrong, refusing to save, crashing on print), the corruption often sits in the file's global settings, not in the pages themselves. Rebuild the container around good pages.

Create a new, blank publication with the same page size as the damaged one.
Open the damaged file (with Open and Repair if needed).
Go to the first page. Edit then Select All. Copy.
Switch to the new publication, same page. Paste.
Repeat for every page. Save the new file frequently.

Tedious for a fifty-page document, fast for a flyer or a brochure. The point is to leave behind whatever metadata was making the original unstable. Fonts, master pages, and page-level styles come across with the paste; document-level oddities do not.

Method 5: batch extract with a server-side tool

For a file Publisher itself refuses to touch, or for a whole archive where per-file work is not realistic. This is where a converter that reads .pub outside Publisher pays for itself.

PublisherRescue accepts a folder, a ZIP, or a drag-and-drop of files. On the server the pipeline opens each .pub with the native Publisher engine, exports the salvageable content to a high-fidelity PDF, and generates editable formats where the file permits. Files Publisher declared unopenable often produce a usable partial extraction (missing pages flagged, everything else intact). You see a free preview per file before you decide to pay, so you know exactly what came back.

When repair really is not possible

Some files are past saving. If the .pub is a few kilobytes when it should be megabytes, or if opening it in a hex editor shows large runs of zero bytes, the file was truncated (usually by a broken upload, a bad USB stick, or a sync that got half a file). No repair tool brings back bytes that were never written.

At that point the useful move is a recovery pass, not a repair. Look for a previous version of the same file: Windows File History on the folder, OneDrive version history, or a colleague's inbox where you emailed it once. Details in the Publisher file recovery guide.

A whole archive of broken .pub files?

Upload every file. We open what Publisher refuses to open and return a preview of what came back, before you pay.

Rescue my archive

Frequently asked questions

How do I repair a corrupted Publisher file?

Publisher File then Open, arrow next to Open, Open and Repair. If that fails, try a different Publisher version, recover the auto-save, copy content into a fresh .pub, or use a batch extractor.

Publisher opens the file but shows a blank canvas. What now?

The metadata opens, the pages did not. Open and Repair often fixes it; a different Publisher version is the next try; a batch extractor is the last resort.

What causes a .pub to become corrupted?

Interrupted save (crash, freeze), sync conflict on OneDrive or SharePoint, or a truncated transfer over email, cloud, or USB. .pub has no redundancy: one bad header byte breaks the whole file.

Is there a Microsoft Publisher repair tool?

No standalone tool. Repair lives inside Publisher as Open and Repair. Nothing like scanpst.exe exists for .pub.

Can I repair without Publisher installed?

LibreOffice Draw opens many .pub files for a re-save. For deeper damage, a server-side extractor reads the raw structure outside Publisher.

How is repair different from recovery?

Repair fixes a file that is on disk but broken. Recovery brings back a file that is missing. If it is on disk, you need this page. If it is gone, see the recovery guide.