How to Clean ODF Metadata in LibreOffice and OpenOffice Files

You just finished drafting a sensitive report or a confidential proposal. You hit save, attach the file to an email, and send it off. But did you realize that your document is carrying a digital fingerprint? Inside every OpenDocument Format (ODF) file-whether it's an .odt text doc, an .ods spreadsheet, or an .odp presentation-there is a hidden layer of data revealing who wrote it, when it was edited, and how many times you changed your mind. For professionals handling private client info, legal drafts, or internal strategy, this invisible trail can be a major liability.

Cleaning this metadata isn't just about tidying up; it's a critical step for data privacy and compliance. Whether you are using LibreOffice, maintained by The Document Foundation, or Apache OpenOffice, the process requires more than just deleting visible text. You have to strip the structural history embedded deep within the file's architecture. Here is exactly how to scrub those files clean so only the content remains.

Understanding the Hidden Structure of ODF Files

To understand what you are removing, you first need to know where it lives. An ODF file is essentially a ZIP archive containing several XML files. When you open an .odt file in an archiver, you will see specific components like content.xml, styles.xml, and most importantly for privacy, meta.xml.

The meta.xml file stores standard Dublin Core properties such as dc:creator (the author's name), dc:date, and creation timestamps. It also holds application-specific stats like meta:editing-duration (total time spent editing in seconds) and meta:editing-cycles (number of saves). Beyond these standard fields, user-defined custom properties often sit in meta:user-defined elements. These might contain project codes, client names, or internal version tags that you definitely do not want landing on a competitor's desk.

Because this data is structural, simply highlighting and deleting text in the document window does not touch it. The metadata survives copy-paste operations and even some export formats unless explicitly stripped. This makes manual inspection or dedicated tooling essential before any external distribution.

Manual Cleaning Steps in LibreOffice

If you prefer to handle this directly within your office suite, LibreOffice provides several built-in mechanisms to reduce your digital footprint. However, there is no single "magic button" that scrubs everything at once. You must follow a multi-step checklist.

1. Clear User Data: Go to Tools → Options → LibreOffice → User Data. Clear your first name, last name, initials, and company fields. If these are filled, they will automatically populate the meta:initial-creator field in every new document you create.
2. Enable Auto-Cleanup: In the same Options menu, navigate to Security → Options. Check the box labeled "Remove personal information on saving." This setting forces LibreOffice to strip user names from comments and changes upon every save, though it may not clear all historical data from older versions of the file.
3. Reset Statistics: Open your target document and go to File → Properties → General. Click the "Reset" button. This zeros out the total editing time and revision count. Crucially, uncheck the "Apply user data" box here to ensure the current session doesn't re-embed your profile into the file.
4. Scrub Description Fields: Switch to the Description tab in the Properties dialog. Manually delete the Title, Subject, Keywords, and Comments fields. These are often overlooked but can reveal the document's purpose or internal categorization.
5. Remove Custom Properties: Move to the Custom Properties tab. Delete any rows present here. These are frequently used by templates or add-ins to store metadata that is invisible in the main interface but readable by anyone with access to the raw XML.

While these steps cover the basics, they miss the deeper layers of hidden content that pose the highest risk.

Handling Tracked Changes, Comments, and Hidden Content

Metadata cleaning is incomplete if you leave behind edit history. Tracked changes in ODF Writer are stored as markup inside content.xml. They record exactly who inserted or deleted text and when. To clear this:

• Go to Edit → Changes → Manage.
• Select all changes and choose either "Accept All" or "Reject All."
• This action flattens the document, removing the underlying XML tags that identify the editor.

Comments are equally dangerous. They are saved as office:annotation elements and always carry the creator's name and timestamp. Use Edit → Comments to view them, then right-click each one to delete. Do not assume they are gone just because they aren't visible in Print Preview mode.

Finally, check for hidden content. In Writer, enable View → Hidden Paragraphs to see if confidential notes were hidden rather than deleted. In Calc (spreadsheets), go to Format → Sheet and look for hidden sheets. A hidden sheet might contain a lookup table with employee IDs or backup data that wasn't meant for publication. Unhide them, verify the content, and delete if necessary.

Automated Solutions for Batch Processing

Manually checking ten documents is tedious. Checking a hundred is impossible without automation. For organizations releasing large volumes of ODF files-such as universities publishing open educational resources or NGOs sharing reports-batch tools are necessary.

In the free-software ecosystem, the Metadata Anonymisation Toolkit 2 (MAT2) is a powerful command-line utility. Built on Python, MAT2 parses the ZIP structure of .odt, .ods, and .odp files. It strips known metadata fields like dc:creator and removes thumbnail previews (thumbnail.png) that can leak visual snapshots of the document. It is widely used in privacy-focused distributions like Tails.

For users who prefer a graphical interface or need to process mixed formats (including Microsoft Office docs), proprietary tools like BatchPurifier offer enterprise-grade scrubbing. However, these often require installation and licensing.

A modern alternative that bridges the gap between convenience and privacy is Vaulternal's document metadata remover. Unlike desktop software that requires installation, this tool runs entirely in your browser. Because it processes files locally using WebAssembly, your document never leaves your device. You can upload an .odt file, inspect the exposed metadata fields, and strip them-including author names, editing cycles, and custom properties-in seconds. It works seamlessly on Mac, Linux, ChromeOS, and Windows, making it a versatile option for cross-platform teams who cannot rely on a single installed suite.

Technical Deep Dive: Manual XML Editing

For power users who need absolute control, direct manipulation of the ODF package is possible. Since an ODF file is just a renamed ZIP archive, you can extract it using standard tools like unzip. Once extracted, open meta.xml in a plain-text editor.

You can manually delete specific XML nodes such as <dc:creator>, <meta:initial-creator>, and <meta:creation-date>. You should also check manifest.rdf for any RDF metadata that might point to user identities. After editing, compress the files back into a ZIP archive and rename it to .odt.

Warning: This method is high-risk. Careless editing can break the internal manifest checksums, causing LibreOffice or OpenOffice to flag the file as corrupted. Furthermore, if the document has a digital signature (stored in manifest-signatures.xml), modifying the XML will invalidate that signature. Always keep a backup before attempting manual XML edits, and validate the resulting file using an ODF validator tool.

Best Practices for Ongoing Privacy

Cleaning metadata after the fact is reactive. The best strategy is proactive prevention. Configure your office suite settings once so that every new document starts clean.

• Blank Profiles: Keep your LibreOffice/OpenOffice User Data fields empty or use pseudonymous values. This prevents accidental leakage of real names into meta:initial-creator.
• Disable Tracking: Unless you specifically need version control, turn off "Record changes" in the Security tab of File Properties. This prevents the accumulation of edit history that is hard to clean later.
• Verify Before Sending: Make it a habit to open File → Properties before hitting send on any external email. Glance at the General and Description tabs. If you see your name or internal project codes, stop and clean them.
• Use Dedicated Tools: For high-stakes documents, don't rely solely on memory. Run the file through a dedicated scrubber like this document metadata stripper to ensure no residual traces remain. The peace of mind is worth the extra minute.