DOCX with Metadata Stripped
The same DOCX document part without core or custom property parts, suitable for checking OOXML metadata removal without content loss.
Rendered preview of the docx file (1.6 KB). Download above for the original.
Specifications
- Metadata
- none (stripped)
- Document Xml Sha256
- 2aa28c5e20d27bb6181272ea01d85daad6e4f099c2dca5611d1e368d32fc2c69
- Twin
- stripped
Testing contract
Expected to pass- Scenario
- Verify metadata removal from the stripped DOCX without changing its underlying content.
- Expected result
- Find no descriptive metadata; compute documentXml SHA-256 2aa28c5e20d27bb6181272ea01d85daad6e4f099c2dca5611d1e368d32fc2c69, matching the full twin.
What is a .docx file?
DOCX is the default Microsoft Word format, an Office Open XML document packaged as a ZIP archive of XML parts, media, and relationships. It stores structured text, styles, tables, images, and metadata. It is the dominant format for editable word-processing documents.
How to use this file
Use an example DOCX to test Office Open XML parsing, text and style extraction, ZIP-package handling, and converters that render or transform Word documents.
How to use this file for testing
“DOCX with Metadata Stripped” is a deterministic Testaroo fixture for Metadata testing, Conversion testing. Images, audio, video, and documents with documented metadata paired with deliberately stripped versions, for verifying extraction, preservation, redaction, and privacy-scrubbing behavior.
Documented properties for this file: DOCX · 1,603 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.
Code examples
from docx import Document # pip install python-docx
doc = Document("docx-core-custom-stripped.docx")
for p in doc.paragraphs[:10]:
print(p.text)Generated by generation/p6_core.py. Free for any use, no attribution required, license.
Related files
- pdfAlder Table Bistro: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Alder Table Bistro. Invoice INV-BST-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 207.60, GST 10.38, 217.98 CAD due. This is the only file in the set that carries its data twice in one container.
- pdfCedar Street Tacos: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Cedar Street Tacos. Invoice INV-TRK-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 187.70, GST 9.38, 197.08 CAD due. This is the only file in the set that carries its data twice in one container.
- pdfCopper Oven Bakery: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Copper Oven Bakery. Invoice INV-BAK-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 165.41, GST 8.27, 173.68 CAD due. This is the only file in the set that carries its data twice in one container.
- pdfEmber Lane Pizza: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Ember Lane Pizza. Invoice INV-PIZ-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 243.81, GST 12.19, 256.00 CAD due. This is the only file in the set that carries its data twice in one container.
- pdfHarbour Kitchen Group: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Harbour Kitchen Group. Invoice INV-GRP-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 261.93, GST 13.10, 275.03 CAD due. This is the only file in the set that carries its data twice in one container.
- pdfJuniper Corner Cafe: Factur-X hybrid invoice PDFFactur-X hybrid invoice PDF for Juniper Corner Cafe. Invoice INV-CAF-5001 rendered for a person and attached as machine-readable XML for a system. The embedded file is named factur-x.xml, is referenced from both the EmbeddedFiles name tree and the document-level AF array with an AFRelationship of Data, and is byte-identical to invoice-facturx-cii.xml. The visible page and the XML agree: net 330.69, GST 16.53, 347.22 CAD due. This is the only file in the set that carries its data twice in one container.
