Convert DOTX to PDF

This is the fact the whole page rests on. The registry marks DOTX with `template: true`, and Word treats that flag as an instruction: double-clicking the file produces `Document1`, a new unsaved file that inherits the template’s styles, content and page setup. The template itself is not open, has not been touched, and is not what you are looking at.

That behaviour is correct and useful — it is precisely what a template is for — and it is why "just print it to PDF" does not do what people expect. Exporting from that new document gives you a PDF of a copy, which is usually identical in appearance and is not the same object, and any change you made while poking around goes into the export. To open the template as itself you have to use File, Open and select it explicitly, which almost nobody knows. This conversion removes the trap by never involving Word at all.

Approval is the commonest reason. A new house style, letterhead or report format has to be signed off by people who will never install it — a communications lead, a partner, a client, a brand agency — and sending them a `.dotx` invites the confusion above. A PDF is something they can open on a phone, mark up and return.

Documentation is the second. A process note that explains how to complete a form is far clearer with the blank form beside it, and staff who receive the finished documents may never have the template at all. Audit is the third and the least glamorous: a shared drive accumulates templates nobody has looked at in years, and rendering the lot to PDF is the fastest way to see which ones still carry the old logo, the old address, or a name that left in 2019.

A PDF renders pages, so what you get is the template’s own content: body text, boilerplate paragraphs, tables, the letterhead, headers and footers, watermarks, page setup and margins, and any instructional or placeholder text the author left in place. That is a complete picture of the template’s visible layer and it is usually what somebody approving a design needs to see.

What cannot appear is everything that exists as a definition rather than as content. A style that is defined and used nowhere leaves no mark on any page. Building blocks and AutoText entries stored in the template are not rendered, because nothing has inserted them. Keyboard shortcuts, custom toolbar entries and the list of styles offered in the gallery are all properties of the template rather than marks on paper. If the point of the template is its style set, a PDF is the wrong way to review it and the styles pane in Word is the right one.

A common outcome of this conversion is a single page with a logo, an address block and nothing else, and it looks like a failure. It usually is not. A great many corporate templates contain no body content at all: their entire value is a style set, a page setup and a header, and the person who created them never intended anyone to read them as a document.

If that is what you get, the conversion has told you something useful about the file rather than failing to render it. It also tells you what to do next: to show what documents made from this template look like, create one, put some representative text in it, and convert that instead. A specimen document with two headings, a paragraph, a table and a bullet list demonstrates a house style far better than the template ever will.

Nothing is filled in and nothing is calculated. Content controls and structured document tags show their placeholder text — the grey "Click here to enter text" prompts — because that is genuinely what the template holds. DOCPROPERTY fields show the template’s own properties. Cross-references have nothing to refer to. Automatic numbering starts wherever the template says it starts.

Date fields are the one to watch, because they render as something plausible and wrong: a field set to update automatically resolves to the date of the conversion, which will look to a reviewer like a deliberate example. If the template is being circulated for approval, say so in the covering note, or replace the field with a specimen date in a copy of the template before converting. A reviewer who thinks the date is hard-coded will raise it as a fault that does not exist.

The rendering is done by LibreOffice rather than by Word, and the converter carries metric-compatible substitutes for Arial, Times New Roman, Courier New, Calibri and Cambria — faces with the same character widths as the originals, so line breaks land in the same places and layouts hold.

Templates are nonetheless the file type most exposed to font substitution, because a house style exists in order to specify a house typeface, and that typeface is usually a licensed one that is installed on staff machines and nowhere else. A template does not embed its fonts unless somebody explicitly turned embedding on. So the PDF may show your letterhead set in a substitute, which is a poor advertisement for a design being reviewed. If the point of the circulation is the typography, embed the fonts in a copy of the template first, or send the PDF with a note about what it is showing.

Three template formats turn up in the same shared drives and they are not interchangeable. DOTX arrived in 2007 alongside DOCX, is a ZIP of ECMA-376 XML, and cannot contain a VBA project — the registry records it as a template with macros absent. DOTM is the same container with macros permitted, which is why it is the one that gets quarantined by mail filters.

The older `.dot` is the binary Word template from the 1990s, an OLE compound file like a `.doc`, and it is the one most likely to be blocked outright by a modern Word installation’s file-block policy. If an old template will not open at all, that is the reason. Converting it is a separate job from this page, and the practical route is usually to open it in LibreOffice, save it as a DOTX, and work from there — which also removes whatever macro history the file accumulated over twenty years.

On our server rather than in your browser. Rendering a Word template needs a real office engine, and this page says so plainly instead of implying that everything on this site runs on your own device. The file travels over an encrypted connection to a container running LibreOffice headless, and that container has no outbound internet access of its own.

Each job gets its own scratch directory and its own LibreOffice profile — two `soffice` processes sharing one profile corrupt it, and the symptom is a conversion that never returns rather than an error — and the directory is deleted when the job ends whatever the outcome. Anything still running after sixty seconds is terminated. The free tier accepts 25 MB per uploaded file, which is generous for a template, since templates are almost always small.

The audit case is worth doing in bulk rather than one at a time. Convert every template in the shared drive, put the PDFs in one folder, and page through them: outdated logos, a registered address that changed, a strapline that was retired, a named contact who left, and three near-identical versions of the same letter all become obvious in about the time it takes to scroll. That is a job that is nearly impossible in Word, because every double-click creates a document you then have to close without saving.

Name the PDFs after the templates so the two sets line up, and keep them — a dated set of renderings is a reasonable record of what the organisation’s document estate looked like at a point in time, and it is far easier to compare against next year than a folder of `.dotx` files that can only be inspected one at a time. If a template turns out to be wrong, fix the template; the PDF is evidence, not the thing to correct.