How should I use the ODT manifest endpoint?

Fetch manifest JSON to pin fixture names, sizes, hashes, and MIME expectations in automated tests.

Why does this format have a category-specific hub?

A category-specific hub keeps assumptions aligned with practical workflows and related format alternatives.

Format reference

ODT Format Hub

OpenDocument Text (.odt) is the OASIS-defined open standard for word processing documents, compatible with LibreOffice, OpenOffice, and other suites. It supports structured styles, embedded objects, and XML-based metadata. Use sample .odt files to confirm ODF compatibility, style preservation, and accurate conversion to and from other document formats.

Open Sample Page Open Manifest JSON

4 Files

220 Downloads (30d)

application/vnd.oasis.opendocument.text

Keep adjacent formats visible.

CSV (22) JSON (22) PDF (21) TXT (14) XML (11) TSV (9) DOCX (8) MD (8)

Format Strategy Links

Keep strategy links secondary but close.

Open ODT FAQ

Best Format Guides

Best Document Format for Final Sharing

Best Format for Use Cases

Best Format for Collaborative Document Editing

Implementation Notes

Keep implementation notes explicit.

Use the manifest endpoint for deterministic fixture selection in CI, then validate MIME/type detection against actual parser output.

If this format appears in multiple categories, prefer category-specific hub pages to keep test assumptions aligned with real usage.