What is POT? PowerPoint Template (Legacy) Explained

How POT Works

A .pot file is a PowerPoint template saved in the older binary PowerPoint format used through the PowerPoint 97 to 2003 era. Rather than a plain text or a modern archive, it is stored as a Compound File Binary document, sometimes called an OLE compound file. This container works like a small file system packed inside a single file: it holds a set of internal streams and storages, each carrying a distinct part of the template such as the document summary, the presentation records, and any embedded objects.

Because it belongs to the same binary family as the classic .ppt, a .pot file shares almost the same internal record structure. The difference is one of role rather than encoding. A template is meant to be a reusable starting point, so it stores slide masters, slide layouts, theme colors, font choices, background settings, and placeholder text. When you build a new presentation from it, PowerPoint copies those design elements into a fresh working file instead of editing the template in place.

Reading the format means parsing the compound file directory, locating the presentation stream, and walking a sequence of typed binary records. Each record carries a header and a payload, and records can nest to describe masters, color schemes, and placeholders. This tight binary layout kept files compact for its time, but it also made the format hard to inspect without PowerPoint or a dedicated library, since none of the structure is human readable text.

A .pot template could also carry VBA macros embedded as an internal stream. That gave organizations a way to ship automation alongside a corporate design, but it also meant a template could execute code, which is why later formats separated macro-free templates from macro-enabled ones.

History and Standardization

The .pot extension dates from the era when Microsoft PowerPoint stored everything in the proprietary binary compound format, spanning roughly the PowerPoint 97 through 2003 releases. During that period the binary format was the default for presentations, templates, and slide shows alike, and it was documented mainly through Microsoft's own specifications rather than an open standard body.

With Office 2007, Microsoft moved to the Office Open XML family and split the old template role into two clearer successors: the macro-free .potx and the macro-enabled .potm. The legacy .pot was retained only for backward compatibility, so newer versions of PowerPoint can still open it but no longer produce it as the standard template type.

Adoption of the binary .pot was tied directly to how widely PowerPoint itself was deployed in offices, schools, and design teams. Many organizations built libraries of branded templates in this format, which is why files and tooling for it persisted well after the format was officially superseded.

POT Compared to POTX and PPT

Compared with POTX, the key contrast is the underlying container. POT uses the opaque binary compound file, while POTX uses a modern archive of XML parts that is far easier to inspect, script, and repair. POTX is also macro-free by design, moving any automation into the separate .potm type, whereas a single .pot could freely mix template design and executable macros in one file.

Compared with PPT, the relationship is one of purpose rather than encoding. A .ppt is a finished presentation, while a .pot is a template you spawn new presentations from, yet both sit on the same binary compound file structure. That shared foundation is why converting between them within older PowerPoint was straightforward and why the same parsing libraries tend to handle both.

The honest trade-off is compatibility versus transparency. Keeping a design in .pot maximizes compatibility with very old software, but the binary format is harder to audit, more fragile if corrupted, and unable to separate trusted design from potentially unsafe macros. For most current work, migrating a legacy template to .potx gives a cleaner, safer, and more portable result while preserving the reusable design intent.