📖 What is a PUB File?
A PUB file is a document created by Microsoft Publisher, the desktop publishing application Microsoft shipped from 1991. It holds page layout work such as brochures, newsletters, flyers, posters, catalogues, certificates and business cards. This is different from a .pub public-key file created by SSH tools such as ssh-keygen or PuTTY, which shares the extension but is an unrelated plain-text cryptographic key.
The distinction that matters is how a PUB file thinks about a page. A word processing file such as DOCX describes text flowing down a page, with images anchored into that flow. A PUB file does the opposite. It stores a set of independent objects, each pinned to an absolute coordinate on a specific page. A headline is not "the first paragraph" but a text frame at a fixed position with fixed dimensions. This is what makes Publisher good at layout and what makes PUB files awkward to convert into anything that expects flowing text.
Key Characteristics
- Binary format - not XML, not human-readable
- Coordinate-based - objects at absolute positions
- Undocumented - no published specification
- Single-vendor - only Publisher wrote it natively
What It Stores
- Text frames - with linked overflow chains
- Raster and vector images - embedded or linked
- Master pages - repeating background layouts
- Embedded fonts - for print fidelity
⚡ Quick Facts
| File Extension | .pub |
| Full Name | Microsoft Publisher Document |
| Category | Desktop Publishing / Page Layout |
| MIME Type | application/x-mspublisher (also seen as application/vnd.ms-publisher) |
| Developed By | Microsoft Corporation |
| First Released | 1991 (Microsoft Publisher 1.0) |
| Last Version | Publisher 2021 LTSC / Microsoft 365 Publisher |
| Specification | Never published by Microsoft |
| Container (v1.0) | Flat proprietary binary |
| Container (v2.0+) | Compound File Binary Format (CFBF / OLE) |
| Related Extension | .puz, Pack and Go bundle (Cabinet archive) |
| Application Status | Publisher retires October 1, 2026 |
Neither MIME type is registered with IANA, which is consistent with a format that was never formally specified.
🔬 Inside a PUB File
From Publisher 2.0 onward, a .pub file is not one continuous block of data. It is a Compound File Binary Format container, sometimes called OLE2 or a structured storage file. The easiest way to picture it is as a miniature file system packed inside a single file, with its own directories and its own separate data streams.
This container is not unusual in itself. Microsoft used the same wrapper for legacy .doc and .xls files, and the container format is publicly documented. What sits inside the container is where Publisher diverges. The way it encodes pages, objects, their coordinates and the relationships between them is entirely proprietary.
PUB file (CFBF container)
├── Contents # the proprietary payload (layout, objects, text)
├── Escher # drawing / shape records
├── Quill # text storage engine data
├── SummaryInformation # title, author, standard metadata
└── DocumentSummaryInformation # version number (2003+)
Stream names vary across Publisher generations and this diagram is illustrative rather than exhaustive. The practical point is the separation. Metadata sits in documented, readable streams, while the layout itself sits in an undocumented one.
✓ Readable Without Publisher
- File signature and version detection
- Document summary metadata (title, author)
- Page count and document dimensions
- Many embedded raster images
✗ Requires a Purpose-Built Parser
- Exact object coordinates and z-order
- Text frame linking and overflow chains
- Master page inheritance
- Embedded font data and typography
🔖 PUB File Signatures
Because the .pub extension has covered several generations of internal format, file identification relies on signatures rather than the extension alone. Publisher 1.0 wrote a flat binary file with its own magic header. From version 2.0 the file became a CFBF container, and the signature moved inside, onto the Contents stream.
| Generation | Signature | Location |
|---|---|---|
| Publisher 1.0 | E7 AC 2C 00 | Start of file (flat binary) |
| Publisher 2.0 – 2000 | E8 AC 22 00 | Contents stream inside CFBF |
| Publisher 2002 – 2019 | E8 AC 2C 00 | Contents stream inside CFBF |
| Publisher 2003+ | Version number also recorded in the container's document summary information | |
Signature values as catalogued by the Archive Team file format wiki. Because no official specification exists, community documentation of this kind is the primary public reference for the format.
🔒 Why the Format Stayed Closed
In February 2008, Microsoft released documentation for its core binary Office formats, Word, Excel and PowerPoint, under the Open Specification Promise. Third-party developers could finally implement them properly. Publisher was not included.
The omission was deliberate rather than an oversight. When a developer asked directly on Microsoft's own binary file format forum whether the Publisher specification would be published, a Microsoft escalation engineer replied that there were no plans to document the .pub file format. That position never changed over the following years.
No Specification
Word, Excel and PowerPoint were documented in 2008. Publisher was left out, and Microsoft confirmed it had no plans to change that.
Reverse Engineering Only
Every non-Microsoft reader of PUB files was built by studying real files and inferring the rules, not by following documentation.
libmspub
The open-source library behind LibreOffice's PUB support. Impressive work, but partial coverage, which is why complex files fail.
Version Drift
Each Publisher generation changed internal structure. A parser tuned for 2016 files may not read a 1997 file at all.
No Ecosystem
Closed formats attract few implementers. PUB never developed the broad third-party support that DOC and XLS eventually gained.
Preservation Risk
A format readable by exactly one application, from one vendor, is a textbook digital preservation problem.
⚔️ PUB vs Other Layout Formats
PUB is one of several page layout formats. Comparing them on openness and portability explains why PUB is the difficult one:
| Format | Application | Structure | Spec Public | Reads Elsewhere |
|---|---|---|---|---|
| .pub | Microsoft Publisher | Binary (CFBF) | ✗ No | ~ Partial only |
| .indd | Adobe InDesign | Binary | ✗ No | ~ Via IDML exchange |
| .idml | Adobe InDesign | XML in ZIP | ✓ Yes | ✓ Good |
| .afpub | Affinity Publisher | Binary | ✗ No | ✗ No |
| .sla | Scribus | XML | ✓ Yes (open source) | ✓ Good |
| Many | Binary (ISO 32000) | ✓ Yes | ✓ Universal |
PUB vs DOCX
These formats model a document in fundamentally different ways, which is why conversion between them is lossy by nature rather than by poor implementation.
- PUB: objects at absolute coordinates
- DOCX: text flowing through a page
- PUB: binary, undocumented
- DOCX: XML in ZIP, ISO 29500
PUB vs PDF
Both describe a fixed page, but they sit at opposite ends of the document lifecycle.
- PUB: editable source, elements separate
- PDF: fixed output, elements committed
- PUB: one application
- PDF: open standard, universal readers
💻 Software Support for PUB
Support for the PUB format is narrow and uneven. This table records what each application can actually do with a .pub file, rather than what it advertises:
| Application | Reads PUB | Complex Layouts | Platform |
|---|---|---|---|
| Microsoft Publisher | ✓ Native | ✓ Full | Windows |
| Univik PUB tools | ✓ Dedicated parser | ✓ Full | Windows |
| LibreOffice Draw | ~ Via libmspub | ~ Frequently fails | Win / Mac / Linux |
| CorelDRAW | ~ Partial import | ~ Variable | Windows |
| Microsoft Word | ✗ No import filter | ✗ — | — |
| Adobe InDesign | ✗ Not natively | ✗ — | — |
| Affinity Publisher | ✗ No | ✗ — | — |
| Canva | ✗ No PUB import | ✗ — | — |
| Google Docs / Drive | ✗ Stores, cannot preview | ✗ — | — |
To inspect a .pub file on Windows, the free Univik PUB Viewer reads the format directly, with no Publisher installation required. For choosing replacement software now that Publisher is retiring, see the Microsoft Publisher alternatives guide.
🔄 PUB Conversion Targets
Because PUB stores absolutely positioned objects, how well it converts depends entirely on whether the destination format shares that model. Fixed-layout targets preserve the page; flowing-text targets do not. This reference shows what survives:
| Target | Layout Model | Fidelity | Best For |
|---|---|---|---|
| Fixed page | ✓ Highest | Archiving, print, sharing | |
| PNG / JPG | Fixed raster | ✓ Visual only | Web, previews, slides |
| SVG | Fixed vector | ✓ High | Design handoff, scaling |
| DOCX | Flowing text | ~ Layout shifts | Editing copy |
| HTML | Flowing / positioned | ~ Approximated | Web publishing |
| RTF / TXT | Text only | ✗ Layout lost | Content extraction |
| ePub | Reflowable | ✗ Rebuilt | E-readers |
Step-by-Step Conversion Guides
This page is a format reference. For instructions on each conversion, see the dedicated guides:
For batch processing across an archive, the Univik PUB Converter reads the format directly on Windows.
📜 Format Evolution 1991–2026
The .pub extension stayed constant for 35 years while the format underneath it changed repeatedly. This is why file age matters more than file size when troubleshooting:
1991 Publisher 1.0
First release, for Windows 3.0. The format is a flat proprietary binary file with its own magic header. Files from this era are the least widely readable today.
1993 Publisher 2.0
The format moves into a Compound File Binary Format container. The proprietary payload becomes an internal stream rather than the whole file. This container approach persists for the rest of the format's life.
1998 Publisher 98
Commercial printing features expand, increasing use of embedded fonts and colour separation data inside the file.
2000 Publisher 2000
Publisher joins the Microsoft Office family. Adoption widens sharply, and this generation accounts for a large share of surviving legacy PUB archives.
2002 to 2003 Signature Shift
The internal Contents stream signature changes, and from Publisher 2003 the container also records a version number in its document summary information, making programmatic version detection possible for the first time.
2007 Publisher 2007
Native PDF export arrives. Notably, Microsoft never introduced an XML-based .pub successor in the way DOC became DOCX. Publisher stayed binary while the rest of Office modernised.
2021 Publisher 2021 LTSC
The last perpetual-licence release. Publisher is subsequently omitted from the Office 2024 suite entirely.
October 1, 2026 Application Retirement
Microsoft 365 access to Publisher ends, on the same day Office LTSC 2021 reaches end of support. Perpetual installations keep running without updates. The format specification was never published in those 35 years, so no documented reference is left behind. See the guide to what happens to PUB files.
1991
First Release
Publisher 1.0
0
Published Specs
In 35 years
35
Years of Files
1991 to 2026
❓ Frequently Asked Questions
A PUB file is a Microsoft Publisher document. Publisher was Microsoft's desktop publishing application, shipped from 1991 until its retirement on October 1, 2026.
Key characteristics:
- Page layout, not word processing. objects sit at absolute coordinates
- Binary format. not XML, not human-readable
- Undocumented. Microsoft never published a specification
- Container-based from version 2.0 onward (CFBF / OLE)
MIME type: application/x-mspublisher
You have three practical options once Publisher is gone.
- View it. A dedicated PUB viewer reads the format directly on Windows and shows the page exactly, with no Publisher installation needed.
- Convert it. Turn the .pub file into PDF for a faithful copy, or into Word, an image or HTML depending on what you need next.
- LibreOffice Draw. Free and cross-platform, though its reverse-engineered support struggles with complex layouts, custom fonts and older files.
Renaming the file to .pdf or .docx does not work, because the extension is only a label. The bytes inside are still the proprietary Publisher format and need a tool that understands it.
Word has no import filter for the PUB format. There is no File → Open path that reads a .pub file, in any version of Word including Microsoft 365.
The deeper reason is structural rather than a missing feature:
- Word models a document as text flowing down a page
- Publisher models it as independent frames at fixed coordinates
- There is no clean mapping between the two models
- Even with a perfect parser, a multi-column brochure has no natural Word equivalent
- This is why converted output often needs manual layout repair
No. The extension covers several generations of internal format.
| Generation | Structure |
|---|---|
| Publisher 1.0 | Flat proprietary binary |
| Publisher 2.0 – 2000 | CFBF container, early signature |
| Publisher 2002 – 2019 | CFBF container, later signature |
| Publisher 2003+ | Version number also in summary information |
This explains a common experience. A tool opens recent PUB files but fails on files from the 1990s. The extension is identical; the format is not.
A PUZ file is a Publisher "Pack and Go" bundle, not a Publisher document.
Pack and Go was designed for handing work to a commercial printer or moving it between machines. It gathers the publication together with its dependencies into a single transferable file:
- The publication itself
- Linked images that live outside the .pub file
- Fonts required for correct rendering
Structurally a PUZ file is a Cabinet archive. If you have inherited a PUB file whose images appear missing, checking whether a matching PUZ bundle exists is worthwhile, since the assets may never have been embedded in the .pub file at all.
libmspub is an open-source library that reads the Microsoft Publisher format. Because Microsoft never documented PUB, the library was built by reverse engineering, studying real files and inferring the rules.
Why it matters:
- It is what gives LibreOffice Draw its PUB support
- Coverage is partial by nature. reverse engineering cannot be exhaustive
- Simple layouts often open correctly
- Complex layouts, custom fonts and pre-2000 files frequently fail
- It is a significant technical achievement, not a shortcoming. The limitation is the absent specification
No, and renaming does not work. Changing a file's extension changes its label, not its contents. A .pub file renamed to .pdf contains exactly the same bytes and no PDF reader will open it.
The formats serve opposite purposes:
| Aspect | PUB | |
|---|---|---|
| Role | Editable source | Fixed output |
| Elements | Separate and adjustable | Committed to the page |
| Specification | Unpublished | ISO 32000 |
| Readers | Publisher and few others | Universal |
No. In February 2008 Microsoft published documentation for its core binary Office formats, Word, Excel and PowerPoint, under the Open Specification Promise. Publisher was excluded.
Asked directly on Microsoft's binary file format developer forum whether the Publisher specification would be released, a Microsoft engineer replied that there were no plans to document the .pub file format. That position was never reversed.
The container is documented. Compound File Binary Format is public, and is the same wrapper used by legacy .doc and .xls files. What remains undocumented is the proprietary layout payload stored inside it.
The most widely used MIME type is application/x-mspublisher. The variant application/vnd.ms-publisher also appears in some systems.
Neither is registered with IANA, which is consistent with a format that was never formally specified. Where this matters in practice:
- Web servers without a .pub mapping serve the file as
application/octet-stream, a generic download - Upload filters that whitelist by MIME type may reject .pub attachments unless one of the two types is added
- Email systems vary in which of the two types they attach to .pub files
📝 Summary
- PUB = Microsoft Publisher document
- Uses the .pub file extension
- Proprietary binary. no published specification
- CFBF container from Publisher 2.0 onward
- Stores objects at absolute coordinates
- Word cannot open PUB, with no import filter
- libmspub gives LibreOffice partial support
- .puz is a Pack and Go Cabinet bundle
- Signatures differ across format generations
- Application retires October 1, 2026