DOT File Format: The Legacy Microsoft Word Template Explained

A DOT file is a legacy Word starting point, not a finished document

A .dot file is a Microsoft Word 97-2003 template. It is a reusable starting point that can hold fixed wording, paragraph and character styles, page layout, headers, footers, AutoText entries, custom keyboard assignments, menus, and sometimes VBA macros. Word used DOT for templates while .doc was the ordinary document extension. A template may contain sample content, but its main job is to generate new documents that share the same rules. This is why a DOT file commonly appears among old business forms, letterheads, reports, contracts, or internal add-ins rather than among final records.

The time boundary is important. DOT was compatible with Word 97 through Word 2003 on Windows and Word 98 through Word 2004 on Mac. Word 2007 changed Office files to the XML-based Open XML family. The modern macro-free template is .dotx; the modern macro-enabled template is .dotm. Current desktop Word can still open an old DOT, but making a new template today usually calls for DOTX or DOTM. A legacy DOT should be retained only when an older Word environment, an old template workflow, or a compatibility requirement genuinely needs the old binary format.

The template flag and the compound file behind it

DOT is not a plain-text file and it is not a renamed DOCX. Like a Word 97-2003 DOC file, it is stored in an OLE2 Compound File Binary container. Its familiar opening signature is D0 CF 11 E0 A1 B1 1A E1, the same signature used by many old Word, Excel, and PowerPoint files. That signature can identify an old Office compound file, but it cannot by itself distinguish a DOT template from a DOC document. The distinction is made through the extension and an internal template setting in Word's File Information Block, often called the fTemplate flag.

This shared binary structure explains two otherwise confusing facts. First, changing a file name from .doc to .dot may make Word treat it as a template even though the core binary records have not been converted into a new format. Second, a hex editor cannot safely repair a template just because the words are visible somewhere in the file. Word's binary format is a collection of records and structures for text, tables, fields, pictures, and other content. A damaged file can have intact visible text but broken indexes or streams. Use Word's Open and Repair feature or a trusted recovery route on a copy before attempting low-level edits.

Keeping a legacy template has costs beyond its age

• Gain - original workflow behavior: an old Word installation can use its styles, AutoText, menus, and other template resources as their author intended.
• Gain - new documents from one master: opening a template normally creates an unsaved document based on it, reducing accidental edits to the master.
• Gain - legacy compatibility: DOT is the correct template form for Word 97-2003 and older Mac Word workflows that cannot use DOTX.
• Loss - binary opacity: the OLE container and Word records are much harder to inspect or repair than the XML parts inside modern DOTX files.
• Loss - feature ceiling: a DOT cannot represent all functionality added to Word after the 2007 Open XML transition.
• Loss - security and support friction: DOT may contain VBA macros, and current Office applies extra protection to template files downloaded from the internet.

A template is not automatically harmless because its visible purpose is a letterhead. In Microsoft's current macro-blocking guidance, .dot is listed alongside DOTM as a macro-enabled template type when it carries Mark of the Web from an internet download or email attachment. Office blocks macros by default in that situation. Do not remove the security mark merely to silence a warning. Verify the publisher and intended code first. A digitally signed template from a trusted publisher, or one distributed through a managed Trusted Location, is a safer organizational route than asking people to enable unknown macros individually.

Where current Word and alternative editors draw the line

Current desktop Word can open older DOT files, and it can save a new document as a modern DOTX template or a DOTM template when macros must remain. Word for the web is not the right environment for validating an old template's behavior: legacy menus, VBA code, template attachment, and other desktop features need a desktop application. On macOS, Microsoft documents a separate user-template location and advises saving new templates as DOTX or DOTM. Those current locations do not change the file format of an inherited DOT; they are only where modern Word looks for templates.

LibreOffice Writer and other suites may open a DOT, but opening is not proof of full template compatibility. LibreOffice uses its own template management rather than Word's Normal.dot/Normal.dotm model, and a legacy Word template can contain menus, macros, AutoText, fields, or formatting behaviors with no exact equivalent. Treat an alternative editor as an inspection or recovery option, then test the new document in the Word version that will actually be used. This is especially important for printed forms, headers, page numbering, data fields, and document automation, where a small compatibility difference can become a wrong page layout or a missing command.

Before replacing a DOT, make two controlled tests: open the master for editing, then create a fresh document from it. These actions exercise different behavior. In the fresh document, type enough text to force a second page, use each prepared style, fill a table, and save under a new name. If the original template supplied an AutoText item or custom command, test that exact item rather than merely checking the opening page. This small test exposes template resources that a document-to-PDF comparison cannot reveal.

Why a template opens a blank document, loses menus, or warns about macros

Double-clicking the DOT produces a new unnamed document. That is normal template behavior, not evidence that the file is empty. Save the generated document under a different name. To change the master, use Word's Open command to open the template itself, make the change, and keep a backup before saving. The result has different fonts or pages after opening. The old template may call for fonts that are absent on the current computer. Word substitutes another font, changing word widths and therefore line and page breaks. Install a licensed matching font where appropriate, or deliberately replace it and review every form field, table, header, and page break.

Custom buttons or automated actions have disappeared. They may depend on VBA, an old menu system, an attached global template, or an add-in that did not come with the DOT. Opening the document in another office suite can also remove or reinterpret these controls. Record what action is expected, inspect the template in desktop Word, and do not enable unknown code while troubleshooting. Office reports blocked macros. A downloaded DOT can carry Mark of the Web. Confirm the origin, scan it under the organization's process, and use a signed or managed-trust distribution if the automation is legitimate; do not treat conversion to a new extension as a security fix.

DOT, DOC, DOTX, and DOTM compared by job

Questions before putting an old template back into use

Can I rename DOT to DOTX?
No. DOTX is a ZIP-based Open XML template, while DOT is an OLE compound binary file. Use an actual conversion or Save As operation, then test the output.

Why does Word make a new document instead of opening the file?
That is the template's intended behavior. Open the DOT directly through Word when editing the master, and save documents made from it under new names.

Can a DOT contain macros even though its name does not end in DOTM?
Yes. DOT predates the modern macro-specific extension split. Treat an untrusted DOT as potentially macro-bearing and follow Office's security warning rather than enabling code on request.

What should be archived after modernization?
Keep the original DOT, a documented tested DOTX or DOTM replacement, the necessary fonts and add-ins where licensing permits, and a sample document that proves the expected output.