Working With OpenOffice Templates in 2025
Most people treat a Template For Open Office as a magic box that saves them work. It's not. It's a file you open, modify, and resave. The real problem is understanding how the template system actually stores and retrieves style information. If you've ever opened a .ots file and watched your carefully formatted tables collapse into default margins, you know what I mean. OpenOffice (and its fork LibreOffice) uses two template formats: the legacy .ots format and the newer ODT-based template system that LibreOffice adopted around 2013. The legacy format creates a separate template cache that often gets out of sync with your actual working files. This causes issues where a document appears to use the template styles but actually loaded a cached version from weeks ago. I spent three days tracking down why my invoice template was showing wrong currency formats. Turns out the template cache at ~/.config/openoffice.org/3/user/template/ wasn't being cleared between updates.
How a Template For Open Office Actually Works
A template is just an ODT file with a specific flag set in META-INF/manifest.xml that marks it as a template rather than a regular document. When you create a new document from it, LibreOffice reads that flag, copies the style definitions, but leaves the actual content empty. Styles include page layouts, character formatting, paragraph styles, and frame properties. The tricky part is that styles can be inherited or overridden. A paragraph style in your template might be based on "Default Paragraph Style," which itself inherits from the document's default settings. If someone later modifies the base style in a different template and you don't realize it, your documents will shift unexpectedly. I've seen this happen when companies migrate from OpenOffice to LibreOffice — the style inheritance chain differs slightly between the two applications, and existing templates start producing inconsistent results without any obvious error message.
Creating Your Own Template
Start with a blank document or an existing file you want to preserve the formatting of. Go to File > Templates > Save As. Name it something descriptive — vague names like "Invoice Template" will haunt you when you have twelve similar templates all doing different things. I recommend naming conventions like "Invoice-Standard-V2.1.ots" so versioning is visible. Before saving, remove any content-specific data. Tables with actual numbers, client names, or sample paragraphs should go. What stays are the styles, page layouts, headers, footers, and any frames or images that are purely structural. I usually create a test document from each new template and verify it opens clean before distributing it to others.
Get the Full Details
Common Pitfalls That Waste Hours
Style conflicts between templates — If you import styles from one template into another, conflicts occur when both templates define the same style name with different properties. The imported version wins, but you won't get a warning. Use the Styles sidebar (F11) and check for crossed-out style names, which indicate conflicts. Cached template data — The first time you open a template after modifying it, the application sometimes serves you a cached version. Close the application completely, clear the user template cache folder, and reopen. This resolves about 80% of "my template changes didn't apply" complaints I see on forums. Macro-enabled templates — Templates with embedded macros (.ots with basic macros) behave differently across operating systems and application versions. A macro that works on Windows OpenOffice 4.1.15 won't necessarily run the same way on Linux LibreOffice 7.4. Test thoroughly or avoid embedding macros in templates entirely.
Font dependencies — If your template uses a specific font that isn't installed on the target machine, LibreOffice substitutes it silently. The document looks fine on your screen but renders completely differently on someone else's computer. Always embed fonts in the template if cross-platform compatibility matters, or stick to system fonts like Arial, Times New Roman, and Courier New.
When Templates Fail Completely
Templates cannot fix broken style hierarchies. If your source document has inline formatting mixed with styles (which most manual formatting produces), saving it as a template just preserves the mess. You need to clean up the style usage first by running Format > Clear Direct Formatting on problematic sections, then reapplying proper paragraph styles. Also, templates don't replicate correctly when shared via email. The recipient often gets a regular document instead of a usable template because the template flag doesn't transfer through most email clients. Use a shared network folder or cloud storage with proper file extensions (.ots or .ott) to avoid this. If you need template sharing at scale, consider using LibreOffice's built-in template management system under File > New > Templates, which centralizes all templates in one accessible location rather than scattering them across individual folders.
