DOCX compatibility across editing engines
UseJunior publishes a live comparison of DOCX libraries and services so teams can see which implementations preserve structure, formatting, tracked changes, tables, headers, and comments across repeatable fixtures.
What the comparison covers
The matrix is generated from the open DOCX platform test suite. Each adapter receives the same fixture and operation definition, then the runner records whether it passed, produced a different document, reported unsupported capability, or failed unexpectedly.
The current suite compares safe-docx with python-docx, LibreOffice, the Open XML SDK, docx, SuperDoc, and docx-rs. The cases are intentionally practical: replacing text while preserving runs, editing tables, adding headers and footers, working with comments, and accepting or rejecting tracked changes.
Live endpoints
How to read the results
Passed
The adapter completed the requested operation and produced the expected DOCX output.
Different
The adapter completed, but the generated document did not match the expected structure or content.
Unsupported
The implementation declared that the operation is outside its supported capability set.
Error
The adapter exited unexpectedly. These are treated as defects in the adapter or runner until classified.
Source and attribution
The matrix is proxied through usejunior.com for discoverability and traffic measurement, while the generated artifacts remain published from the Open Agreements DOCX platform tests project.